Accessibility

Make the interface usable by keyboard, screen reader, magnification, voice and reduced-motion users. Judge real behavior, not the presence of ARIA. Automated scans find roughly a third of issues; the rest needs manual checks.

Phase 1: Scope

• Name the pages, flows and components in scope, the conformance target (default WCAG 2.2 AA), supported browsers, and whether the task is audit-only or audit-and-fix.
• Read the component library and design tokens first. A fix belongs in the shared component or token, not in one screen's copy.
• Pick representative states: default, hover, focus, error, empty, loading, expanded, modal open, long content, narrow viewport, dark mode.

Phase 2: Test

Run each layer and record what it covered. See references/wcag-checklist.md for the criteria, how to test each, and the 2.2 additions.