Accessibility
A general claim of accessibility is worthless in procurement. GOV UI states a target and publishes evidence against it.
Scope. GOV UI supports conformance at the component level. It cannot certify an application. A team building on it still owns its own content, information architecture, server-side validation and end-to-end testing.
Target
| Commitment | Detail |
|---|---|
| Standard | WCAG 2.2 Level AA |
| Evidence | VPAT 2.5 ACR per minor release |
| India | GIGW 3.0 conformance mapping, certified by STQC |
| Automated | Contrast and markup gates in CI |
| Manual | NVDA, JAWS and VoiceOver matrix per interactive component |
| High contrast | forced-colors: active supported |
Automated tooling catches roughly a third of real accessibility defects. The manual matrix is not optional, and is part of a component's definition of done.
What runs on every change
- Contrast. Every color pair the system depends on is measured from the tokens that ship — 24 pairs, including text on each surface, control edges, status badges and both edges of the focus ring.
- Conformance. Every emitter produces the agreed markup, so ARIA and semantics cannot drift per framework.
- Budget. Payload stays within a gzipped limit, because performance is an accessibility issue on a low-end device.
Not yet automated. Browser-level checks — axe, forced-colors, 200% zoom and RTL rendering — are not in CI yet. Everything verified today is static analysis and DOM comparison, which is genuinely useful but is not the same as testing rendered output.
Reporting a problem
Accessibility defects are treated as correctness bugs, not enhancements. Report the component, the assistive technology and version, and what you expected.