Accessibility Audit (WCAG) skill for Claude and Codex

Accessibility Audit (WCAG) as an AI skill. It asks for What is being audited, Markup or description, Design colours and 3 more, then does the rest. Free to…

Install it once and Claude or Codex runs it for you. When your request matches, your AI loads the skill, asks for anything it is missing, and works through the template itself. Prefer to fill it in by hand? See the full prompt template.

Download the skill (.zip) · View SKILL.md

When it is used

Use when a page, component or design needs a WCAG 2.1 AA check covering contrast, keyboard use, focus, labels and screen reader behaviour. Do not use for fixing a single known bug or running an automated scanner. Related topics: design, coding.

What it will ask you for

• What is being audited (free text, e.g. "Page or component name")
• Markup or description (longer free text)
• Design colours (longer free text)
• Platform (choose one: Website, Web app, Mobile web, Design mockup)
• Assistive tech in scope (choose any: Screen reader, Keyboard only, Voice control, Zoom, Reduced motion)
• Audience notes (longer free text)

How it works

1. Compute the contrast ratio for every supplied colour pair and list each one that misses its threshold.
2. Trace the keyboard path through the interface and record unreachable controls, wrong order, hidden focus and traps.
3. Check labels, alt text, link text, headings and landmarks, naming the element each finding applies to.
4. Read the markup as a screen reader would and note state changes, errors or updates that go unannounced.
5. Rank findings by severity with criterion number, evidence and a concrete fix, and list what could not be verified.

What you get

A findings table sorted by severity with columns for criterion, element, evidence and fix, then a short list of unverified areas and a summary of pass or fail per area.

What it watches out for

• Claiming a pass on screen reader behaviour from markup alone, when real announcements depend on browser and reader combinations.
• Counting only missing alt attributes and skipping poor alt text, which technically passes while still failing users.
• Suggesting ARIA roles where native elements would do, which adds failure modes instead of removing them.

How to install

Claude.ai and the Claude desktop app

1. Download the skill .zip.
2. Open Settings, then Capabilities, and find Skills.
3. Choose Upload skill and select the .zip.
4. Ask Claude for help with the task. It loads the skill when your request matches.

Claude Code

1. Download the skill .zip.
2. Unzip it into ~/.claude/skills/ (or .claude/skills/ inside a project).
3. Start a new session. Claude Code loads the skill when your request matches.

Codex

1. Download the skill .zip.
2. Unzip it into ~/.agents/skills/ (or .agents/skills/ inside a project).
3. Codex picks it up on its own. Type $ and the skill name to use it, or just ask for the task.

Cursor

1. Download the Cursor rule (.mdc).
2. Save it in .cursor/rules/ inside your project.
3. Cursor's agent applies the rule when your request matches its description.

AGENTS.md (Codex, Cursor, and other coding agents)

1. Copy the AGENTS.md section.
2. Paste it into AGENTS.md at the root of your repository, creating the file if needed.
3. Coding agents that read AGENTS.md follow it when your request fits.