Run a WCAG 2.1 AA accessibility audit on a design or page. Trigger with "audit accessibility", "check a11y", "is this accessible?", or when reviewing a design for color contrast, keyboard navigation, touch target size, or screen reader behavior before handoff.
The accessibility-review skill performs comprehensive WCAG 2.1 AA accessibility audits on designs and web pages. It identifies barriers that prevent users with disabilities from accessing digital content, checking for issues across perceivability, operability, understandability, and robustness. The skill can be triggered with natural commands like "audit accessibility", "check a11y", or "is this accessible?", making it easy to integrate accessibility checks into design review workflows.
This skill evaluates multiple accessibility dimensions including color contrast ratios, keyboard navigation patterns, touch target sizes, screen reader compatibility, and semantic HTML structure. It goes beyond automated scanning by combining programmatic checks with manual testing guidelines for keyboard-only navigation, screen reader testing with tools like VoiceOver and NVDA, and layout verification at 200% zoom. The audit covers the most common accessibility violations including insufficient contrast, missing form labels, keyboard access gaps, and missing alternative text.
Designers, developers, and QA teams use this skill during design handoff, pre-launch reviews, and ongoing compliance monitoring. It generates structured audit reports with severity-ranked findings, specific WCAG criterion references, and actionable recommendations. When integrated with design tools like Figma or project trackers, it can automatically inspect design specifications and create remediation tickets, streamlining the accessibility compliance workflow across teams.
This skill audits against WCAG 2.1 AA (Web Content Accessibility Guidelines 2.1, Level AA), which is the most commonly required compliance standard for web accessibility.
Yes, the skill can audit Figma URLs for design-phase accessibility, live URLs for deployed pages, or work from descriptions of the interface being reviewed.
No, automated scanning typically catches only about 30% of accessibility issues. This skill combines automated checks with manual testing guidelines for keyboard navigation, screen reader compatibility, and visual inspection to provide comprehensive coverage.
When design tools like Figma are connected, the skill can inspect color values, font sizes, and touch targets directly. When project trackers are connected, it can automatically create tickets for findings with severity levels and WCAG references.
Issues are categorized as Critical (blocks access for users with disabilities), Major (significantly impacts usability), or Minor (nice-to-have improvements), helping teams prioritize remediation work.
Quick Setup:
.claude/skills/Repository
anthropics/knowledge-work-plugins