What dashboard accessibility standards do US agencies follow?

What to take away

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.

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.

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.

In a lowest-price technically acceptable buy, price is not opened until the technical review passes, so an accessibility finding can end the bid before any cost comparison.

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.

An individual may file a Section 508 complaint with the Access Board within 180 days of the alleged violation. The revised standards took effect on January 18, 2018, and the safe harbor covers only unchanged equipment that met the older rule.

Remediation has no fixed price. It depends on how many templates and views carry the failing pattern, and whether the vendor still ships fixes for that version.

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 puts the requirement in the Department of Information Resources rules at 1 Texas Administrative Code Chapter 206, which sets state web standards, with the underlying authority in Texas Government Code Chapter 2054.

California sets its requirement in Government Code section 7405, which covers state internet and intranet sites, and Government Code section 11135 reaches technology in state-funded programs. State entities in California 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.

Accessibility sits alongside the design choices in the reporting layer. 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