Wcag Audit Patterns

by wshobson46891e7e60daNo licenseListed Oct 8, 2026Updated Oct 8, 2026

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.

Instructions onlySecurity
AI-generated overview

Guides WCAG 2.2 accessibility audits with automated testing, manual verification, and remediation advice.

What it does
This skill provides guidance for auditing web content against WCAG 2.2, covering conformance levels, the POUR principles, and common violations grouped by impact. It outlines best practices for accessible design and remediation, and points to a reference file for detailed patterns and worked examples. It produces audit guidance and remediation recommendations rather than running tests itself.
When to use it
Use it when auditing websites or components for accessibility, fixing WCAG violations, or implementing accessible design patterns. It also fits preparation for accessibility lawsuits and ADA, Section 508, or VPAT compliance work.
Requirements
No scripts or tools are required; it is instructions only. It references a bundled reference file for detailed patterns.

WCAG Audit Patterns

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

When to Use This Skill

  • Conducting accessibility audits
  • Fixing WCAG violations
  • Implementing accessible components
  • Preparing for accessibility lawsuits
  • Meeting ADA/Section 508 requirements
  • Achieving VPAT compliance

Core Concepts

1. WCAG Conformance Levels

LevelDescriptionRequired For
AMinimum accessibilityLegal baseline
AAStandard conformanceMost regulations
AAAEnhanced accessibilitySpecialized needs

2. POUR Principles

Perceivable:  Can users perceive the content?Operable:     Can users operate the interface?Understandable: Can users understand the content?Robust:       Does it work with assistive tech?

3. Common Violations by Impact

Critical (Blockers):├── Missing alt text for functional images├── No keyboard access to interactive elements├── Missing form labels└── Auto-playing media without controls
Serious:├── Insufficient color contrast├── Missing skip links├── Inaccessible custom widgets└── Missing page titles
Moderate:├── Missing language attribute├── Unclear link text├── Missing landmarks└── Improper heading hierarchy

Detailed patterns and worked examples

Detailed pattern documentation lives in references/details.md. Read that file when the navigation tier above is insufficient.

Best Practices

Do's

  • Start early - Accessibility from design phase
  • Test with real users - Disabled users provide best feedback
  • Automate what you can - 30-50% issues detectable
  • Use semantic HTML - Reduces ARIA needs
  • Document patterns - Build accessible component library

Don'ts

  • Don't rely only on automated testing - Manual testing required
  • Don't use ARIA as first solution - Native HTML first
  • Don't hide focus outlines - Keyboard users need them
  • Don't disable zoom - Users need to resize
  • Don't use color alone - Multiple indicators needed

Source and attribution

Source:wshobson/agentsinplugins/accessibility-compliance/skills/wcag-audit-patternsat commit46891e7

License: No license

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal