a11y-audit
Audit a UI or design against WCAG 2.2 AA/AAA and ARIA patterns, returning criterion-referenced findings with severity and specific fixes. Use when the user wants an accessibility check, contrast verification, keyboard/screen-reader review, or wants to confirm a component meets POUR.
How do I install this agent skill?
npx skills add https://github.com/plugin87/ux-ui-agent-skills --skill a11y-auditIs this agent skill safe to install?
- Gen Agent Trust Hubwarn
The skill performs accessibility audits but contains instructions to access a 'tokens' directory outside its folder, which is a potential indicator of credential harvesting. It also executes external scripts and downloads code via npx.
- Socketpass
No alerts
- Snykpass
Risk: LOW · No issues
What does this agent skill do?
Skill: Accessibility Audit
Requirements
This skill needs the full UX/UI Agent Skills kit: the gates, the references and
the design-system library. Install it with npx ux-ui-agent-skills@3.1.1 init
or as the Claude Code plugin. npx skills@1.7.6 add copies the skill folder and
nothing else. Installed that way, this skill runs in guidance-only mode: no gate
runs, so it gives no verdict.
Step 0: is the kit here? Check once:
ls ${CLAUDE_SKILL_DIR}/../../../tokens >/dev/null 2>&1 && echo KIT_OK || echo KIT_MISSINGOnKIT_MISSING, open your reply with: "Guidance-only mode: the UX/UI Agent Skills kit is not installed here, so no gate ran and nothing below is measured." Then work from this file and general practice, under three rules. Do not guess or cite the contents of a kit file you could not open. State no measured number (no contrast ratio, no N/N, no "passes WCAG"): write "not verified" where one would go. End with a lineSkipped (kit not installed):that names every gate script this file tells you to run, then the install command above.
Evaluate against WCAG 2.2 and the project's ARIA patterns.
Steps
- Read
${CLAUDE_SKILL_DIR}/../../../accessibility/wcag-checklist.md(POUR-organized, P0/P1/P2) and${CLAUDE_SKILL_DIR}/../../../accessibility/aria-patterns.md. - Check the mandatory P0 set per component: keyboard navigable, focus visible (≥3:1), screen-reader name/role/state, contrast (4.5:1 text / 3:1 UI), target size ≥24×24, no color-only signaling.
- Verify WCAG 2.2 additions: Focus Not Obscured (2.4.11), Target Size (2.5.8), Accessible Authentication (3.3.8).
- Contrast: measure, don't eyeball. For rendered HTML, RUN the real-render gates and report their actual output (CLAUDE.md → Verification Protocol):
node ${CLAUDE_SKILL_DIR}/../../../scripts/gate.mjs measure_render.mjs <file> [--dark](every text element) ANDnode ${CLAUDE_SKILL_DIR}/../../../scripts/gate.mjs verify_states.mjs <file> [--dark](every interactive element in default/hover/focus; catches hover-state failures). For loose color pairs,python3 ${CLAUDE_SKILL_DIR}/../../../scripts/contrast.py "<fg>" "<bg>". Never state a ratio you did not measure. - Check reduced-motion handling (
${CLAUDE_SKILL_DIR}/../../../taste/motion-choreography.md).
Output
A findings table: WCAG criterion (e.g. 1.4.3) · severity (P0/P1/P2) · what fails · specific fix. Confirm passes explicitly. Accessibility may never be traded for aesthetics.
How can the creator link this skill?
Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.
<a href="https://skillzs.dev/skills/plugin87/ux-ui-agent-skills/a11y-audit">View a11y-audit on skillZs</a>