wcag-audit-patterns

Name: wcag-audit-patterns
Author: wshobson

9.6kinstalls4.1kforks

How to install wcag-audit-patterns?

wshobson/agents/wcag-audit-patterns

$npx -y skills add wshobson/agents --skill wcag-audit-patterns

Installs into the current project.

Summary

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.

Files · 1

View on GitHub

SKILL.md

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

People who liked this also viewed

6 picks

Type

wcag-audit-patterns

9.6kinstalls4.1kforks

View on GitHub

How to install wcag-audit-patterns?

wshobson/agents/wcag-audit-patterns

$npx -y skills add wshobson/agents --skill wcag-audit-patterns

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

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

People who liked this also viewed

6 picks

Type