agentleFS
nisarthnisarth/claude-skills-store/skills/design/accessibility-review/SKILL.md

accessibility-review

Skill1 starsChanged 7 months agoMITView on GitHub

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 shipping. Trigger phrases: "accessibility audit", "check accessibility", "WCAG review", "a11y check", "is this accessible", "color contrast check", "screen reader review", "keyboard navigation test", "touch targets", "accessibility compliance"

19 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

6 rules. 0 are common, 6 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 16 edited versions we read keep these.

  • 6

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Response: Check color contrast for all text elements against backgrounds.

    line 153
  2. Distinctive:

    Response: Check keyboard interaction (Enter to open, Arrow keys to navigate, Escape to close).

    line 157
  3. Distinctive:

    Response: Run the full checklist across all four WCAG principles.

    line 161
  4. Distinctive:

    Do not rely on ARIA alone: Use semantic HTML first (button, not div with role=button).

    line 166
  5. Distinctive:

    Check focus management in SPAs: When content changes without a page reload, focus must be managed explicitly.

    line 168
  6. Distinctive:

    Document known issues: If shipping with known accessibility gaps, document them with a remediation timeline.

    line 172

“Common” is measured: kept by at least 6 in 10 of the 16 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Accessibility Review (WCAG 2.1 AA)

Conduct a structured WCAG 2.1 AA accessibility audit covering color contrast, keyboard navigation, screen reader compatibility, touch targets, and semantic structure.

Workflow

Step 1: Identify the Review Target

Clarify what is being audited:

Target TypeWhat to Review
Design mockupVisual contrast, touch targets, text sizing, focus indicators, layout
Live page/URLFull audit including DOM, ARIA, keyboard, screen reader
ComponentProps for a11y, focus management, state announcements
User flowEnd-to-end task completion with assistive technology

Step 2: Run the Audit by Category

2a: Perceivable

Color Contrast (WCAG 1.4.3, 1.4.6):

ElementForegroundBackgroundRatioRequiredPass/Fail
Body text[Color][Color][X:1]4.5:1
Large text[Color][Color][X:1]3:1
UI component[Color][Color][X:1]3:1
Focus indicator[Color][Color][X:1]3:1

Text and Content:

  • Text can be resized to 200% without loss of content (1.4.4)
  • Color is not the sole means of conveying information (1.4.1)
  • Images have meaningful alt text or are marked decorative (1.1.1)
  • Content does not rely on sensory characteristics alone (1.3.3)
  • Text spacing can be adjusted without breaking layout (1.4.12)

Media:

  • Video has captions (1.2.2)
  • Audio has transcripts (1.2.1)
  • No auto-playing media (1.4.2)

2b: Operable

Keyboard Navigation (2.1.1, 2.1.2):

  • All interactive elements reachable via Tab
  • Tab order follows visual reading order
  • No keyboard traps (user can always Tab away)
  • Focus is visible on all interactive elements (2.4.7)
  • Custom components support expected keyboard patterns (Arrow keys for menus, Escape to close)

Touch Targets (2.5.5 AAA, but recommended for AA):

ElementSizeMinimumPass/Fail
Buttons[WxH]44x44px
Links in body[WxH]44x44px
Form inputs[WxH]44x44px
Close/dismiss[WxH]44x44px

Timing and Motion:

  • No time limits or user can extend (2.2.1)
  • Motion animation can be disabled via prefers-reduced-motion (2.3.3)
  • Nothing flashes more than 3 times per second (2.3.1)

2c: Understandable

Forms and Input:

  • All form inputs have visible labels (3.3.2)
  • Labels are associated with inputs via for/id or wrapping (1.3.1)
  • Error messages identify the field and describe the error (3.3.1)
  • Required fields are indicated without relying solely on color (3.3.2)
  • Input purpose is identified where applicable via autocomplete (1.3.5)

Language and Readability:

  • Page language is set in HTML lang attribute (3.1.1)
  • Navigation is consistent across pages (3.2.3)
  • Interactive elements behave predictably (3.2.2)

2d: Robust

Semantic HTML and ARIA:

  • Headings follow a logical hierarchy (h1 > h2 > h3) (1.3.1)
  • Landmarks used appropriately (nav, main, aside, footer) (1.3.1)
  • ARIA roles, states, and properties are correct (4.1.2)
  • Dynamic content changes are announced (aria-live, aria-relevant) (4.1.3)
  • Custom components expose correct role and state

Screen Reader Testing:

ActionExpected AnnouncementActualPass/Fail
Navigate to [element][Expected][Actual]
Activate [control][Expected][Actual]
Error on [field][Expected][Actual]

Step 3: Prioritize Findings

Classify each issue:

PriorityDefinitionExample
CriticalBlocks access entirely for some usersNo keyboard access to primary action
MajorSignificant barrier, workaround existsForm errors not announced to screen readers
MinorInconvenience, does not block accessTouch target 40px instead of 44px
EnhancementExceeds AA, improves experienceAdding skip links, improving focus management

Step 4: Compile the Report

## Accessibility Audit: [Page/Component/Flow]
Date: [Date] | Standard: WCAG 2.1 AA

### Summary
- **Critical**: [N] issues
- **Major**: [N] issues
- **Minor**: [N] issues
- **Overall**: [Pass / Conditional Pass / Fail]

### Critical Issues
| # | Issue | WCAG Criterion | Location | Recommendation |
|---|-------|---------------|----------|---------------|
| 1 | [Description] | [X.X.X] | [Where] | [Fix] |

### Major Issues
[Same table format]

### Minor Issues
[Same table format]

### What Passes
[List of things that meet or exceed the standard]

### Recommended Enhancements (Beyond AA)
- [Enhancement]: [Benefit]

### Testing Methodology
- Tools used: [axe, Lighthouse, manual, screen reader]
- Browsers: [Chrome, Firefox, Safari]
- Assistive tech: [VoiceOver, NVDA, JAWS]

Examples

Example 1: Design Mockup Review

User: "Is this login page design accessible?" Response: Check color contrast for all text elements against backgrounds. Verify form labels are visible (not placeholder-only). Check touch target sizes for the submit button and links. Flag if error states rely solely on color. Verify focus order makes sense visually.

Example 2: Component Audit

User: "Review this dropdown component for accessibility." Response: Check keyboard interaction (Enter to open, Arrow keys to navigate, Escape to close). Verify ARIA attributes (role=listbox, aria-expanded, aria-selected). Ensure focus management (focus moves into dropdown on open, returns to trigger on close). Test screen reader announcements.

Example 3: Full Page Audit

User: "Run an accessibility audit on our settings page." Response: Run the full checklist across all four WCAG principles. Use automated tools for contrast and semantic structure. Manually test keyboard navigation through every interactive element. Test critical flows with a screen reader. Prioritize findings by severity.

Best Practices

  1. Test with real assistive technology. Automated tools catch 30-40% of issues. Manual testing with screen readers and keyboard-only navigation catches the rest.
  2. Do not rely on ARIA alone. Use semantic HTML first (button, not div with role=button). ARIA is a supplement, not a replacement.
  3. Test at 200% zoom. Many users with low vision zoom rather than using screen readers. Layouts must remain usable at 200%.
  4. Check focus management in SPAs. When content changes without a page reload, focus must be managed explicitly. This is the most common gap in modern web apps.
  5. Color is never the only indicator. Error states, status badges, and required fields must use text, icons, or patterns in addition to color.
  6. Test with prefers-reduced-motion. Users who set this preference should not see animations, transitions, or parallax effects.
  7. Audit early in the design process. Fixing contrast and layout issues in mockups costs minutes. Fixing them in production costs days.
  8. Document known issues. If shipping with known accessibility gaps, document them with a remediation timeline. This demonstrates good faith and helps track progress.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.