keyboard-review
Review keyboard navigation and focus management in an existing interface. Chains: keyboard-navigation, feedback-and-status. Use when testing or reviewing keyboard accessibility specifically, before a release, or when users report keyboard issues.
- Installs
- 73
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/owl-listener/inclusive-design-skills --skill keyboard-review- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads keyboard-review automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
Keyboard Review
A focused review of keyboard accessibility — the single most important interaction requirement. If keyboard doesn't work, screen readers don't work, switch devices don't work, and many motor-impaired users are completely blocked.
Process
Step 1: Tab Through Everything
Starting from the browser address bar, press Tab repeatedly through the entire page. Document:
- Unreachable elements — interactive items that Tab skips
- Wrong order — focus jumps to unexpected locations
- Invisible focus — focus moves but you can't see where it is
- Keyboard traps — focus enters a region and can't leave
Step 2: Test All Components
Using keyboard-navigation, test each component type present:
- Menus: Tab to open, Arrow keys to navigate, Escape to close
- Modals: focus trapped inside, Escape to close, focus returns on close
- Tabs: Arrow keys between tabs, Tab into panel content
- Forms: Tab between fields, Enter to submit
- Custom widgets: appropriate keyboard patterns for the role
Step 3: Test Dynamic Content
When content changes on screen:
- Does focus move to the new content when appropriate?
- Are screen reader users informed of the change?
- When content is removed, does focus move to a logical place?
- Do loading states announce themselves?
Using feedback-and-status, verify all dynamic changes are announced via aria-live regions or focus management.
Step 4: Check Skip Links and Landmarks
- Is "Skip to main content" present and functional?
- Are ARIA landmarks present (banner, navigation, main, contentinfo)?
- Can a keyboard user bypass repeated navigation efficiently?
Output
Deliver a keyboard accessibility report:
- Pass/fail summary — can every task be completed by keyboard?
- Tab order map — the actual focus sequence with issues marked
- Component results — pass/fail for each interactive component
- Dynamic content results — focus management for content changes
- Fix list — prioritised by severity (blocker, major, minor)
FAQ
What does the keyboard-review skill do?
Review keyboard navigation and focus management in an existing interface. Chains: keyboard-navigation, feedback-and-status. Use when testing or reviewing keyboard accessibility specifically, before a release, or when users report keyboard issues.
How do I install keyboard-review?
Run npx skills add https://github.com/owl-listener/inclusive-design-skills --skill keyboard-review in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/keyboard-review/ (personal) or .claude/skills/keyboard-review/ (project).
Which AI agents can use keyboard-review?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is keyboard-review safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains keyboard-review?
It is published by owl-listener in owl-listener/inclusive-design-skills. It has 73 recorded installs.
More from owl-listener/inclusive-design-skills
plain-language-design
owl-listener/inclusive-design-skills
Write and review content for plain language accessibility. Use when writing interface copy, error messages, instructions, onboarding text, help content, legal or medical information, forms, or any user-facing text. Triggers on: plain language, reading level, simplify text, jargon, hard to understand, nobody reads this, unclear copy, rewrite, too complicated, ESL, literacy, readability.
keyboard-navigation
owl-listener/inclusive-design-skills
Design keyboard navigation and focus management for users who cannot or prefer not to use a mouse or touch screen. Use when designing any interactive interface — forms, menus, modals, tabs, carousels, drag-and-drop, data tables, or custom components. Triggers on: keyboard, focus, tab order, focus trap, skip link, arrow keys, keyboard shortcut, can't use mouse, motor disability, switch access, focus indicator, focus ring.
cognitive-load-assessment
owl-listener/inclusive-design-skills
Assess and reduce cognitive load in interfaces, flows, and content. Use when designing or reviewing any multi-step process, complex form, dashboard, decision flow, or information-dense screen. Triggers on: cognitive load, too complex, overwhelmed, too many steps, decision fatigue, confusing, information overload, simplify this flow. Applies to any interface where users must think, decide, or remember.
responsive-review
owl-listener/inclusive-design-skills
Review responsive and flexible layout for accessibility across devices, zoom levels, and orientations. Chains: responsive-accessibility, flexible-typography, information-density. Use when testing an existing interface across screen sizes and zoom levels for accessibility.
user-preference-respect
owl-listener/inclusive-design-skills
Design interfaces that detect and respond to system-level user preferences. Use when implementing dark mode, reduced motion, high contrast, text scaling, or any user preference that affects how the interface renders. Triggers on: user preference, system preference, prefers-reduced-motion, prefers-contrast, prefers-color-scheme, forced-colors, media query, user settings, system settings, accessibility settings, OS settings.
error-prevention-recovery
owl-listener/inclusive-design-skills
Design error prevention, error messages, and recovery flows for cognitive accessibility. Use when designing forms, checkout flows, account creation, settings, data entry, or any flow where users can make mistakes. Triggers on: error handling, error messages, form errors, validation, users make mistakes, users abandon, error recovery, undo, forgiving design.
Popular code quality & workflow skills
grill-me
mattpocock/skills
A relentless interview to sharpen a plan or design.
improve-codebase-architecture
mattpocock/skills
Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.
handoff
mattpocock/skills
Compact the current conversation into a handoff document for another agent to pick up.
domain-modeling
mattpocock/skills
Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a GLOSSARY.md, or recording or editing an ADR.
codebase-design
mattpocock/skills
Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.
diagnosing-bugs
mattpocock/skills
Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.