a11y-passlisted

# Accessibility Pass (WCAG 2.2 AA) Accessibility is whether a person can finish a real task without an avoidable barrier. Repair the failing path, then prove the repair in the rendered interface. ## Triage one rendered user path Write one path before opening a checker: **entry → action → result/recovery**. Name the user-facing outcome, the affected UI, and the smallest viewport or assistive setup that can expose the 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 to express a relationship or live behavior native elements cannot supply. Never use a role, audit score, or automated pass as proof that the path works. ## Prove the path in the interface 1. Tab forward and backward from the browser chrome through completion. Record focus order, visible indicator, and any trap. 2. Trigger the failure state with the keyboard. Confirm focus stays purposeful, the error is progr