home / Design / Wcag Audit Patterns Skill by @sickn33

Wcag Audit Patterns Skill by @sickn33

FREE

github stars★ 48,690updatedOct 2026repo@sickn33

activity (commits, last 6 months)

6mo ago0

this month2

$git clone https://github.com/sickn33/agentic-awesome-skills

The skill is the skills/wcag-audit-patterns folder inside that repository. Copy it into the folder your agent loads skills from; check your agent's documentation for where that is.

about Wcag Audit Patterns Skill by @sickn33

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

our take

A guide to auditing web content against WCAG 2.2 with actionable remediation strategies. It states when to use it and includes a safety section.

when to use it

You need an accessibility audit of a page or flow
You want fixes proposed for each issue found
You are preparing for an accessibility review

before you install

Automated audits miss issues that need manual testing with assistive technology
Conformance claims need real testing, not just an agent's report

what's inside

The original SKILL.md is organised into these sections:

Use this skill when
Do not use this skill when
Instructions
Safety
Resources
Limitations

source and license

Written and maintained by @sickn33. It is published under the MIT license, which allows reuse with attribution. SkillDirectory does not claim authorship: this page adds our own review and links back to the original, and the skill's text belongs to its author.

View the full SKILL.md on GitHub ↗

Read the opening of the original SKILL.md

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

Excerpt only, quoted from the author's repository. Open the repository for the complete file.

↓ download .zip