Agent skill · writing content · nickcrew
accessibility-audit
Fast, high-signal accessibility triage for pages, components, or PRs targeting WCAG 2.2 AA compliance.
Why this skill is useful
Provides specific WCAG 2.2 AA compliance checks and automated tool commands that the AI wouldn't reliably generate on its own.
What it needs
Requires axe-core, pa11y installed locally. About 2k tokens when loaded. Last updated 2026-06-29. 28 stars on the source repository.
What this skill does
Accessibility Audit Skill Fast, high-signal accessibility triage for pages, components, or PRs. This is a lightweight check, not a full compliance audit. When to Use This Skill Quick accessibility triage before releases Component-level a11y verification PR review for accessibility regressions Smoke checks for WCAG compliance Validating keyboard navigation on new features Quick Audit Checklist 1. Automated Snapshot (Recommended) Run one of these automated tools first: npx @axe-core/cli <url> - Quick axe-core scan npx pa11y <url> --standard WCAG2AA - Pa11y audit Lighthouse Accessibility score (Chrome DevTools > Lighthouse > Accessibility) 2. Keyboard Basics Check Expected ------- ---------- All interactive elements reachable via Tab Yes Focus indicator always visible Yes No keyboard traps Yes Logical tab order Yes Skip link works for long pages Yes 3. Semantics and Labels Check Expected ------- ---------- Single, descriptive H1 Yes Logical heading order (no large jumps) Yes Form inputs have visible labels or aria-label Yes Buttons and links have clear names Yes Images have meaningful alt text (or empty for decorative) Yes 4. Visual Contrast Element Minimum Ratio --------- --------------- Normal text 4.5:1 Large text (18pt+ or 14pt bold+) 3:1 UI components (inputs, buttons, focus rings) 3:1 5. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills nickcrew/accessibility-audit