$ ~/registry/skill/anthropics-design-skills-accessibility-review

SKILL

accessibility-review

Name: accessibility-review
Author: anthropics

Audit designs or pages for WCAG 2.1 AA accessibility issues.

Stars

★ 22,528

Source

GitHub

Updated

2026-07-11

// securityCaution

Prompt only, no code
Open source

Summary

This skill appears to be an open-source, prompt-only accessibility review template. It requires no secrets and declares no network endpoints or local system execution, so overall risk is low based on the provided materials, with only limited community adoption and unclear maintenance to note.

CredentialsLow risk

The materials explicitly state that no keys or environment variables are required. There is no request for API tokens, account credentials, or sensitive scopes, so credential leakage and abuse risk is low.

Network egressLow risk

No remote host is declared, and the content appears to be a local prompt/checklist template. The materials do not describe sending user design or page data to any third-party service.

Code executionLow risk

The system flags it as prompt-only. The README only describes how to trigger an accessibility audit and the expected output format, with no indication of script execution, process spawning, shell access, or other system capabilities.

Data accessLow risk

The materials do not declare any ability to read or write local files, databases, browser sessions, or external resources. Its function looks like a text-based review template over user-provided content, with no sign of excessive data access.

Supply chainCaution

The source is an open-source GitHub repository, and the code is auditable, which is a strong risk-reducing factor. However, the license is not stated, stars are 0, and maintenance status is unknown, so the supply-chain profile is acceptable but warrants some attention to future maintenance and repository integrity.

Recommendations

Review the skill files directly in the repository to confirm it is truly prompt-only and has no hidden dependencies.
Verify the repository license and recent maintenance status before adoption.
If the platform supports it, restrict the skill to only the design/page content explicitly provided by the user.

Audited by: gpt-5.4 · 2026-06-17

// install

Copy the install command and let the AI configure it · recommended for beginners

Please install the "accessibility-review" skill from askskill:
1. Download https://raw.githubusercontent.com/anthropics/knowledge-work-plugins/main/design/skills/accessibility-review/SKILL.md
2. Save it as ~/.claude/skills/accessibility-review/SKILL.md
3. Reload skills and tell me it's ready

// download

Download SKILL.mdInstall manifest ↗

// examples

Audit a landing page for accessibility issues

Prompt

Run a WCAG 2.1 AA accessibility audit on this landing page. Focus on color contrast, keyboard navigation, touch target sizes, form labels, and screen reader readability. List issues by severity and suggest fixes.

Expected

A severity-ranked accessibility issue list with violation details, affected areas, and actionable fixes.

Check UI components before design handoff

Prompt

Review this UI component set for WCAG 2.1 AA compliance. Focus on text/background contrast, focus states, disabled-state clarity, target size, and whether icon buttons have accessible names.

Expected

A component-level accessibility assessment highlighting noncompliant elements and design adjustments.

Verify keyboard and screen reader accessibility

Prompt

Check whether this page works well with keyboard navigation and screen readers. Review focus order, skip links, semantic structure, image alt text, and announcements for dynamic content.

Expected

A pre-handoff report summarizing keyboard and screen reader risks with fix priorities.

// docs

/accessibility-review

If you see unfamiliar placeholders or need to check which tools are connected, see CONNECTORS.md.

Audit a design or page for WCAG 2.1 AA accessibility compliance.

Usage

/accessibility-review $ARGUMENTS

Audit for accessibility: @$1

WCAG 2.1 AA Quick Reference

Perceivable

1.1.1 Non-text content has alt text
1.3.1 Info and structure conveyed semantically
1.4.3 Contrast ratio >= 4.5:1 (normal text), >= 3:1 (large text)
1.4.11 Non-text contrast >= 3:1 (UI components, graphics)

Operable

2.1.1 All functionality available via keyboard
2.4.3 Logical focus order
2.4.7 Visible focus indicator
2.5.5 Touch target >= 44x44 CSS pixels

Understandable

3.2.1 Predictable on focus (no unexpected changes)
3.3.1 Error identification (describe the error)
3.3.2 Labels or instructions for inputs

Robust

4.1.2 Name, role, value for all UI components

Common Issues

Insufficient color contrast
Missing form labels
No keyboard access to interactive elements
Missing alt text on meaningful images
Focus traps in modals
Missing ARIA landmarks
Auto-playing media without controls
Time limits without extension options

Testing Approach

Automated scan (catches ~30% of issues)
Keyboard-only navigation
Screen reader testing (VoiceOver, NVDA)
Color contrast verification
Zoom to 200% — does layout break?

Output

## Accessibility Audit: [Design/Page Name]
**Standard:** WCAG 2.1 AA | **Date:** [Date]

### Summary
**Issues found:** [X] | **Critical:** [X] | **Major:** [X] | **Minor:** [X]

### Findings

#### Perceivable
| # | Issue | WCAG Criterion | Severity | Recommendation |
|---|-------|---------------|----------|----------------|
| 1 | [Issue] | [1.4.3 Contrast] | 🔴 Critical | [Fix] |

#### Operable
| # | Issue | WCAG Criterion | Severity | Recommendation |
|---|-------|---------------|----------|----------------|
| 1 | [Issue] | [2.1.1 Keyboard] | 🟡 Major | [Fix] |

#### Understandable
| # | Issue | WCAG Criterion | Severity | Recommendation |
|---|-------|---------------|----------|----------------|
| 1 | [Issue] | [3.3.2 Labels] | 🟢 Minor | [Fix] |

#### Robust
| # | Issue | WCAG Criterion | Severity | Recommendation |
|---|-------|---------------|----------|----------------|
| 1 | [Issue] | [4.1.2 Name, Role, Value] | 🟡 Major | [Fix] |

### Color Contrast Check
| Element | Foreground | Background | Ratio | Required | Pass? |
|---------|-----------|------------|-------|----------|-------|
| [Body text] | [color] | [color] | [X]:1 | 4.5:1 | ✅/❌ |

### Keyboard Navigation
| Element | Tab Order | Enter/Space | Escape | Arrow Keys |
|---------|-----------|-------------|--------|------------|
| [Element] | [Order] | [Behavior] | [Behavior] | [Behavior] |

### Screen Reader
| Element | Announced As | Issue |
|---------|-------------|-------|
| [Element] | [What SR says] | [Problem if any] |

### Priority Fixes
1. **[Critical fix]** — Affects [who] and blocks [what]
2. **[Major fix]** — Improves [what] for [who]
3. **[Minor fix]** — Nice to have

If Connectors Available

If ~~design tool is connected:

Inspect color values, font sizes, and touch targets directly from Figma
Check component ARIA roles and keyboard behavior in the design spec

If ~~project tracker is connected:

Create tickets for each accessibility finding with severity and WCAG criterion
Link findings to existing accessibility remediation epics

Tips

Start with contrast and keyboard — These catch the most common and impactful issues.
Test with real assistive technology — My audit is a great start, but manual testing with VoiceOver/NVDA catches things I can't.
Prioritize by impact — Fix issues that block users first, polish later.