keyboard-accessibilitylisted

# Keyboard accessibility Apply these rules to every interactive element and feature. Examples are React-first. Vanilla JavaScript is shown only where it differs meaningfully. The detailed rules and code examples are bundled under `./reference/`. Read the relevant file before applying or citing a rule. ## Core mandate All interactive functionality must be fully usable with a keyboard alone, with no mouse or touch required, except where the function genuinely depends on path-based movement (for example, freehand drawing). Keyboard access is not the same as "can Tab to it": native and composite widgets use different key conventions, and users must be able to reach, operate, and leave every component. ## Confirmation When you are only reviewing, report findings without pausing. Before applying edits to existing files, confirm the intended change set first, and ask for any context you need to judge correctly instead of guessing. ## Severity scale | Level | Meaning | | --- | --- | | **Critical** | Blocks task completion entirely for keyboard and assistive technology (AT) users | | **Serious** | Significantly impairs keyboard access, with no reasonable workaround | | **Moderate** | Creates friction, but a workaround exists | | **Minor** | Best-practice gap with marginal impact | Judge severity by the actual effect on the task, not the rule alone: can the user reach, operate, and leave the component; is an essential task blocked; is focus lost or placed misleadingly. ## Refe