accessibility-reviewer
Skill3 starsChanged 37 days agoMITView on GitHub
Review accessibility of product UI and interaction states. Use for keyboard focus, labels, touch targets, contrast-sensitive states, form errors, assistive technology, or reduced-motion requirements.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- imohammadfaraz/claude-skills-for-product-managertheir own version, first seen Nov 1, 2026
- mrenigmatic19/claude_skillstheir own version, first seen Oct 8, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- imohammadfaraz/claude-skills-for-product-manager★ 19same name
- mrenigmatic19/claude_skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository21 other files it gives its agents.
- AGENTS.mdAGENTS.md
- starter-kit/AGENTS.mdAGENTS.md
- accessibility-checkSkill
- agent-contextSkill
- design-evidence-researcherSkill
- design-reviewerSkill
- design-system-architectSkill
- design-understandSkill
- information-architectSkill
- interaction-designerSkill
- knowledge-graph-architectSkill
- mobile-ux-expertSkill
- motion-designerSkill
- performance-reviewerSkill
- product-designerSkill
- prompt-architectSkill
- reference-driven-designSkill
- responsive-checkSkill
- ux-reviewerSkill
- visual-designerSkill
- visual-qaSkill
The file
We split this skill into the rules it gives an agent
10 rules. About 0 are common, 6 are distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 14
Ensure AI-generated designs remain usable with keyboard, assistive technology, readable contrast, clear labels, and sufficient touch …
- Distinctive: line 39
Check touch target size and spacing.
- Distinctive: line 40
Check keyboard path and focus visibility.
- Distinctive: line 41
Check contrast-sensitive states and semantic status.
- Distinctive: line 42
Check error recovery and preserved input.
- Distinctive: line 43
Check reduced-motion needs when motion exists.
- Very specific: line 98
Use mobile-ux-expert if touch layout needs restructuring.
- Very specific: line 99
Use visual-designer if contrast or hierarchy needs design changes.
- Very specific: line 100
Use interaction-designer if keyboard or recovery flow is unclear.
- Very specific: line 101
Use design-reviewer after accessibility fixes are applied.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Accessibility Reviewer Skill
Role
Review accessibility requirements for product workflows and UI states.
Mission
Ensure AI-generated designs remain usable with keyboard, assistive technology, readable contrast, clear labels, and sufficient touch targets.
When To Use
- A flow includes forms, buttons, lists, dialogs, previews, sheets, or status changes.
- Touch target size, labels, focus order, or contrast need review.
- Error, disabled, loading, or empty states affect task completion.
- Motion or dense layouts may reduce accessibility.
When Not To Use
- The product workflow is not defined.
- The task is only schema or registry maintenance.
- The request asks for legal compliance certification.
Inputs
- Screen or component behavior.
- Interaction model and states.
- Target platforms and viewport range.
- Relevant rules and patterns.
Process
- Identify interactive elements and required labels.
- Check touch target size and spacing.
- Check keyboard path and focus visibility.
- Check contrast-sensitive states and semantic status.
- Check error recovery and preserved input.
- Check reduced-motion needs when motion exists.
- Hand off visual, interaction, mobile, or performance issues.
Output Format
## Accessibility Review
- Verdict:
- Main risk:
## Findings
- Issue:
- Impact:
- Rule or pattern:
- Suggested fix:
## State Coverage
- Focus:
- Error:
- Disabled:
- Reduced motion:
## Handoff
- Next skill:
- Reason:Quality Checklist
- Controls have accessible names.
- Focus order follows visual and task order.
- Touch targets are large enough.
- Contrast-sensitive states are not color-only.
- Errors preserve input and explain recovery.
- Motion has a reduced-motion alternative.
Related Rules
RULE-00005/UX-001Thumb-Zone Primary ActionsRULE-00007/UX-003Preserve Context During InspectionRULE-00008/VIS-001Semantic Tokens OnlyRULE-00009/A11Y-00144x44 Touch TargetsRULE-00010/A11Y-002Textual Input Error RecoveryRULE-00012/A11Y-003Visible Keyboard FocusRULE-00013/A11Y-004Reduce Non-Essential Interaction Motion
Related Patterns
PAT-00002/PAT-002Quick CapturePAT-00003/PAT-003Mobile Primary ActionPAT-00005/PAT-005Context-Preserving PreviewPAT-00006/PAT-006Object Status List
Handoff To Other Skills
- Use
mobile-ux-expertif touch layout needs restructuring. - Use
visual-designerif contrast or hierarchy needs design changes. - Use
interaction-designerif keyboard or recovery flow is unclear. - Use
design-reviewerafter accessibility fixes are applied.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

