Web Interface Guidelines Reviewer
vercel-labs/openreview
Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my…
Design keyboard navigation and focus management for users who cannot or prefer not to use a mouse or touch screen.
Install Keyboard Navigation
$ npx skills add Owl-Listener/inclusive-design-skills --skill keyboard-navigation -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Owl-Listener/inclusive-design-skills keyboard-navigation --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/Owl-Listener/inclusive-design-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/inclusive-interaction/skills/keyboard-navigation .claude/skills/keyboard-navigation && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "keyboard-navigation" agent skill from https://github.com/Owl-Listener/inclusive-design-skills/tree/main/inclusive-interaction/skills/keyboard-navigation into .claude/skills/keyboard-navigation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "keyboard-navigation", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/Owl-Listener/inclusive-design-skills/tree/main/inclusive-interaction/skills/keyboard-navigationType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add Owl-Listener/inclusive-design-skills --skill keyboard-navigation -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Owl-Listener/inclusive-design-skills keyboard-navigation --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Owl-Listener/inclusive-design-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/inclusive-interaction/skills/keyboard-navigation .agents/skills/keyboard-navigation && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "keyboard-navigation" agent skill from https://github.com/Owl-Listener/inclusive-design-skills/tree/main/inclusive-interaction/skills/keyboard-navigation into .agents/skills/keyboard-navigation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "keyboard-navigation", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Owl-Listener/inclusive-design-skills --skill keyboard-navigation -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Owl-Listener/inclusive-design-skills keyboard-navigation --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Owl-Listener/inclusive-design-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/inclusive-interaction/skills/keyboard-navigation .cursor/skills/keyboard-navigation && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "keyboard-navigation" agent skill from https://github.com/Owl-Listener/inclusive-design-skills/tree/main/inclusive-interaction/skills/keyboard-navigation into .cursor/skills/keyboard-navigation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "keyboard-navigation", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/Owl-Listener/inclusive-design-skills.git --path inclusive-interaction/skills/keyboard-navigation--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add Owl-Listener/inclusive-design-skills --skill keyboard-navigation -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Owl-Listener/inclusive-design-skills keyboard-navigation --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Owl-Listener/inclusive-design-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/inclusive-interaction/skills/keyboard-navigation .gemini/skills/keyboard-navigation && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "keyboard-navigation" agent skill from https://github.com/Owl-Listener/inclusive-design-skills/tree/main/inclusive-interaction/skills/keyboard-navigation into .gemini/skills/keyboard-navigation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "keyboard-navigation", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install Owl-Listener/inclusive-design-skills keyboard-navigationInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add Owl-Listener/inclusive-design-skills --skill keyboard-navigation -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Owl-Listener/inclusive-design-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/inclusive-interaction/skills/keyboard-navigation .github/skills/keyboard-navigation && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "keyboard-navigation" agent skill from https://github.com/Owl-Listener/inclusive-design-skills/tree/main/inclusive-interaction/skills/keyboard-navigation into .github/skills/keyboard-navigation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "keyboard-navigation", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Owl-Listener/inclusive-design-skills --skill keyboard-navigation -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install Owl-Listener/inclusive-design-skills keyboard-navigation --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Owl-Listener/inclusive-design-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/inclusive-interaction/skills/keyboard-navigation .opencode/skills/keyboard-navigation && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "keyboard-navigation" agent skill from https://github.com/Owl-Listener/inclusive-design-skills/tree/main/inclusive-interaction/skills/keyboard-navigation into .opencode/skills/keyboard-navigation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "keyboard-navigation", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
keyboard-navigation- GitHub stars
- 104
- Token cost
- ~985 tokens
- SKILL.md length
- 511 words
- Files
- 1
- Skills in repo
- 55
- Repo updated
- First seen
- Licence
- MIT
At a glance
Design keyboard navigation and focus management for users who cannot or prefer not to use a mouse or touch screen.
- Designing any interactive interface — forms
- SKILL.md covers Who This Is For, Core Principles, Keyboard Patterns by Component and Skip Links, plus 1 more section
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Custom components
What it does
Keyboard Navigation is an agent skill from 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.
Its SKILL.md is about 990 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Frontend & Design, covering Accessibility. The repository describes itself as: Inclusive design skills for AI coding agents — from cognitive accessibility to adaptive interfaces, inclusive research, and accessibility decision-making. The licence is MIT.
When your agent uses it
- Designing any interactive interface — forms
- Custom components
- Keyboard shortcut
- Motor disability
Example prompts
- “/keyboard-navigation”
What it can do on your machine
Read from SKILL.md and the folder at commit 6e0740f. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Keyboard Navigation loads about 985 tokens when it runs. Until then it costs about 111 tokens; SKILL.md has 511 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from Owl-Listener/inclusive-design-skills at commit 6e0740f, republished under its MIT licence (© Owl-Listener). 511 words, ~985 tokens.
Download SKILL.mdSave it as
.claude/skills/keyboard-navigation/SKILL.md (or your agent's skills folder).- name
- keyboard-navigation
- description
- 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.
Keyboard Navigation
Design interactions so that every task can be completed using only a keyboard. This is non-negotiable — it's the foundation of all interaction accessibility.
Who This Is For
- People with motor disabilities who cannot use a mouse
- People using switch devices or mouth sticks
- Screen reader users (keyboard is their primary input)
- Power users who prefer keyboard for speed
- Anyone with a temporarily injured hand or arm
Core Principles
Everything Must Be Reachable
- Every interactive element must be focusable via Tab key
- Focus order must follow the visual reading order (left to right, top to bottom in LTR languages)
- No element should be reachable only by mouse hover or click
- Custom components need explicit tabindex and keyboard handlers
Focus Must Be Visible
- Focus indicator must be visible on every interactive element
- Minimum: 2px solid outline with 3:1 contrast against background
- Never use outline: none or outline: 0 without a visible replacement
- Focus style should be consistent across the entire interface
- Test: can you always see which element is focused?
Focus Must Be Managed
- When a modal opens, move focus into the modal
- When a modal closes, return focus to the element that opened it
- When content is deleted, move focus to a logical next element
- When a page section updates dynamically, manage focus appropriately
- Never trap focus unintentionally (only trap inside open modals)
Keyboard Patterns by Component
Navigation Menus
- Tab moves between top-level items
- Arrow keys move within a dropdown
- Enter/Space activates a menu item
- Escape closes an open dropdown and returns focus to trigger
Tabs
- Tab moves to the active tab panel, not through all tabs
- Arrow keys move between tabs
- Enter/Space activates a tab (if not automatic)
Modals / Dialogs
- Focus moves to first focusable element inside modal on open
- Tab cycles only within the modal (focus trap)
- Escape closes the modal
- Focus returns to trigger element on close
Show full SKILL.md (200 more words)Show less
Forms
- Tab moves between fields in logical order
- Error messages are focusable or announced
- Submit via Enter key on the last field or a visible button
- Required field indicators are not conveyed by colour alone
Drag and Drop
- Always provide a keyboard alternative (move up/down buttons, select-and-place, or arrow key reordering)
- Announce the current position and available actions
Carousels / Sliders
- Arrow keys move between items
- Provide visible previous/next buttons
- Pause autoplay on focus or hover
- Announce current position ("Item 2 of 5")
Skip Links
Every page should have a "Skip to main content" link as the first focusable element. This lets keyboard users bypass repeated navigation.
- Visible on focus (can be visually hidden until focused)
- Links to the main content area via an anchor
- Consider additional skip links for long pages ("Skip to search", "Skip to footer")
Assessment Checklist
- Every interactive element is reachable via Tab
- Focus order matches visual order
- Focus indicator is visible on every element (2px, 3:1 contrast)
- Modals trap focus and return it on close
- All custom components have keyboard handlers
- Drag-and-drop has a keyboard alternative
- Skip link is present and functional
- No keyboard traps exist anywhere in the interface
- Dynamic content changes manage focus appropriately
© Owl-Listener, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in inclusive-interaction/skills/keyboard-navigation of Owl-Listener/inclusive-design-skills.
Open the folder on GitHubat commit 6e0740f
Compare with similar skills
Keyboard Navigation next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Keyboard Navigation this skillOwl-Listener/inclusive-design-skills | 104 | — | ~985 | Automated safety check: Pass | MIT | |
| Web Interface Guidelines Reviewervercel-labs/openreview | 1.7k | 97 repos | ~308 | Automated safety check: Pass | None | |
| Accessibility Reviewmarkmead/hyperui | 12k | 1 repos | ~1.1k | Automated safety check: Pass | MIT | |
| Web Animation DesignbaptisteArno/typebot.io | 11k | 2 repos | ~2.7k | Automated safety check: Pass | Custom licence | |
| Accessibility Fixeribelick/ui-skills | 9.5k | 4 repos | ~1.2k | Automated safety check: Pass | MIT | |
| Wcag Audit PatternsvmDeshpande/ai-agent-automation | 178 | 11 repos | ~610 | Automated safety check: Pass | Apache-2.0 |
Similar skills
- Official
Accessibility Review
markmead/hyperui
Run a WCAG 2.1 AA accessibility audit on a design or page. An agent skill from markmead/hyperui.
Web Animation Design
baptisteArno/typebot.io
Guides easing, timing and animation choices for UI motion, based on a web animation course, and reviews existing animations in a before-and-after table.
Accessibility Fixer
ibelick/ui-skills
Audits and fixes HTML accessibility problems such as ARIA labels, keyboard navigation, focus management, contrast and form errors with minimal changes.
Wcag Audit Patterns
vmDeshpande/ai-agent-automation
Conduct WCAG 2.2 accessibility audits with automated testing, manual verification, and remediation guidance.
Baseline UI
ibelick/ui-skills
Applies a fixed set of UI rules for stack, components, interaction, animation, typography and layout, or reviews a file against them with concrete fixes.
More from Owl-Listener/inclusive-design-skills
All 55 skills in this repoAssistive Technology Scenarios
Owl-Listener/inclusive-design-skills
Writes usage scenarios, use cases and storyboards that show real people using screen readers, switches, voice control and other assistive technology to finish tasks.
Error Prevention and Recovery
Owl-Listener/inclusive-design-skills
Designs forgiving forms and flows: prevent input errors, write messages that say what happened and what to do, and add undo, confirmation and recovery paths.
Accessible Heading Structure
Owl-Listener/inclusive-design-skills
Designs heading hierarchies for screen reader navigation and cognitive accessibility on pages, articles, dashboards and forms.
Ability Spectrum Mapping
Owl-Listener/inclusive-design-skills
Maps a feature across a range of vision, hearing, motor and cognitive ability to find where the design starts to fail, and to explain accessibility scope to stakeholders.
Accessibility Debt Tracking
Owl-Listener/inclusive-design-skills
Track and manage accessibility debt — known accessibility issues that have been deferred.
Accessibility Testing Strategy
Owl-Listener/inclusive-design-skills
Plan what to test, how to test, and who should test for accessibility.
Related
Categories
Questions about Keyboard Navigation
What does Keyboard Navigation do?
Design keyboard navigation and focus management for users who cannot or prefer not to use a mouse or touch screen. Keyboard Navigation is an agent skill from 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.
When should I use Keyboard Navigation?
Keyboard Navigation fits situations like: designing any interactive interface — forms; custom components; keyboard shortcut; motor disability.
How do I install Keyboard Navigation in Claude Code?
Run `npx skills add Owl-Listener/inclusive-design-skills --skill keyboard-navigation -a claude-code`. Or copy the skill folder (inclusive-interaction/skills/keyboard-navigation in Owl-Listener/inclusive-design-skills) into .claude/skills/keyboard-navigation in your project. Claude Code loads it when a task matches its description.
How do I install Keyboard Navigation in Codex?
Run `npx skills add Owl-Listener/inclusive-design-skills --skill keyboard-navigation -a codex`. Or copy the skill folder (inclusive-interaction/skills/keyboard-navigation in Owl-Listener/inclusive-design-skills) into .agents/skills/keyboard-navigation in your project. Codex loads it when a task matches its description.
Can I use Keyboard Navigation in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Owl-Listener/inclusive-design-skills --skill keyboard-navigation -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/keyboard-navigation, .gemini/skills/keyboard-navigation, .github/skills/keyboard-navigation and .opencode/skills/keyboard-navigation in your project.
What does Keyboard Navigation need to run?
SKILL.md names no scripts, command-line tools or credentials: Keyboard Navigation is instructions for the agent only.
Does Keyboard Navigation access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Keyboard Navigation safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Keyboard Navigation use?
Keyboard Navigation is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Keyboard Navigation use?
About 985 tokens (SKILL.md is roughly 3.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Keyboard Navigation?
Skills that share tags, products or a category with Keyboard Navigation: Web Interface Guidelines Reviewer (vercel-labs/openreview, 1.7k stars), Accessibility Review (markmead/hyperui, 12k stars), Web Animation Design (baptisteArno/typebot.io, 11k stars) and Accessibility Fixer (ibelick/ui-skills, 9.5k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Keyboard Navigation?
Owl-Listener (a GitHub user) maintains it in Owl-Listener/inclusive-design-skills, which has 104 GitHub stars. The repository holds 55 skills in this directory. The repository was last updated on June 9, 2026.
Source: Owl-Listener/inclusive-design-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.