Rules
What dashboard accessibility standards do US agencies follow?
Dashboard accessibility standards US agencies follow start with Section 508 and WCAG 2.x, with state rules layered on top, plus required VPAT documentation.
What to take away
- Federal agencies must meet Section 508, which adopts WCAG 2.0 Level AA as the technical standard for web content and dashboards.
- Contractors selling dashboards to federal buyers inherit the same obligation through the contract, not through a voluntary pledge.
- A compliant accessibility conformance report states which criteria pass, which fail, and which remain untested.
- Texas and California add their own procurement rules on top of the federal baseline.
- A failed conformance report can remove a product from consideration before any demo happens.
The rule that governs most American dashboard work is Section 508 of the Rehabilitation Act. It applies to federal agencies when they build, buy, maintain or use electronic and information technology. Dashboards count as information technology, so the obligation attaches to the tool itself and to the people who operate it.
Who has jurisdiction
The Access Board writes the technical standards that Section 508 enforces. Those standards incorporate WCAG 2.0 Level AA by reference, and many agencies now ask vendors for WCAG 2.1 AA instead because the newer version closes gaps on mobile and low-vision use.
The Section 508 laws and policies page sets out which entities fall inside the requirement. Federal agencies are covered directly. Contractors are covered when the contract says so, which most federal solicitations now do.
The ADA reaches a different set of organizations. Title II covers state and local government entities, and the Department of Justice has stated that web content falls within its scope. A city dashboard open to residents sits inside that reading. The ADA web guidance explains how the department frames the obligation for public entities.
What must be disclosed
A vendor responding to a federal solicitation usually files an accessibility conformance report built on the VPAT template. The report is a disclosure document, not a certificate. It states, criterion by criterion, whether the product supports, partially supports, does not support, or has not been evaluated against each success criterion.
A usable report contains four things.
- The exact standard and version tested, such as WCAG 2.1 Level AA.
- A per-criterion result with a short note explaining any partial support.
- The date of the evaluation and the product version it covers.
- Contact information for follow-up questions from the buying agency.
Agencies that skip this step and accept a marketing claim instead tend to discover the gap during remediation, when the cost lands on them. The WCAG overview is the reference document most conformance reports cite.
Records to keep
Accessibility paperwork has a retention life. Agencies and their contractors generally keep the following on file for the life of the system and through any audit window.
- The signed conformance report for each product version in use.
- Test scripts and results from the most recent evaluation.
- A log of accessibility complaints and how each was resolved.
- The remediation plan for any criterion marked as not supported.
- Proof that staff who publish dashboards received accessibility training.
That last item matters more than it looks. A dashboard platform can pass every automated check and still fail in practice because an analyst published a chart with color as the only cue. For the questions that recur once a dashboard is live, see the dashboards questions that keep coming back.
What happens if you do not
The concrete consequence is procurement exclusion. A federal contracting officer who receives a conformance report showing unsupported criteria on a core function can rule the product out before evaluation of price or features. There is no partial credit for a strong demo.
For an agency already running a non-compliant dashboard, the consequence arrives as a complaint. A member of the public files an accessibility grievance, the agency opens a case, and remediation moves onto a schedule it does not control. In some cases the office has to publish the same data in an alternate format while the fix is pending.
A dashboard that fails a conformance review does not get a warning period. It gets a finding, and the finding follows the program office into the next budget cycle.
Where the rules differ by place
Federal rules set a floor, and states build above it. Texas requires state agencies to follow accessibility standards in procurement and publishes its own rules for electronic information resources. California applies accessibility requirements to state government web content and to technology contracts, and its state entities often ask for WCAG 2.1 AA rather than 2.0.
Two practical differences show up in state work. First, the reporting template may differ from the federal VPAT. Second, the enforcement path runs through a state agency rather than a federal contracting officer, so the timeline for a complaint is shorter.
| Layer | Who is covered | Standard named |
|---|---|---|
| Federal Section 508 | Agencies and covered contractors | WCAG 2.0 AA, often 2.1 AA |
| ADA Title II | State and local public entities | Department of Justice web guidance |
| Texas | State agencies and vendors | State accessibility rules |
| California | State entities and contractors | WCAG 2.1 AA in practice |
For teams building the reporting layer itself, the obligations sit alongside the design choices. A reporting guide for grading an explanation covers the review step that catches accessibility defects before publication. Teams that treat accessibility as a separate workstream usually find it reappears as a defect later, which is the pattern described in reporting mistakes that outlive correct arithmetic.
Common questions
Does Section 508 apply to a private company building an internal dashboard? No, unless the company holds a federal contract that carries the clause, or the dashboard is used to deliver a federal program. The obligation travels with the contract, not with the software category.
Which WCAG version should a US agency ask for? WCAG 2.0 Level AA is the floor written into the current standards. Many agencies specify 2.1 AA because it adds criteria for mobile orientation and text spacing at no real cost to the vendor.
Is an automated scan enough to prove compliance? No. Automated tools catch a minority of success criteria. A defensible conformance report includes manual testing with a screen reader and keyboard-only operation, which is where most dashboard failures appear.
What does a non-compliant dashboard cost an agency? The direct cost is remediation, plus the staff time to publish an accessible alternative while the fix is pending. The larger cost is the procurement finding, which can delay a program by a full budget cycle.
