Skill

accessibility-review

Audit designs and code for WCAG 2.1 AA compliance. Trigger with "is this accessible", "accessibility check", "WCAG audit", "can screen readers use this", "color contrast", or when the user asks about making designs or code accessible to all users.

npx claudepluginhub 8gg-git/knowledge-work-plugins --plugin design

Invocation

How this skill is triggered — by the user, by Claude, or both

Slash command

/design:accessibility-review

User invocable

Model invocable

Inline context

Default effort

Context Preview

The summary Claude sees in its skill listing — used to decide when to auto-load this skill

Evaluate designs and implementations against WCAG 2.1 AA standards.

SKILL.md

50 lines · ~396 tokens

Similar Skills

accessibility-audit

Audits web accessibility for WCAG 2.1 AA compliance using checklists across perceptible, operable, comprehensible, robust principles, with issues and code fixes.

alfred-dev

accessibility-review

12.3k

Audits Figma designs or web pages for WCAG 2.1 AA compliance, checking color contrast, keyboard navigation, touch targets, labels, and screen reader support.

design

accessibility-checker

Automatically checks code and elements for accessibility issues when users ask about WCAG compliance or accessibility. Performs focused checks on components, forms, or pages.

cms-cultivator

Stats

Parent stars0

MaintenanceGood

Last CommitFeb 24, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

Stats

Actions

Help us improve

Share bugs, ideas, or general feedback.

Accessibility Review

Evaluate designs and implementations against WCAG 2.1 AA standards.

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?