skills.rest
FR-LYO-CYS-AURA
FR-LYO-CYS-AURAOFFICIAL
Explore all skills by this author →
GitHub

wcag

Advise on WCAG 2.0, 2.1, and 2.2 success criteria, audits, and legal conformance mapping.

Updated Jul 29, 2026
Search Tags:#accessibility#a11y#audit#wcag#aria#conformance#section 508
One-click install
npx skills add https://github.com/FR-LYO-CYS-AURA/GRC-Consultant --skill wcag-fr-lyo-cys-aura
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: wcag
Source: https://github.com/FR-LYO-CYS-AURA/GRC-Consultant/tree/main/extracted-skills/wcag
Command: npx skills add https://github.com/FR-LYO-CYS-AURA/GRC-Consultant --skill wcag-fr-lyo-cys-aura

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 understand which conformance level (A/AA/AAA) their jurisdiction legally requires. This Skill turns WCAG 2.0, 2.1, and 2.2 into actionable guidance with criterion-level fixes, testing workflows, and legal mappings. ## Core Features & Use Cases - Criterion Explanations & Fixes: Every Level A and AA success criterion explained with common failures, sufficient techniques, and remediation steps, always cited by number (e.g., SC 1.4.3 Contrast Minimum). - Accessibility Audits & Gap Assessments: Structured audit tables mapping criteria to issues, severity, and remediation, plus a full manual testing workflow covering keyboard, screen reader, contrast, and reflow testing. - Legal Conformance Mapping: Side-by-side mapping of WCAG versions to EN 301 549, the European Accessibility Act, Section 508, ADA Title III, AODA, and other global regulations. - Use Case: A developer asks why their modal fails accessibility review. The Skill identifies SC 2.1.2 No Keyboard Trap and SC 4.1.2 Name, Role, Value violations, then provides the corrected ARIA dialog pattern with focus management. ## Quick Start Ask the assistant to audit your page against WCAG 2.1 Level AA and list each failing success criterion with its fix.

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 scanning with axe-core, Lighthouse, or WAVE, then manually test keyboard navigation, screen readers (NVDA, JAWS, VoiceOver), colour contrast, and 320px reflow. Automated tools catch roughly 30-40% of issues, so manual testing is essential.

What is the difference between WCAG 2.1 and WCAG 2.2?▼

WCAG 2.2 adds nine new success criteria including Focus Not Obscured, Dragging Movements, Target Size Minimum, and Accessible Authentication, and removes SC 4.1.1 Parsing. It is fully backwards-compatible, so conforming to 2.2 AA also satisfies 2.1 AA.

What contrast ratio does WCAG require for text?▼

WCAG 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, while AAA raises normal text to 7:1.

Which WCAG level is legally required for accessibility compliance?▼

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.

Why do automated accessibility tools miss most WCAG issues?▼

Automated tools only detect programmatically verifiable failures, roughly 30-40% of all issues. Criteria like meaningful alt text quality, logical focus order, and error message clarity require human judgment and manual testing with keyboards and screen readers.

When should I use ARIA instead of native HTML?▼

Use native HTML elements first; the first rule of ARIA is that no ARIA is better than bad ARIA. Add ARIA roles and attributes only when HTML cannot express the semantics, and follow the ARIA Authoring Practices Guide keyboard patterns for custom widgets.

Related Skills

Explore More Legal & Compliance Skills→
Community-AccessCommunity-Access
387

web-scanning

Crawl websites and generate page inventories for accessibility audits.

Official
Intermediate
MinBZKMinBZK
2

a11y-review

Automate WCAG 2.1 AA accessibility reviews for web templates, CSS, and HTML.

Official
Basic
gonzoblascogonzoblasco
1

wcag-audit-patterns

Audit web content against WCAG 2.2 criteria and map violations to code remediation.

Community
Intermediate
alexchloualexchlou
2

skill-manager

Uninstall or disable third-party community skills in legal AI systems.

Community
Basic