accessibility-reviewby Anthropic

Accessibility Review Skill.

A Claude Code and Codex skill for design review: wCAG 2.1 AA audit of a design or page: contrast, keyboard, touch targets.

Design Review & Accessibility
Review report

Download OpenDesign View usage guide

anthropics/knowledge-work-plugins · design/skills/accessibility-review/SKILL.mdSKILL.md

--- name: accessibility-review description: 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. --- ## Usage ## Testing Approach ## Output ## Accessibility Audit: [Design/Page Name] ## If Connectors Available ## Tips

Front matter and section headings read from the upstream file on 2026-09-14 · 4,248 characters in full

01 What it does

What the accessibility-review Skill Does in Claude Code and Codex

Summary, workflow and outputs, all read from the skill's SKILL.md.

From the SKILL.mdRead 2026-09-14 · not a recorded run

In the Skill's Own Terms

A WCAG 2.1 AA audit routine for a design or page, triggered by phrases like "audit accessibility" or "check a11y" and taking a Figma URL, URL or description as its argument.

It carries a condensed quick reference of eleven criteria across Perceivable, Operable, Understandable and Robust, covering 4.5:1 contrast for normal text, 3:1 for large text and UI components, keyboard access, visible focus and 44x44 CSS pixel touch targets, plus eight common issues and a five-step testing approach that begins with an automated scan catching roughly 30% of problems. Findings land in a fixed markdown report with severity counts, per-principle tables, contrast, keyboard and screen reader sections and prioritized fixes.

What it produces

A markdown accessibility audit report headed with the design or page name and the WCAG 2.1 AA standard.
A findings section broken into Perceivable, Operable, Understandable and Robust tables of issue, criterion, severity and recommendation.
Dedicated color contrast, keyboard navigation and screen reader tables, including the announced name per element.
An ordered priority fix list splitting critical fixes that block users from major improvements and minor nice-to-haves.

See the example prompt ↗

How It Works

01
Pass in the Thing to Audit
The command takes a Figma URL, a page URL, or a written description as its argument and audits that target.
02
Check the Eleven AA Criteria
The quick reference groups criteria under Perceivable, Operable, Understandable and Robust, each with its success criterion number and threshold.
03
Run the Five Testing Passes
Automated scan, keyboard-only navigation, screen reader testing, contrast verification and 200% zoom, in that order.
04
Write the Fixed Report Shape
One markdown report with a severity summary, a findings table per principle, and separate contrast, keyboard and screen reader tables.
05
Use Connectors When Present
With a design tool connected it reads color values, font sizes and touch targets from Figma; with a project tracker it files per-finding tickets.

02 Find your fit

When to Use the accessibility-review Skill

Use the accessibility-review skill in Claude Code or Codex when the job is design review of this kind. Fit and limits below are taken from the skill's own file.

Good Fit

Reviewing a design for color contrast, keyboard navigation, touch target size or screen reader behavior before handoff.
Auditing a finished page, given you can hand it a URL.
Reading color values, font sizes and touch targets straight out of a Figma file when a design tool is connected.
Turning the audit into tracked work by creating tickets per finding and linking them to existing remediation epics.

Know the Boundaries

Treating the audit as complete coverage: the automated scan misses most issues and real assistive technology testing is still needed.

What to Provide

The design or page reference itselfIt is substituted into the audit instruction as the first argument.

03 Inside the skill

Rules the accessibility-review Skill Gives Claude Code and Codex

7 concrete instructions, defaults and limits the SKILL.md sets for the agent — the part of the file that changes the result.

Hold UI Components to 3:1
Non-text contrast of at least 3:1 is required for UI components and graphics under 1.4.11.
Enforce 44x44 Touch Targets
Touch targets must be at least 44x44 CSS pixels, per criterion 2.5.5.
Make Everything Keyboard Reachable
All functionality has to be available via keyboard (2.1.1) with a visible focus indicator (2.4.7).
Zoom to 200% as a Pass or Fail
The layout is tested at 200% zoom and flagged if it breaks.
Tie Every Finding to a Criterion
Each row in the findings tables names the WCAG criterion alongside the issue, severity and recommendation.
Grade Severity Critical, Major or Minor
Findings are labeled with one of three severities shown as colored markers in the recommendation column.
Start with Contrast and Keyboard
The skill defaults to contrast and keyboard first because they catch the most common and impactful problems.

04 Put it to work

Install accessibility-review in Claude Code or Codex

One npx skills add command, then a first task in your agent and a checklist for the result.

Add accessibility-review to Claude Code, Codex or Your Agent

Run in your project; the installer asks which agent to add it to.

Terminal

npx skills add https://github.com/anthropics/knowledge-work-plugins --skill accessibility-review

Generic skills CLI form for design/skills/accessibility-review/SKILL.md; the repository may document its own path.

Give the Skill a First Design Review Task

Written in the skill's own terms; replace the bracketed parts with your material.

Starter prompt

Audit accessibility for [Figma URL for the checkout flow] before we hand it to engineering. Start with contrast and keyboard access, and flag anything that would block a screen reader user as critical.

Source: written from the SKILL.md in the skill's own terms.

Check the First Result

What the SKILL.md itself says a correct result looks like:

Navigate the whole thing with the keyboard alone.
Test with VoiceOver or NVDA rather than relying on the audit.
Verify the actual contrast ratios against the required values.
Work the priority fixes in order, blocking issues before polish.

In OpenDesign import accessibility-review from its SKILL.md link: Plugins → Add → Skill → Import from link, then pick it in the top bar.

Download OpenDesign Read the quickstart

05 Open source, traceable

Source, License and Verification

Where this page's facts come from, and when they were last checked.

Author: Anthropic
Repository: github.com/anthropics/knowledge-work-plugins Branch main
Skill file: design/skills/accessibility-review/SKILL.md Content checksum recorded at verification; commit 8f877b6
License: Apache-2.0 From LICENSE.
Repository stars: 24,012 GitHub snapshot taken 2026-09-14 for the whole anthropics/knowledge-work-plugins repository, which contains 7 skills in this catalog. Not a rating or usage count for accessibility-review.
Verified by OpenDesign: 2026-09-14 Source file, path, license text and star count were checked. Not bundled in OpenDesign main (checked 2026-08-28); a live run has not been recorded on this page.

Inside the SKILL.md

UsageShows the command form and how the argument is substituted into the audit.
WCAG 2.1 AA Quick ReferenceEleven criteria listed under Perceivable, Operable, Understandable and Robust with thresholds.
Common IssuesEight recurring failures from contrast and form labels to focus traps and time limits.
Testing ApproachFive passes: automated scan, keyboard, screen reader, contrast, 200% zoom.
OutputThe report template with severity summary, principle tables, contrast rows and priority fixes.
If Connectors AvailableWhat changes with a design tool or project tracker connected.
TipsStart with contrast and keyboard, test with real assistive tech, prioritize by impact.

The Skill's Own Description

“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.”

Front-matter description from SKILL.md. The full file is about 4,248 characters. Read the full file on GitHub.

Accessibility Review

Run accessibility-review on a Real Design Review Task.

Download OpenDesign, import accessibility-review from its SKILL.md link, paste the prompt above, and read the plan before the result.

Download OpenDesign Browse all skills

Terminal

npx skills add https://github.com/anthropics/knowledge-work-plugins --skill accessibility-review

What the accessibility-review Skill Does in Claude Code and Codex

In the Skill's Own Terms

How It Works

When to Use the accessibility-review Skill

Good Fit

Know the Boundaries

What to Provide

Rules the accessibility-review Skill Gives Claude Code and Codex

Hold UI Components to 3:1

Enforce 44x44 Touch Targets

Make Everything Keyboard Reachable

Zoom to 200% as a Pass or Fail

Tie Every Finding to a Criterion

Grade Severity Critical, Major or Minor

Start with Contrast and Keyboard