Working demonstration
Accessibility is a legal requirement and the right thing to do for residents who reach AHA on a phone or with a screen reader. So we measured it. Below is a real automated audit of the current site next to this prototype.
On June 3, 2026 we scanned 12 of the most-used pages on abqha.org with axe-core, the industry-standard automated accessibility scanner, against the federal standard (WCAG 2.1 Level A and AA). We ran the same scan on this prototype. Automated testing catches a large share of issues; the rest we confirm by hand and with assistive-technology testing.
These are real numbers, not estimates. The scan is a committed script (scripts/aha-audit.ts, axe-core 4.11.3 via Playwright) that anyone can rerun against both sites. The findings below are the rules axe flagged, by how many times each appears across the 12 pages. The two highlighted in red, missing alternative text and color contrast, are the ones residents feel first. The full method and page-by-page results are in the Accessibility Pre-Audit appendix that accompanies our proposal.
Filter by severity or success criterion. Everything runs in your browser, no page reload.
Loading findings…
Beyond the scanner
Albuquerque is roughly half Hispanic, yet the current site offers no Spanish navigation or pages, only a few standalone bilingual notices. This prototype ships Spanish versions of the most common tasks, tagged so screen readers read them in Spanish.
The current site is built on a heavy visual page builder that emits as many as thirteen top-level headings on a single page. A screen-reader user hears thirteen “heading level 1” landmarks instead of one clear title. The rebuild uses clean, semantic structure.
How we get to AA
Automated and manual testing of every template, with assistive-technology testing and a cited findings report you can act on.
Semantic HTML, full keyboard support, labelled forms, contrast-checked color, and remediation of the documents residents actually download.
Ongoing monitoring, a yearly conformance statement, staff training, and periodic re-audits so the site stays compliant as content changes.
The federal requirement for many public entities to meet WCAG 2.1 Level AA is being phased in over the coming years under the Department of Justice's Title II rule. A measured plan now is the difference between meeting it comfortably and scrambling later.
