Skip to main content
AI/MLsickn33

wcag-audit-patterns

Comprehensive guide to auditing web content against WCAG 2.2 guidelines with actionable remediation strategies.

Stars
39,227
Source
sickn33/antigravity-awesome-skills
Updated
2026-05-30
Slug
sickn33--antigravity-awesome-skills--wcag-audit-patterns
View on GitHubRaw SKILL.md

// install — copy + paste into any project

mkdir -p .claude/skills && curl -fsSL https://raw.githubusercontent.com/sickn33/antigravity-awesome-skills/HEAD/plugins/antigravity-awesome-skills-claude/skills/wcag-audit-patterns/SKILL.md -o .claude/skills/wcag-audit-patterns.md

Drops the SKILL.md into .claude/skills/wcag-audit-patterns.md. Works with Claude Code, Cursor, and any agent that loads SKILL.md files from .claude/skills/.

WCAG Audit Patterns

Comprehensive guide to auditing web content against WCAG 2.2 guidelines with actionable remediation strategies.

Use this skill when

  • Conducting accessibility audits
  • Fixing WCAG violations
  • Implementing accessible components
  • Preparing for accessibility lawsuits
  • Meeting ADA/Section 508 requirements
  • Achieving VPAT compliance

Do not use this skill when

  • You need legal advice or formal certification
  • You only want a quick automated scan without manual verification
  • You cannot access the UI or source for remediation work

Instructions

  1. Run automated scans (axe, Lighthouse, WAVE) to collect initial findings.
  2. Perform manual checks (keyboard navigation, focus order, screen reader flows).
  3. Map each issue to a WCAG criterion, severity, and remediation guidance.
  4. Re-test after fixes and document residual risk and compliance status.

Refer to resources/implementation-playbook.md for detailed patterns, checklists, and templates.

Safety

  • Avoid claiming legal compliance without expert review.
  • Keep evidence of test steps and results for audit trails.

Resources

  • resources/implementation-playbook.md for detailed patterns, checklists, and templates.

Limitations

  • Use this skill only when the task clearly matches the scope described above.
  • Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
  • Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.