mcpField
W
wcag-audit-patterns

wcag-audit-patterns

github.com/sickn33Testing & quality48.8k228 installsUpdated today
Repository

About wcag-audit-patterns

wcag-audit-patterns is a skill for teams auditing and remediating web accessibility against WCAG 2.2. It combines automated scans with manual checks and criterion-based findings, while emphasizing retesting and evidence rather than legal certification.

Key features

  1. 01Automated scan and manual-check guidance
  2. 02WCAG criterion and severity mapping
  3. 03Remediation guidance for findings
  4. 04Retesting and audit-trail documentation
  5. 05Implementation patterns and checklists

Use cases

  1. 01Auditing a website for accessibility issues
  2. 02Planning fixes for WCAG violations
  3. 03Checking keyboard and screen-reader flows
  4. 04Documenting test results and residual risks

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/sickn33/agentic-awesome-skills --skill wcag-audit-patterns

After installing, type/wcag-audit-patternsin Claude Code to confirm it loaded.

Bundled filesresources/implementation-playbook.md

Details

From the project README

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.

Comments

Markdown supported