a11y-audit

Audits codebases against WCAG 2.2 AA/AAA criteria across ten accessibility dimensions with fix generation.

6|Updated Mar 27, 2026
One-click install
npx skills add https://github.com/greglas75/zuvo --skill a11y-audit-greglas75
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: a11y-audit
Source: https://github.com/greglas75/zuvo/tree/main/skills/a11y-audit
Command: npx skills add https://github.com/greglas75/zuvo --skill a11y-audit-greglas75

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Web projects often ship with accessibility violations that block keyboard and screen reader users and create legal exposure under ADA Title II, EAA, and Section 508. This Skill performs a deep, criterion-mapped WCAG 2.2 audit of your codebase and produces scored findings with concrete fixes. ## Core Features & Use Cases - Ten-dimension audit (A1-A10): Covers semantic HTML, keyboard navigation, ARIA patterns, color contrast, forms, images/media, responsive/zoom, motion, reading/content, and legal compliance, with critical gates on keyboard (A2) and contrast (A4). - WCAG criterion mapping and legal risk assessment: Every finding maps to a specific WCAG 2.2 success criterion and severity, with a compliance summary for ADA Title II, EAA, and Section 508. - Fix generation and backlog persistence: The --fix flag generates before/after code fixes for CRITICAL and HIGH findings, and --persist-backlog records them for tracking. - Use Case: Before a public launch, run a full audit with --standard AA --legal ada to get a scored report, identify keyboard traps and contrast failures, and auto-generate fixes for the critical findings. ## Quick Start Ask the AI to run a WCAG 2.2 AA accessibility audit on your project with the a11y-audit skill, for example: audit the src/components directory and generate fixes for critical findings.

Frequently Asked Questions about a11y-audit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run a WCAG 2.2 accessibility audit on my codebase?

Invoke the a11y-audit skill with a path, the full flag, or --live-url for browser testing. It scans templates, JSX/TSX, and CSS across ten dimensions and outputs a scored report with WCAG criterion-mapped findings.

What accessibility issues can automated WCAG audits detect?

Automated checks catch roughly 30-57% of WCAG issues, including missing alt text, contrast failures, missing labels, and ARIA misuse. Alt text quality, keyboard traps in complex widgets, and logical reading order still require manual verification.

Does this audit support ADA Title II and EAA compliance checks?

Yes. The --legal flag accepts ada, eaa, or 508 and maps A1-A9 findings to the selected legal standard. The report includes a compliance summary showing COMPLIANT, AT RISK, or NON-COMPLIANT status per standard.

Can the audit automatically fix accessibility violations?

Yes. The --fix flag generates before/after code fixes and auto-applies CRITICAL and HIGH fixes after creating a git rollback tag. Fixes only touch accessibility attributes, ARIA properties, semantic elements, and CSS focus or contrast styles.

What causes an accessibility audit to fail regardless of overall score?

Two critical gates force a FAIL verdict: keyboard navigation (A2) scoring below 6 of 12, or color contrast (A4) scoring below 5 of 10. An overall score below 70% also fails regardless of gate status.