Accessibility
WCAG 2.1 AA, from the first wireframe.
The RFP requires WCAG 2.1 AA — screen-reader support, full keyboard access, 4.5:1 contrast, alt text, text resizing to 200%, and accessible forms. This prototype is built to that bar and re-tested with axe-core on every route.
170automated axe violations across 8 representative pages of the current City site (nrhtx.com)
0axe violations across this prototype's 15 routes
AAthe standard we design and test to: color, keyboard, forms, labels, and authoring
What we found
What the current-site issues mean for residents
| Issue family | Scale | Resident impact |
|---|---|---|
| Lists that aren't real lists | 59 nodes | Several pages expose list items outside proper lists, which can make menus and content groups confusing to screen-reader users. |
| Page sections a screen reader can skip to | 63 nodes | Repeated or missing landmarks make it harder to jump between navigation, main content, sidebars, and footers. |
| Links that don't say where they go | 35 nodes | Some links have no discernible text, so assistive technology cannot tell residents where the link goes. |
| Labels assistive technology relies on | 4 critical nodes | Certain ARIA roles are missing required child roles. These are high-priority fixes because they can break expected keyboard or screen-reader behavior. |
| Data tables and heading order | 9 nodes | A few pages have invalid table scope attributes or skipped heading levels, which affects page scanning and table interpretation. |
How it stays fixed
Accessibility as a habit, not a one-time pass
| Design | Contrast, headings, tab order, focus states, and responsive text are checked before any visual is approved. |
|---|---|
| CMS | Image fields require alt text, form labels are explicit, and the publish workflow includes an accessibility review step. |
| Testing | Automated axe-core scans, keyboard walkthroughs, VoiceOver and NVDA spot checks, and mobile overflow checks run before launch. |
| Reporting | The launch package includes the issue register, screenshots, remediation notes, and a public accessibility statement with a report-an-issue route. |
