agentleFS
Sign inStart free
OneWave-AIOneWave-AI/claude-skills/accessibility-auditor/SKILL.md

accessibility-auditor

Skill378 starsChanged 52 days agoMITView on GitHub

Audit websites for accessibility issues and WCAG compliance. Use when checking accessibility, fixing a11y issues, or ensuring WCAG compliance.

10 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

4 rules. 0 are common, 1 is distinctive, and 3 are very specific to this project.

  • 0

    Common

    Most of the 9 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Run automated checks. Execute the CLI scans and add jest-axe or Playwright assertions per references/automated-testing.md.

    line 19
  2. Very specific:

    Test the keyboard. Tab through the page and verify order, activation, escape, focus visibility, and absence of traps using the checklist in …

    line 20
  3. Distinctive:

    Test with a screen reader.

    line 21
  4. Very specific:

    Check WCAG criteria. Audit each Level A and AA criterion in references/wcag-checklist.md.

    line 22

“Common” is measured: kept by at least 6 in 10 of the 9 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 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.

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.

Check your setup, free