---
name: accessibility-auditor
description: Audit websites for accessibility issues and WCAG compliance. Use when checking accessibility, fixing a11y issues, or ensuring WCAG compliance.
---

# Accessibility Auditor

Audit a website for accessibility defects and bring it to WCAG 2.1 AA compliance.

## Contents

- `references/automated-testing.md` - CLI commands, jest-axe, Playwright, and tooling
- `references/wcag-checklist.md` - WCAG Level A/AA criteria and keyboard testing checklist
- `references/common-fixes.md` - Fix patterns for the 7 most common defects plus the sr-only class
- `references/aria-patterns.md` - ARIA markup for tabs, accordion, menu, alert, progress

## Workflow

1. Run automated checks. Execute the CLI scans and add jest-axe or Playwright assertions per `references/automated-testing.md`.
2. Test the keyboard. Tab through the page and verify order, activation, escape, focus visibility, and absence of traps using the checklist in `references/wcag-checklist.md`.
3. Test with a screen reader. Walk the page with NVDA or VoiceOver and confirm names, roles, and announced state.
4. Check WCAG criteria. Audit each Level A and AA criterion in `references/wcag-checklist.md`.
5. Apply fixes. Resolve each finding with the patterns in `references/common-fixes.md` and `references/aria-patterns.md`, then re-run step 1 to confirm zero violations.

---

## Agent contract

_Added by Tacit's Skill Builder so agents use this skill predictably. Everything above this section is the
author's original, unchanged. This section restates what the skill already implies; verify it before relying on it._

**Before you start, ask for** (in one message; state assumptions if the user wants you to proceed):
- The URL or code to audit (local or staging preferred)
- The target standard (WCAG 2.1 AA by default) and any legal requirement driving it
- Whether to only report or also fix

**Output format:**

```
ACCESSIBILITY AUDIT: <site>
Summary: issues by severity (critical / serious / moderate / minor)
Per issue: WCAG criterion, where (page, element), who it affects, fix (code)
Automated vs manual checks performed
What still needs testing with real assistive-technology users
```

**When to stop and hand off to a human:**
- Automated checks can't certify compliance: say a manual audit with assistive-technology users is still needed
- A legal accessibility claim or complaint is involved: involve counsel and a certified auditor

_Original: [Accessibility Auditor](https://github.com/OneWave-AI/claude-skills/blob/main/accessibility-auditor/SKILL.md) by OneWave AI, licensed MIT. Changes: added this "Agent contract" section._


---

<!-- Original licence -->

MIT License

Copyright (c) 2025 OneWave AI

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.