agentleFS
samsam007bsamsam007b/claude-code-standards-kit/skills/accessibility-review/SKILL.md

accessibility-review

Skill2 starsChanged 8 months agoMITView on GitHub

WCAG 2.1 accessibility audit: contrast, keyboard navigation, ARIA, screen readers, forms. Sources: W3C WCAG 2.1 AA, Nielsen 10 heuristics, ARIA Authoring Practices Guide.

18 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use frontend-design.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • BlockSkill

    frontend-design

    Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.

    Also in 4 projects that use this

The file

Files
SKILL.md

/accessibility-review: WCAG 2.1 Accessibility Audit

When to use

  • Audit of a component or page (WCAG 2.1 AA conformance)
  • Review before launching a public feature
  • Verification of a critical form or flow
  • Fixing axe/Lighthouse accessibility errors

WCAG 2.1 AA criteria

Perceivable

  • Text contrast: 4.5:1 minimum (3:1 for large text)
  • Non-text UI contrast (icons, focus borders): 3:1
  • No information conveyed by color alone
  • Alt text on all non-decorative images (alt="" if decorative)

Counting pitfall (a previous run wrongly counted 87 violations): a grep for <Image in a Next.js project matches both the next/image component (needs alt) and the Image/ImageIcon/ImagePlus icon imported from lucide-react (does not need one, it is not an <img> tag). Always check the import source (from 'next/image' vs from 'lucide-react') before counting a hit as a violation. Do not rely on a grep for <Image alone.

  • Captions on videos, transcript for audio
  • Content zooms to 200% without loss of information

Operable (keyboard navigation)

  • All interactive elements reachable by keyboard (Tab, Shift+Tab)
  • Focus visible on all elements (CSS outline not removed)
  • Logical tab order (follows the visual flow)
  • No keyboard trap (modal closes with Escape)
  • Skip links ("Skip to content" as the first element)
  • Keyboard shortcut for repetitive functions

Understandable

  • lang on <html> (and on inline language changes)
  • Explicit labels on all inputs (not placeholder only)
  • Error messages associated via aria-describedby
  • No timeout without warning (WCAG 2.2.1)
  • Confirmation before irreversible actions

Robust (ARIA)

  • ARIA only if semantic HTML is insufficient
  • role, aria-label, aria-describedby consistent
  • Live regions (aria-live="polite") for dynamic updates
  • aria-expanded, aria-selected, aria-checked on custom components
  • Unique IDs in the page (never duplicates)

Custom components (ARIA Authoring Practices)

ComponentRequired ARIA pattern
Modalrole="dialog", aria-modal="true", focus trap, close on Escape
Dropdownrole="listbox" + role="option", aria-selected
Tabsrole="tablist", role="tab", aria-selected, role="tabpanel"
Toastrole="status" or role="alert", aria-live
Accordionaria-expanded, controls/labelledby

Output format

## Accessibility Review: [component/page]

### WCAG 2.1 AA score: [X/100]

### 🔴 Critical non-conformance (legally blocking, EAA 2025)
### 🟡 AA non-conformance to fix
### 🟢 AAA (bonus)

### Code fixes
[Fixed JSX/HTML with ARIA]

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.