Accessibility Gaps in U.S. Government Dashboards for Blind and Low-Vision Residents
Chadani Acharya
TL;DR
The paper investigates accessibility gaps in U.S. government dashboards for blind and low-vision residents. It audits six public dashboards across federal, state, and city levels using a WCAG-aligned rubric that covers discoverability, keyboard access, semantic labeling, plain-language status, and machine-readable data. A central contribution is the identification of urgency inversion, where time-sensitive dashboards provide weaker accessibility than slower accountability dashboards. The authors propose three baseline obligations for public dashboards: provide plain-language status updates at the update cadence, ensure mirrored machine-readable data, and include explicit accessibility commitments in dashboard descriptions, aligning with ADA Title II. The findings have practical implications for policy and design, guiding regulators and practitioners toward accessible, accountable civic interfaces.
Abstract
Public dashboards are now a common way for US government agencies to share high stakes information with residents. We audited six live systems at federal, state, and city levels: CDC respiratory illness, HUD homelessness PIT and HIC, California HCD Annual Progress Report, New York City Mayor's Management Report, Houston Permitting, and Chicago public health and budget dashboards. Using a rubric based on screen reader needs and WCAG, we checked five items: (1) discoverability of key metrics by assistive tech, (2) keyboard access without mouse hover, (3) clear semantic labels for axes, series, and categories, (4) short plain language status and trend notes, and (5) machine readable tables or CSVs that mirror what sighted users see. Findings are mixed. Many charts fail basic discoverability or depend on hover, which blocks keyboard and screen reader use. Plain language summaries are common in CDC and Chicago, but rare in HUD and Houston. Machine readable data is strong for NYC, California, and HUD; it is weaker or unclear for Houston. Several sites promise service for the public or for customers yet do not name accessibility in their descriptions. Across systems we also observe urgency inversion: faster, operational dashboards tend to provide fewer accessible affordances than slower accountability dashboards. These patterns matter for equal participation and for ADA Title II compliance that references WCAG 2.1 AA. We propose three steps for any public dashboard: add a brief status and trend text at the same update cadence, publish a matching table or CSV of the visual metrics, and state an explicit accessibility commitment.
