Skip to main content

Accessibility standard

WCAG 2.2 AA as concrete per-component and per-screen acceptance criteria, not a policy essay. Design owns the bar; Test enforces it in the gates. For EU-market clients, EN 301 549 / the European Accessibility Act apply on top.

How it's expressed​

Not "be accessible" but testable criteria per element and screen:

  • Focus order and visible focus.
  • Keyboard operability of every interactive element.
  • Labels / ARIA per the WAI-ARIA APG.
  • Contrast ratios.
  • Error identification and recovery.

These live in each screen spec.

Enforcement​

  • Automated — axe-core / Pa11y in CI, blocking the merge gate on regressions.
  • Manual — a keyboard + screen-reader charter per key journey (automation can't catch everything).
  • Verified at the Design Review and Refinement Exit gates.

Because agents build most first-draft UI, encoding accessibility into the design context pack and lint means agents build accessible-by-default rather than being retrofitted.

Standards referenced: WCAG 2.2 AA, EN 301 549, WAI-ARIA APG.