accessibility-reviewer — Claude Code skill: review and install
accessibility-reviewer is a Claude Code skill that reviews interface accessibility using browser and source evidence. It checks semantics, keyboard behavior, contrast, and accessible states.
MIT ★ 529 updated 2026-11-17
npx skills add ShuaiMXu/happyhands --skill accessibility-reviewer -a claude-codeWhat accessibility-reviewer does
The skill identifies barriers that make an interface hard to perceive or operate. Its review uses rendered states, DOM semantics, a keyboard path, and relevant source code.
The output contains evidence, findings, proposed changes, and limitations. Automated checks are kept separate from manual review, and each finding points to an affected control and state. Automated rules cannot certify accessibility conformance. When required evidence or professional review is missing, the skill marks the result needs-evidence.
What it helps with
- find barriers that block keyboard interaction
- inspect DOM semantics and control states
- separate automated checks from manual findings
- prioritize barriers that prevent task completion
Example prompts for the agent
- Review this page's accessibility using browser and source evidence.
- Find keyboard navigation and DOM semantics issues.
- Check contrast and accessible states for the interface controls.
How to install accessibility-reviewer
1Skills CLI (Vercel)
npx skills add ShuaiMXu/happyhands --skill accessibility-reviewer -a claude-code2Manually: put the files in place
~/.claude/skills/accessibility-reviewer/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/accessibility-reviewer/
1Skills CLI (Vercel)
npx skills add ShuaiMXu/happyhands --skill accessibility-reviewer -a codex2Manually: put the files in place
.agents/skills/accessibility-reviewer/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add ShuaiMXu/happyhands --skill accessibility-reviewer -a cursor2Manually: put the files in place
.cursor/skills/accessibility-reviewer/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install ShuaiMXu/happyhands skills/product-design/accessibility-reviewer2Manually: put the files in place
.github/skills/accessibility-reviewer/SKILL.md1Skills CLI (Vercel)
npx skills add ShuaiMXu/happyhands --skill accessibility-reviewer -a gemini-cli2Platform CLI
gemini skills install https://github.com/ShuaiMXu/happyhands --path skills/product-design/accessibility-reviewerManually: put the files in place
.devin/skills/accessibility-reviewer/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about accessibility-reviewer
How do I install accessibility-reviewer in Claude Code?
Run npx skills add ShuaiMXu/happyhands --skill accessibility-reviewer -a claude-code. The skill file is located at ~/.claude/skills/accessibility-reviewer/SKILL.md.
What does accessibility-reviewer do?
It reviews interface semantics, keyboard behavior, contrast, and accessible states using browser and source evidence. Its report includes findings, supporting evidence, proposed updates, and limitations.
Can accessibility-reviewer certify accessibility conformance?
No. Automated rules cannot certify conformance; the skill separates automated checks from manual review and records the limits of its findings.
Source text
SKILL.md · MIT
--- name: accessibility-reviewer description: "Review semantic structure, keyboard behavior, contrast and accessible states using browser and source evidence." --- # Accessibility Reviewer Identify barriers that prevent people from perceiving or operating the product. ## Required evidence - rendered states - DOM semantics - keyboard path - relevant source ## Decisions - Separate automated checks from manual review - Cite the affected control and state - Prioritize task-blocking barriers ## Boundary Automated rules cannot certify accessibility conformance. Return structured evidence, findings, proposed updates and limitations. Use `needs-evidence` when required inputs or professional review are missing. Never invent an Experience Score or promote a project observation into a universal rule.
© ShuaiMXu · MIT · ShuaiMXu/happyhands