Zero-setup WCAG audits for AI agents.

Drop-in accessibility audit for AI coding agents. Template-aware scanning, actionable remediation hints, zero-config dependency resolution.

Most accessibility tools require manual setup, produce raw violation dumps, and leave you to figure out what to fix first. skill-a11y-audit discovers your site structure automatically, groups violations by shared template, and tells you exactly what to fix and where — in one command.

a11y-audit: Accessibility audit skill for Claude Code and Codex. Powered by axe-core, WCAG 2.1 AA, and Lighthouse.

Why skill-a11y-audit?

Most accessibility tools scan one page at a time, return raw rule IDs, and require manual setup in every project they touch. That model doesn’t scale to real sites or AI agents. skill-a11y-audit is built around three different assumptions.

Template-aware sampling

Large sites have hundreds of pages but only a handful of distinct templates. The skill identifies your templates, scans representatives from each group, and maps every violation to the template it affects. Fix one component; resolve issues across hundreds of pages.

Tells you what to fix

Every violation includes a one-liner remediation hint — not just the rule ID. Findings are ranked by severity and grouped by template so you know which fix has the highest impact before you open a single file.

Zero configuration

Drop the a11y-audit/ folder into .claude/skills/. axe-core and Puppeteer resolve automatically from skill-local deps, project node_modules, global install, or auto-install. No prior setup required.

Install

Copy or symlink the skill folder into any project’s .claude/skills/ directory. Then ask your AI agent to run an audit.

Copy (one-time snapshot)

cp -r ~/Git/skill-a11y-audit/a11y-audit/ \
  /path/to/project/.claude/skills/a11y-audit/

Stable snapshot of the skill at install time.

Symlink (always latest)

ln -s ~/Git/skill-a11y-audit/a11y-audit \
  /path/to/project/.claude/skills/a11y-audit

Always uses the latest version of the skill.

Invoke via Claude Code

Run an accessibility audit on this project.

The skill runs discover → scan → report automatically.

Run the scripts directly

node a11y-audit/scripts/discover.js \
  --url http://localhost:3000 \
  --output /tmp/discover.json

node a11y-audit/scripts/scan.js \
  --root . --summary \
  --output /tmp/scan.json

node a11y-audit/scripts/report.js \
  --input /tmp/scan.json \
  --output-dir ./audits

Each script writes a JSON file the next step reads.

Sample output

A structured markdown report. Pass --output-mode markdown+json for machine-readable data, or markdown+issues to generate GitHub, Linear, or Jira tickets.

## Executive Summary
Pages scanned: 22 of 746  ·  Template groups: 16
Violations: 3  ·  Severity: 1 critical, 1 serious, 1 moderate

## Findings by Rule

Rule                  Impact    Instances  Affects
color-contrast        critical  6          regulation/*, requires/*
aria-required-attr    serious   2          nav, footer
landmark-one-main     moderate  1          homepage

## Shared Template Patterns
Shared issues on regulation/*, requires/*, authority/*: dlitem
→ Fix the shared build template once → resolves across 144 pages.