ux-accessibility-audit

Audit designs and code against WCAG 2.1 AA criteria with severity-rated findings.

12|2|Updated Jun 22, 2026
One-click install
npx skills add https://github.com/Uxcel-Lab/product-skills --skill ux-accessibility-audit-uxcel-lab
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ux-accessibility-audit
Source: https://github.com/Uxcel-Lab/product-skills/tree/main/ux/audits/accessibility
Command: npx skills add https://github.com/Uxcel-Lab/product-skills --skill ux-accessibility-audit-uxcel-lab

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Accessibility reviews are often partial and vague, catching only obvious issues like missing alt text while skipping focus order, heading hierarchy, and table semantics. This Skill runs a systematic six-category WCAG 2.1 AA audit where every finding cites the violated criterion, carries a severity rating, and includes a concrete fix. ## Core Features & Use Cases - Systematic six-category sweep: Covers color and contrast, typography, forms, links and navigation, images and multimedia, and tables and lists so non-obvious issues are not missed. - Severity-rated findings: Classifies each issue as Critical, Major, or Minor based on how completely it blocks access, producing a prioritized fix list. - Criterion-cited fixes: Every finding references the specific WCAG criterion and gives the exact markup, attribute, ratio, or design change needed. - Use Case: After generating a signup form UI, run this audit as a validation step to catch placeholder-only labels, missing focus indicators, and contrast failures before shipping. ## Quick Start Ask the assistant to run an accessibility audit on your login screen against WCAG 2.1 AA and return a prioritized issue list with fixes.

Frequently Asked Questions about ux-accessibility-audit

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

FAQPage Schema
How do I run a WCAG accessibility audit on a design?▼

Work through six categories systematically: color and contrast, typography, forms, links and navigation, images and multimedia, and tables and lists. Flag each violation with its WCAG criterion, a severity rating, and a concrete fix rather than giving vague suggestions.

What contrast ratio does WCAG AA require for text?▼

WCAG 2.1 AA requires at least 4.5:1 contrast for normal text and 3:1 for large text (18pt or 14pt bold and above). Informational icons and input borders also need 3:1 against their surrounding background.

What tools check website accessibility automatically?▼

WAVE, axe DevTools, and Google Lighthouse scan pages and reference violated WCAG criteria. Automated scanners catch only about 30-40% of issues, so manual review of focus order, alt-text quality, and reading order is still required.

Can automated tools catch all accessibility issues?▼

No. Automated scanners catch roughly 30-40% of issues, mostly contrast and missing attributes. Keyboard traps, focus order, alt-text quality, and heading hierarchy require manual testing with tools like VoiceOver or NVDA.

How should accessibility issues be prioritized for fixing?▼

Rate by how completely the issue blocks access, not by fix effort. Critical issues block access entirely (Level A failures like no keyboard access), Major issues cause significant friction (AA failures like low contrast), and Minor issues are best-practice improvements.