wcag-keyboard-navigationlisted
Install: claude install-skill testland/qa
# wcag-keyboard-navigation
> Reference catalog for **how** to verify keyboard-navigation
> conformance. Pairs with the scanner umbrella
> `axe-a11y` (axe-core, pa11y, Lighthouse a11y).
## Overview
WCAG 2.2 organizes accessibility into four principles -
**Perceivable / Operable / Understandable / Robust** - at three
conformance levels - **A / AA / AAA** ([wcag22][wcag22]).
[wcag22]: https://www.w3.org/TR/WCAG22/
Keyboard navigation lives under **Operable** (Principle 2) and
spans six key Success Criteria covering keyboard operability,
focus management, and focus visibility.
## When to use
- Reviewing a component's keyboard interaction surface during PR
review.
- Authoring a keyboard-navigation test plan for a new component.
- Triaging an accessibility audit finding tagged with one of the
SCs below.
- Configuring per-rule severities for
`axe-a11y`.
## Success Criteria
### SC 2.1.1 - Keyboard (Level A)
Per [wcag22][wcag22]: "All functionality of the content is operable
through a keyboard interface" without requiring specific timings.
Path-dependent input (handwriting) is exempt.
| Pattern | What to test |
|-------------------------------------------------------|-------------------------------------------------------|
| `<button>`, `<a href>`, `<input>` | Native - already keyboard-accessible. |
| `<div onclick="...">`