| Layer | Invariant | Ask |
|---|---|---|
| Tokens | Contrast, spacing, motion, readable type. | Can teams combine tokens without creating unreadable UI? |
| Components | Keyboard behavior, focus, names, roles, states. | Does the component make the accessible path the default? |
| Patterns | Recoverable flows and understandable feedback. | Can users complete the task under error, delay, or assistive tech? |
| Docs | Usage rules, examples, anti-patterns. | Do adopters know what not to do? |
Fast checks
- Tab through the flow without a mouse.
- Check focus visibility at every step.
- Confirm every control has a persistent label or accessible name.
- Verify error messages identify the problem and recovery action.
- Test color contrast for normal, hover, disabled, and selected states.