Reviews UI for accessibility issues against WCAG 2.1/2.2 AA. Triggers on "is this accessible?", "check accessibility", or contrast/a11y review requests.
View on GitHubrichtabor/agent-skills
development
January 21, 2026
Select agents to install to:
npx add-skill https://github.com/richtabor/agent-skills/blob/main/skills/accessibility-review/SKILL.md -a claude-code --skill accessibility-reviewInstallation paths:
.claude/skills/accessibility-review/# Accessibility Review ## Overview This skill enables manual accessibility reviews of web content, components, and applications against WCAG 2.1/2.2 Level AA standards. Reviews focus on practical, modern accessibility requirements without being overly pedantic. ## When to Use This Skill Use this skill when the user asks questions like: - "Is this accessible?" - "Can you review the color contrast?" - "Check this component for accessibility issues" - "Does this meet accessibility standards?" - Any request to review, check, or validate accessibility ## Review Process ### 1. Identify the Target Determine what needs to be reviewed: - Specific component (button, form, modal, etc.) - Full page or application - Code file or set of files - Design mockup or screenshot ### 2. Conduct Manual Review Use the WCAG checklist in `references/wcag-checklist.md` to systematically review the target against modern accessibility standards. Focus on the most common and impactful issues: - **Perceivable**: Color contrast, text alternatives, semantic structure - **Operable**: Keyboard navigation, focus management, interactive elements - **Understandable**: Clear labels, error handling, consistent navigation - **Robust**: Valid HTML, ARIA usage, compatibility ### 3. Prioritize Findings Classify each issue as: **Critical** - Blocks users from accessing core functionality: - Missing alt text on meaningful images - Non-keyboard accessible interactive elements - Insufficient color contrast (below 4.5:1 for normal text, 3:1 for large text) - Forms without proper labels - Missing focus indicators - Inaccessible modal/dialog patterns - Auto-playing media without controls **Warning** - Creates friction but doesn't fully block access: - Suboptimal heading hierarchy (skipped levels) - Missing ARIA landmarks - Link text that's unclear out of context - Redundant or unnecessary ARIA - Touch targets smaller than 44x44px - Missing skip links - Non-descriptive error messages ### 4. Stepped Rev