wcag-compliance_skill

Overview

This skill validates web applications against WCAG 2.1 Level AA (and AAA where requested) and provides actionable remediation guidance. It combines automated scanners, programmatic checks, and manual verification steps to produce prioritized fixes and compliance documentation. Use it to find, triage, and resolve accessibility issues before release.

How this skill works

The skill runs automated audits (axe, Lighthouse, WAVE, pa11y) and programmatic checks (contrast ratio calculations, ARIA/HTML validations). It augments tool output with manual test steps: keyboard navigation, screen reader checks, text-resize and media caption inspections. Results are grouped by WCAG principle and impact level, with code examples and recommended fixes.

When to use it

• During UI development to catch accessibility regressions early
• Before production deployment or public release
• When performing accessibility audits or remediation sprints
• To validate legal or procurement requirements (ADA, Section 508)
• When preparing accessibility documentation like VPATs or public statements

Best practices

• Start with semantic HTML and native controls before adding ARIA
• Run automated scans in CI and complement with periodic manual checks
• Prioritize Level A and AA issues; reserve AAA for enhancements
• Provide visible focus styles and ensure full keyboard operability
• Document known issues, workarounds, and remediation timelines (VPAT)
• Test with screen readers (NVDA, JAWS, VoiceOver) and real users

Example use cases

• Audit a form to ensure labels, error messaging, and focus order meet WCAG 2.1 AA
• Integrate axe or pa11y into CI to fail builds on new critical violations
• Run contrast checks across a design system and update tokens to meet 4.5:1
• Perform a remediation sprint: export violations, assign to engineers, verify fixes manually
• Produce an accessibility statement and VPAT after a final compliance pass