a11y-passlisted

# Accessibility Pass (WCAG 2.2 AA) Accessibility means finishing a real task without an avoidable barrier. Repair the failing path; prove it in the rendered interface. ## Triage one rendered user path Write one path before opening a checker: **entry → action → result/recovery**. Name outcome, affected UI, and smallest viewport or assistive setup that exposes failure. | Path point | Inspect | Repair when it fails | | --- | --- | --- | | Entry | landmark, page title, reading order, skip link | give the page a named, reachable start | | Action | visible focus, native semantics, keyboard order, target size | repair the control before adding ARIA | | Change | errors, loading, dialogs, live updates, motion | announce the meaningful change without stealing focus | | Recovery | error copy, focus destination, retained input, retry | return the person to a specific next action | | Layout | 200% and 400% zoom, reflow, narrow viewport | remove horizontal loss and clipped controls | Start with native HTML. Use ARIA only for relationships or live behavior native elements cannot supply. A role, audit score, or automated pass never proves the path. ## Prove the path in the interface 1. Tab forward/back from browser chrome through completion; record order, visible indicator, and traps. 2. Trigger failure by keyboard; confirm purposeful focus, programmatic error association, and retained data. 3. Read the region with a screen reader or inspect computed name, role, value, state, an