wcag-accessibility-audit

Audits websites and apps against WCAG 2.1/2.2 success criteria across four POUR principles.

1|1|Updated Jul 6, 2026
One-click install
npx skills add https://github.com/gabesan21/project-of-projects --skill wcag-accessibility-audit-gabesan21
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: wcag-accessibility-audit
Source: https://github.com/gabesan21/project-of-projects/tree/main/.agents/skills/wcag-accessibility-audit
Command: npx skills add https://github.com/gabesan21/project-of-projects --skill wcag-accessibility-audit-gabesan21

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams shipping websites and apps often lack a structured way to find accessibility barriers, risking legal non-compliance (ADA, Section 508, EAA) and excluding users with disabilities. This Skill provides a complete WCAG 2.1/2.2 audit methodology with prioritized, actionable findings. ## Core Features & Use Cases - Systematic WCAG Evaluation: Covers all four POUR principles (Perceivable, Operable, Understandable, Robust) with critical success criteria for Levels A and AA, including the nine new WCAG 2.2 criteria. - Combined Testing Procedure: Guides automated scans (axe DevTools, WAVE, Lighthouse) plus manual keyboard, screen reader, zoom, form, semantic HTML, and ARIA testing. - Prioritized Remediation Report: Produces a structured report with severity ratings, code-level fix recommendations, effort estimates, and a phased remediation plan. - Use Case: Before launching a web app, run this audit on key pages to identify critical blockers like missing alt text, low contrast, and keyboard traps, then hand the prioritized fix list to your dev team. ## Quick Start Audit my website at the provided URL for WCAG 2.2 Level AA conformance and generate a prioritized remediation report.

Frequently Asked Questions about wcag-accessibility-audit

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

FAQPage Schema
How do I audit a website for WCAG 2.2 compliance?▼

Run automated tools like axe DevTools, WAVE, and Lighthouse to catch obvious violations, then manually test keyboard navigation, screen reader output, color contrast, and form labels. Document failures by success criterion and prioritize Level A and AA issues in a remediation plan.

What is the difference between WCAG Level A, AA, and AAA?▼

Level A covers minimum essential accessibility features, Level AA addresses major barriers and is the target for most organizations and legal requirements, and Level AAA provides enhanced accessibility that is not always achievable for all content.

Can automated tools detect all WCAG accessibility issues?▼

No, automated tools like axe and WAVE catch only about 30-40% of accessibility issues. Manual testing with keyboards, screen readers like NVDA or VoiceOver, and zoom checks is essential for a comprehensive evaluation.

What are the new success criteria in WCAG 2.2?▼

WCAG 2.2 added nine criteria including Focus Not Obscured, Dragging Movements, Target Size (24x24 CSS pixels minimum), Consistent Help, Redundant Entry, and Accessible Authentication. These address focus visibility, pointer alternatives, and cognitive accessibility.

Does WCAG Level AA conformance guarantee legal compliance?▼

Level AA is the common target for laws like ADA, Section 508, and EAA, but legal obligations vary by jurisdiction. An audit provides guidance, not a legal assessment; consult accessibility lawyers for compliance verification.