better-accessibility
Checks semantics, keyboard interaction, focus, forms and assistive technologies.
- Status
- Observed
- Last reviewed
- 2026-10-10
ID: better-accessibility.
What it does
Walks through the experience first with a keyboard and then with a screen reader, when available. Checks control names and states, native HTML elements, dialog focus, errors associated with fields, dynamic announcements, target sizes and motion. Verifies that content remains reachable with zoom and narrow screens. Contrast and colors are measured with better-colors.
When to use it
Use it to examine a complete flow, form, menu or dialog, especially when the experience must work without a mouse. Reading code can reveal some defects but does not replace testing with a keyboard and screen reader.
How to use it
Ask for it by name, or invoke it with /better-accessibility in Claude Code or $better-accessibility in Codex. Specify the flow, components, states and devices to cover. Request issues ordered by severity, with location, consequence and correction. If you authorize changes, keep them within the project system and retest affected behaviors.
What it delivers
- Findings with severity and location
- Corrections based on semantics and behavior
- Outcome and checks not performed
Example
Check the invitation dialog: opening, initial focus, Tab, Escape, return to the button and email field errors.
Executable instructions
The skill is installed from the source maintained by jakubkrehel; its license applies.
In the workflow
Use the router to choose this capability based on the required outcome.