wcag

Audit and remediate digital content against WCAG 2.0, 2.1, and 2.2 success criteria.

869|179|Updated Mar 16, 2026
One-click install
npx skills add https://github.com/Sushegaad/Claude-Skills-Governance-Risk-and-Compliance --skill wcag
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wcag
Source: https://github.com/Sushegaad/Claude-Skills-Governance-Risk-and-Compliance/tree/main/plugins/wcag/skills/wcag
Command: npx skills add https://github.com/Sushegaad/Claude-Skills-Governance-Risk-and-Compliance --skill wcag

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Teams building websites and digital products struggle to interpret WCAG success criteria, run accessibility audits, and map conformance levels to legal requirements like EN 301 549, the EAA, ADA, and Section 508.

Core Features & Use Cases

  • Criterion-by-criterion guidance: Explains every WCAG 2.0/2.1/2.2 success criterion with level, common failures, and fixes across the four POUR principles.
  • Accessibility audits and gap assessments: Produces structured audit tables, conformance reviews, and remediation priorities citing specific SC numbers.
  • Legal mapping and statements: Maps WCAG criteria to global accessibility laws and drafts accessibility statements with conformance claims and known issues.
  • Use Case: A developer asks why a modal fails keyboard accessibility; the skill identifies SC 2.1.2 No Keyboard Trap, explains the failure, and provides corrected focus-management code.

Quick Start

Ask the assistant to audit your page's HTML against WCAG 2.1 Level AA and list each failing success criterion with remediation steps.

Frequently Asked Questions about wcag

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

FAQPage Schema
How do I audit a website for WCAG 2.1 AA conformance?

Combine automated scans (axe-core, Lighthouse, WAVE) with manual testing: keyboard-only navigation, screen reader passes with NVDA or VoiceOver, contrast checks, and 320px reflow testing. Automated tools catch roughly 30-40% of issues, so manual review is essential.

What is the difference between WCAG 2.1 and WCAG 2.2?

WCAG 2.2 adds nine success criteria including Focus Not Obscured, Dragging Movements, Target Size, Consistent Help, Redundant Entry, and Accessible Authentication, and removes SC 4.1.1 Parsing. It is fully backwards-compatible, so 2.2 AA conformance implies 2.1 AA.

Which WCAG level do accessibility laws require?

Level AA is the universal legal benchmark. EN 301 549 and the European Accessibility Act reference WCAG 2.1 AA, Section 508 requires WCAG 2.0 AA, and ADA Title III case law increasingly applies WCAG 2.1 AA.

What contrast ratio does WCAG require for text?

SC 1.4.3 requires 4.5:1 for normal text and 3:1 for large text (18pt regular or 14pt bold and above). UI components and informational graphics need 3:1 under SC 1.4.11, and AAA raises normal text to 7:1.

Why do automated accessibility tools miss most WCAG issues?

Tools like axe-core detect only about 30-40% of failures because many criteria need human judgment, such as alt text quality, focus order logic, and error message clarity. Manual keyboard, screen reader, and zoom testing covers the remainder.