wcag-audit-patterns · git:20261111.00f9c40 · 2026-11-11 · sha256 f920ffe7cb344481

wcag-audit-patterns git:20261111.00f9c40A

Immutable. This exact content never changes and is served at /api/v1/blob/f920ffe7cb344481.

No tool to install first
claude plugin marketplace add https://markdownregistry.com/mp/a/art_sp53g6htodw7at5u/f920ffe7cb344481896df425ee8cc1c661f6e59a370e6011d960ecd48e0dcec3.json

Then /plugin install wcag-audit-patterns@markdownregistry-sp53g6htodw7at5u in Claude Code. It installs this exact version, the one graded A here, pinned to the commit it was graded at, and leaves it there.

---
name: wcag-audit-patterns
description: Comprehensive guide to auditing web content against WCAG 2.2 guidelines with actionable remediation strategies.
metadata:
  aas-risk: safe
  aas-source: community
  aas-date-added: '2026-02-27'
---

# 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.