Table of Contents
Fetching ...

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.

Accessibility Gaps in U.S. Government Dashboards for Blind and Low-Vision Residents

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.

Paper Structure

This paper contains 20 sections, 1 figure, 2 tables.

Figures (1)

  • Figure 1: Accessibility affordances versus operational urgency across six public dashboard ecosystems. Each marker represents one audited dashboard ecosystem: CDC respiratory illness dashboards; HUD PIT/HIC homelessness dashboards; California HCD Annual Progress Report (APR) housing compliance dashboard; New York City’s Mayor’s Management Report (MMR / Dynamic MMR); Houston Permitting Center performance dashboard; and Chicago’s respiratory illness and budget/ARPA dashboards. The horizontal axis encodes how time-sensitive the information is, from annual compliance reporting (left) to daily backlog and inspection status (right). The vertical axis encodes the strength of reported accessibility affordances for blind and low-vision (BLV) residents, computed as the sum of three features (each scored 0, 0.5, or 1): (1) a plain-language status or “what is happening now” summary at the dashboard’s stated update cadence, (2) clearly published machine-readable data (for example, CSV, open data table) that mirrors the same metrics shown visually, and (3) explicit trend or change-over-time described in text rather than only in charts. The dashed line shows the fitted linear trend. The pattern illustrates urgency inversion: dashboards with the most urgent, operational stakes (for example, Houston’s daily permitting backlog, “designed for customers” and “updated daily”) show the weakest accessible affordances for BLV users, while slower accountability dashboards (for example, California housing compliance, New York City’s performance “public report card,” CDC and Chicago’s weekly illness/risk summaries) provide both narrative context and downloadable data. Audit snapshot: September 2025.