What is the accessibility-review skill?
The accessibility-review skill is a slash command skill in Anthropic's knowledge-work-plugins repository. Point it at a Figma URL, a page URL or a description and it returns a WCAG 2.1 AA audit with severity ratings, a contrast table, keyboard and screen reader notes and a short list of priority fixes.
The skill opens with a compact WCAG 2.1 AA quick reference, grouped under perceivable, operable, understandable and a fourth principle for name, role and value, then asks for a Figma URL, a page URL or a description. It audits before handoff.
Its tips are candid about scope. The skill says an automated scan catches about 30% of issues, and that manual testing with VoiceOver or NVDA catches what the audit cannot, so treat the report as a first pass.
Criteria it keeps in view
- Text contrast of at least 4.5:1, or 3:1 for large text, and 3:1 for UI components and graphics.
- Keyboard access for all functionality, a logical focus order and a visible focus indicator.
- Touch targets of at least 44 by 44 CSS pixels.
- Error identification, plus labels or instructions for inputs.
- Name, role and value for every UI component.
How the testing approach runs
- Run an automated scan.
- Navigate with the keyboard only.
- Test with a screen reader, such as VoiceOver or NVDA.
- Verify color contrast.
- Zoom to 200% and see whether the layout breaks.
Fit and limits
Good for
- A pre-handoff pass on a design, before code exists.
- Teams that want findings sorted as critical, major or minor.
- A first review pass. Related: web-accessibility-skill and fixing-accessibility.
Not for
- Certification. It is an agent's review, and the skill itself points to manual assistive technology testing.
- Fixing code. The output is a report. Related: impeccable-audit.
- Standards beyond WCAG 2.1 AA, which is the only level the file names.
Use it with UiChemy
Run this audit on the Figma design before UiChemy Figma to WordPress converts it, so contrast and touch target fixes land in the design. It checks designs and pages, and it does not edit WordPress. Click Get Started on uichemy.com.
How to install Accessibility Review Skill: WCAG 2.1 AA Audits
git clone https://github.com/anthropics/knowledge-work-plugins.gitThe skill file points to CONNECTORS.md for the meaning of its tool placeholders.Clone the repository
Run
git clone https://github.com/anthropics/knowledge-work-plugins.git. The skill sits in design/skills/accessibility-review.Copy the skill folder
Copy design/skills/accessibility-review into the folder your agent reads skills from. The pack shows a single SKILL.md in it.
Optional marketplace route
For Claude Code the README documents
claude plugin marketplace add anthropics/knowledge-work-plugins, followed by installing a plugin, after which skills activate.Run the audit
Type
/accessibility-reviewfollowed by a Figma URL, a page URL or a short description of the screen.
Check that it loaded
Run /accessibility-review on a short description of a sign-up form. The reply should contain a summary with severity counts, four findings tables, contrast, keyboard and screen reader sections and priority fixes.
Key features
- WCAG 2.1 AA referenceA quick reference lists criteria such as 1.4.3 contrast, 2.1.1 keyboard, 2.4.7 focus visible and 4.1.2 name, role and value.
- Three kinds of inputThe argument hint accepts a Figma URL, a page URL or a plain description of the design.
- Findings by principleIssues are tabled under the four WCAG principles, each with a criterion, a severity and a recommendation.
- Severity levelsThe summary counts critical, major and minor issues so a team can triage before fixing.
- Color contrast tableRecords foreground, background, measured ratio and the required ratio for each element, with a pass or fail mark.
- Keyboard navigation tableMaps tab order and the Enter, Space, Escape and arrow key behavior for each interactive element.
- Screen reader tableLists how each element is announced and any problem the announcement exposes.
- Common issues listNames eight frequent failures, including missing form labels, focus traps in modals and auto-playing media without controls.
- Priority fixesEnds with ranked fixes that say who is affected and what is blocked.
- Connector hooksWith a design tool connected it inspects colors, font sizes and touch targets in Figma, and with a project tracker it creates a ticket per finding.
Frequently asked questions
What is the accessibility-review skill?
It is a skill in Anthropic's knowledge-work-plugins repository that audits a design or page for WCAG 2.1 AA compliance. It returns tables of findings, a contrast check, keyboard and screen reader notes and a ranked list of fixes.
How do I install accessibility-review?
Clone anthropics/knowledge-work-plugins and copy the design/skills/accessibility-review folder to where your agent loads skills. The README also documents a marketplace route for Claude Code, using claude plugin marketplace add anthropics/knowledge-work-plugins and then a plugin install.
Does it replace manual accessibility testing?
No. The skill says an automated scan catches about 30% of issues and recommends testing with real assistive technology such as VoiceOver or NVDA. Use the audit as a fast first pass and keep a manual round before release.
Which agents does it work with?
The repository says it is built for Claude Cowork and also compatible with Claude Code. The skill is a plain markdown file, so other agents that read SKILL.md may load it, but the repository does not list them.
Which WCAG level does it check?
Version 2.1 at level AA, which the skill names in its description and its report header. The quick reference covers a selected set of criteria, so it is a focused checklist and not a full reading of the standard.
Can it inspect a Figma file directly?
Yes, if a design tool is connected. The skill then inspects color values, font sizes and touch targets in Figma and checks component ARIA roles and keyboard behavior in the design spec. Without one, it works from your description.
What license does it use?
The repository metadata lists Apache-2.0. The README describes the plugins as markdown and JSON files with no build steps, which you can fork and edit to match your own standards and tools.



