audit-accessibility

Audit designs and builds against WCAG 2.2 AA with severity-rated findings and a launch gate verdict.

1|Updated Jul 13, 2026
One-click install
npx skills add https://github.com/dineshrevunuru/SuperSkills --skill audit-accessibility-dineshrevunuru
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: audit-accessibility
Source: https://github.com/dineshrevunuru/SuperSkills/tree/main/audit-accessibility
Command: npx skills add https://github.com/dineshrevunuru/SuperSkills --skill audit-accessibility-dineshrevunuru

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Accessibility issues slip into shipped products because automated scans catch only about 30% of problems and teams lack a structured manual audit method. This Skill provides a five-pass WCAG 2.2 AA audit workflow that severity-rates every finding and issues a hard PASS / PASS WITH NOTES / BLOCKED launch verdict. ## Core Features & Use Cases - Five-pass manual audit: Covers static/visual checks, keyboard-only navigation, screen reader behavior, zoom and reflow, and motion/time/forms — the 70% of issues automated tools miss. - Severity rating and hard gate: Maps findings to Blocker/Serious/Minor using Nielsen's frequency × impact × persistence method, then issues a non-waivable launch verdict. - Residual-risk reporting: Every report states that a WCAG pass is not proof of real assistive-technology usability and recommends AT-user testing when stakes are high. - Use Case: Before launching a booking flow, run the audit on the staging build, get a findings table with WCAG criteria and severities, and receive a BLOCKED verdict with the shortest path to unblock. ## Quick Start Audit this booking flow prototype for WCAG 2.2 AA accessibility and give me a severity-rated findings report with a launch verdict.

Frequently Asked Questions about audit-accessibility

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

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

Start with an automated scan like axe DevTools or Lighthouse, which catches roughly 30% of issues, then run five manual passes: static/visual checks, keyboard-only navigation, screen reader testing, zoom and reflow, and motion/time/forms. Rate each finding by severity and issue a launch verdict.

What WCAG contrast ratio is required for text?

WCAG 2.2 AA requires at least 4.5:1 for normal text and 3:1 for large text (24px or larger, or 18.5px bold). UI components and meaningful graphics need 3:1 against adjacent colors. Measure with a contrast tool rather than eyeballing.

Can I audit accessibility on a static Figma design?

Yes, but only the static/visual pass applies. You can check contrast, labels, alt text specifications, and reading order, but keyboard, screen reader, and reflow criteria require working code. Untested criteria must be logged as unverified, never marked as passed.

Does passing WCAG mean a site is fully accessible?

No. NN/g research found the web roughly three times harder to use for screen-reader users even on nominally compliant sites. A WCAG pass should be reported with a residual-risk line, and high-stakes products should add usability testing with real assistive-technology users.

When should accessibility findings block a product launch?

Any Blocker finding — where a user group cannot complete a core task at all, such as a keyboard trap or unlabeled required field — blocks launch with no exceptions. Serious findings allow PASS WITH NOTES only if each has a named owner and date.