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…
Review keyboard navigation and focus management in an existing interface.
Install Keyboard Review
$ npx skills add Owl-Listener/inclusive-design-skills --skill keyboard-review -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Owl-Listener/inclusive-design-skills keyboard-review --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-review .claude/skills/keyboard-review && 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-review" agent skill from https://github.com/Owl-Listener/inclusive-design-skills/tree/main/inclusive-interaction/skills/keyboard-review into .claude/skills/keyboard-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "keyboard-review", 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-reviewType 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-review -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Owl-Listener/inclusive-design-skills keyboard-review --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-review .agents/skills/keyboard-review && 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-review" agent skill from https://github.com/Owl-Listener/inclusive-design-skills/tree/main/inclusive-interaction/skills/keyboard-review into .agents/skills/keyboard-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "keyboard-review", 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-review -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Owl-Listener/inclusive-design-skills keyboard-review --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-review .cursor/skills/keyboard-review && 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-review" agent skill from https://github.com/Owl-Listener/inclusive-design-skills/tree/main/inclusive-interaction/skills/keyboard-review into .cursor/skills/keyboard-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "keyboard-review", 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-review--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-review -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Owl-Listener/inclusive-design-skills keyboard-review --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-review .gemini/skills/keyboard-review && 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-review" agent skill from https://github.com/Owl-Listener/inclusive-design-skills/tree/main/inclusive-interaction/skills/keyboard-review into .gemini/skills/keyboard-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "keyboard-review", 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-reviewInstalls 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-review -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-review .github/skills/keyboard-review && 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-review" agent skill from https://github.com/Owl-Listener/inclusive-design-skills/tree/main/inclusive-interaction/skills/keyboard-review into .github/skills/keyboard-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "keyboard-review", 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-review -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-review --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-review .opencode/skills/keyboard-review && 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-review" agent skill from https://github.com/Owl-Listener/inclusive-design-skills/tree/main/inclusive-interaction/skills/keyboard-review into .opencode/skills/keyboard-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "keyboard-review", 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-review- GitHub stars
- 105
- Token cost
- ~585 tokens
- SKILL.md length
- 286 words
- Files
- 1
- Skills in repo
- 55
- Repo updated
- First seen
- Licence
- MIT
At a glance
Review keyboard navigation and focus management in an existing interface.
- Works in 4 steps: Tab Through Everything → Test All Components → Test Dynamic Content → …
- Reviewing keyboard accessibility specifically
- SKILL.md covers Process and Output
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Keyboard Review is an agent skill from Owl-Listener/inclusive-design-skills. 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.
Its SKILL.md is about 590 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
- Reviewing keyboard accessibility specifically
- Before a release
- Users report keyboard issues
Example prompts
- “/keyboard-review”
Workflow steps
4 steps, taken from the step headings in SKILL.md.
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 Review loads about 585 tokens when it runs. Until then it costs about 66 tokens; SKILL.md has 286 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). 286 words, ~585 tokens.
Download SKILL.mdSave it as
.claude/skills/keyboard-review/SKILL.md (or your agent's skills folder).- name
- keyboard-review
- description
- 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.
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)
© 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-review of Owl-Listener/inclusive-design-skills.
Open the folder on GitHubat commit 6e0740f
Compare with similar skills
Keyboard Review 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 Review this skillOwl-Listener/inclusive-design-skills | 105 | — | ~585 | 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.6k | 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 Review
What does Keyboard Review do?
Review keyboard navigation and focus management in an existing interface. Keyboard Review is an agent skill from Owl-Listener/inclusive-design-skills. Review keyboard navigation and focus management in an existing interface.
When should I use Keyboard Review?
Keyboard Review fits situations like: reviewing keyboard accessibility specifically; before a release; users report keyboard issues.
How do I install Keyboard Review in Claude Code?
Run `npx skills add Owl-Listener/inclusive-design-skills --skill keyboard-review -a claude-code`. Or copy the skill folder (inclusive-interaction/skills/keyboard-review in Owl-Listener/inclusive-design-skills) into .claude/skills/keyboard-review in your project. Claude Code loads it when a task matches its description.
How do I install Keyboard Review in Codex?
Run `npx skills add Owl-Listener/inclusive-design-skills --skill keyboard-review -a codex`. Or copy the skill folder (inclusive-interaction/skills/keyboard-review in Owl-Listener/inclusive-design-skills) into .agents/skills/keyboard-review in your project. Codex loads it when a task matches its description.
Can I use Keyboard Review 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-review -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-review, .gemini/skills/keyboard-review, .github/skills/keyboard-review and .opencode/skills/keyboard-review in your project.
What does Keyboard Review need to run?
SKILL.md names no scripts, command-line tools or credentials: Keyboard Review is instructions for the agent only.
Does Keyboard Review 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 Review 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 Review use?
Keyboard Review 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 Review use?
About 585 tokens (SKILL.md is roughly 2.3k 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 Review?
Skills that share tags, products or a category with Keyboard Review: 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.6k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Keyboard Review?
Owl-Listener (a GitHub user) maintains it in Owl-Listener/inclusive-design-skills, which has 105 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.