Claude Cursor Skill

wcag-audit-patterns

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.

LLM Mart · 0 points · 19 views 0 listing impressions 0 install-command copies
Download wshobson-agents-plugins_accessibility-compliance_skills_wcag-audit-patterns-554237f.zip · 5 KB

Install

skills CLI npx skills add https://github.com/wshobson/agents/tree/main/plugins/accessibility-compliance/skills/wcag-audit-patterns
Claude Code claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install wshobson-agents@llmmart
Git git clone https://github.com/wshobson/agents.git

The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole wshobson/agents collection as a plugin from our marketplace. Git is the plain clone.

Skill manifest

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

Level Description Required For
A Minimum accessibility Legal baseline
AA Standard conformance Most regulations
AAA Enhanced accessibility Specialized 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
Files (agents)
  • references
    • details.md 9.7 KB
      Loading…
  • SKILL.md 2.5 KB
    ---
    name: wcag-audit-patterns
    description: 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.
    ---
    
    # 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
    
    | Level   | Description            | Required For      |
    | ------- | ---------------------- | ----------------- |
    | **A**   | Minimum accessibility  | Legal baseline    |
    | **AA**  | Standard conformance   | Most regulations  |
    | **AAA** | Enhanced accessibility | Specialized 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
    

Comments (0)

Sign in to join the conversation.

No comments yet.

Reviews (0)

No reviews yet.