Skills · Design & UI

Wcag Audit Patterns

Unverified30/40

Conduct WCAG 2.2 accessibility audits with automated testing, manual verification, and remediation guidance. Use when auditing websites for accessibility, fixing WCAG violations, or implementing accessible design patterns.

Originally by wshobson · MIT

Claude CodePartialHas SKILL.md but declares no allowed-tools — Claude Code will ask for permission each time
CursorPartialPlain prose you can paste in — but no Cursor rules file
CodexPartialPlain prose you can paste in — but no AGENTS.md
Gemini CLIPartialPlain prose you can paste in
CopilotPartialPlain prose you can paste in — but no Copilot instructions file
npx agentalley add wcag-audit-patterns

This command does not work yet — the CLI is still being built. Until then, use Raw in the reader below to take the file.

Who is stuck, and on what

Conduct WCAG 2.2 accessibility audits with automated testing, manual verification, and remediation guidance. Use when auditing websites for accessibility, fixing WCAG violations, or implementing accessible design patterns.

The whole source

No sign-in, no blur, nothing truncated
wcag-audit-patterns/SKILL.md81 lines2.5 KBRawView on GitHub
Frontmatter — 2 properties
namewcag-audit-patterns
descriptionConduct WCAG 2.2 accessibility audits with automated testing, manual verification, and remediation guidance. Use when auditing websites for accessibility, fixing WCAG violations, or implementing accessible design patterns.
1---
2name: wcag-audit-patterns
3description: Conduct WCAG 2.2 accessibility audits with automated testing, manual verification, and remediation guidance. Use when auditing websites for accessibility, fixing WCAG violations, or implementing accessible design patterns.
4---A5No allowed-tools declared — no way to tell what this skill may touch
5 
6# WCAG Audit Patterns
7 
8Comprehensive guide to auditing web content against WCAG 2.2 guidelines with actionable remediation strategies.
9 
10## When to Use This Skill
11 
12- Conducting accessibility audits
13- Fixing WCAG violations
14- Implementing accessible components
15- Preparing for accessibility lawsuits
16- Meeting ADA/Section 508 requirements
17- Achieving VPAT compliance
18 
19## Core Concepts
20 
21### 1. WCAG Conformance Levels
22 
23| Level | Description | Required For |
24| ------- | ---------------------- | ----------------- |
25| **A** | Minimum accessibility | Legal baseline |
26| **AA** | Standard conformance | Most regulations |
27| **AAA** | Enhanced accessibility | Specialized needs |
28 
29### 2. POUR Principles
30 
31```
32Perceivable: Can users perceive the content?
33Operable: Can users operate the interface?
34Understandable: Can users understand the content?
35Robust: Does it work with assistive tech?
36```
37 
38### 3. Common Violations by Impact
39 
40```
41Critical (Blockers):
42├── Missing alt text for functional images
43├── No keyboard access to interactive elements
44├── Missing form labels
45└── Auto-playing media without controls
46 
47Serious:
48├── Insufficient color contrast
49├── Missing skip links
50├── Inaccessible custom widgets
51└── Missing page titles
52 
53Moderate:
54├── Missing language attribute
55├── Unclear link text
56├── Missing landmarks
57└── Improper heading hierarchy
58```
59 
60## Detailed patterns and worked examples
61 
62Detailed pattern documentation lives in `references/details.md`. Read that file when the navigation tier above is insufficient.
63 
64## Best Practices
65 
66### Do's
67 
68- **Start early** - Accessibility from design phase
69- **Test with real users** - Disabled users provide best feedback
70- **Automate what you can** - 30-50% issues detectable
71- **Use semantic HTML** - Reduces ARIA needs
72- **Document patterns** - Build accessible component library
73 
74### Don'ts
75 
76- **Don't rely only on automated testing** - Manual testing required
77- **Don't use ARIA as first solution** - Native HTML first
78- **Don't hide focus outlines** - Keyboard users need them
79- **Don't disable zoom** - Users need to resize
80- **Don't use color alone** - Multiple indicators needed
81 

Reviews

Installed this one?Write the first review and take the Trailblazer badge.

Reviews only open after a real install, so this is empty — and we leave it empty rather than invent one.

Alternatives

Also in Design & UI