wcag-audit-patterns

wshobson/agents · updated Apr 8, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills add https://github.com/wshobson/agents --skill wcag-audit-patterns
0 commentsdiscussion
summary

Automated WCAG 2.2 auditing with violation detection, remediation patterns, and compliance guidance.

  • Covers all four WCAG principles (Perceivable, Operable, Understandable, Robust) with detailed checklists for Levels A, AA, and AAA conformance
  • Includes code examples for common violations: missing alt text, insufficient contrast, keyboard traps, form labels, and focus management
  • Provides automated testing patterns using axe-core, Playwright, and CLI tools alongside manual verification
skill.md

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

Audit Checklist

Perceivable (Principle 1)

## 1.1 Text Alternatives

### 1.1.1 Non-text Content (Level A)

- [ ] All images have alt text
- [ ] Decorative images have alt=""
- [ ] Complex images have long descriptions
- [ ] Icons with meaning have accessible names
- [ ] CAPTCHAs have alternatives

Check:

```html
<!-- Good -->
<img src="chart.png" alt="Sales increased 25% from Q1 to Q2" />
<img src="decorative-line.png" alt="" />

<!-- Bad -->
<img src="chart.png" />
<img src="decorative-line.png" alt="decorative line" />
```

1.2 Time-based Media

1.2.1 Audio-only and Video-only (Level A)

  • Audio has text transcript
  • Video has audio description or transcript

1.2.2 Captions (Level A)

  • All video has synchronized captions
  • Captions are accurate and complete
  • Speaker identification included

1.2.3 Audio Description (Level A)

  • Video has audio description for visual content

1.3 Adaptable

1.3.1 Info and Relationships (Level A)

  • Headings use proper tags (h1-h6)
  • Lists use ul/ol/dl
  • Tables have headers
  • Form inputs have labels
  • ARIA landmarks present

Check:

<!-- Heading hierarchy -->
<h1>Page Title</h1>
<h2>Section</h2>
<h3>Subsection</h3>
<h2>Another Section</h2>

<!-- Table headers -->
<table>
  <thead>
    <tr>
      <th scope="col">Name</th>
      <th scope="col">Price</th>
    </tr>
  </thead>
</table>

1.3.2 Meaningful Sequence (Level A)

  • Reading order is logical
  • CSS positioning doesn't break order
  • Focus order matches visual order

1.3.3 Sensory Characteristics (Level A)

  • Instructions don't rely on shape/color alone
  • "Click the red button" → "Click Submit (red button)"

1.4 Distinguishable

1.4.1 Use of Color (Level A)

  • Color is not only means of conveying info
  • Links distinguishable without color
  • Error states not color-only

1.4.3 Contrast (Minimum) (Level AA)

  • Text: 4.5:1 contrast ratio
  • Large text (18pt+): 3:1 ratio
  • UI components: 3:1 ratio

Tools: WebAIM Contrast Checker, axe DevTools

1.4.4 Resize Text (Level AA)

  • Text resizes to 200% without loss
  • No horizontal scrolling at 320px
  • Content reflows properly

1.4.10 Reflow (Level AA)

  • Content reflows at 400% zoom
  • No two-dimensional scrolling
  • All content accessible at 320px width

1.4.11 Non-text Contrast (Level AA)

  • UI components have 3:1 contrast
  • Focus indicators visible
  • Graphical objects distinguishable

1.4.12 Text Spacing (Level AA)

  • No content loss with increased spacing
  • Line height 1.5x font size
  • Paragraph spacing 2x font size
  • Letter spacing 0.12x font size
  • Word spacing 0.16x font size

### Operable (Principle 2)

```markdown
## 2.1 Keyboard Accessible

### 2.1.1 Keyboard (Level A)
- [ ] All functionality keyboard accessible
- [ ] No keyboard traps
- [ ] Tab order is logical
- [ ] Custom widgets are keyboard operable

Check:
```javascript
// Custom button must be keyboard accessible
<div role="button" tabindex="0"
     onkeydown="if(event.key === 'Enter' || event.key === ' ') activate()">

2.1.2 No Keyboard Trap (Level A)

  • Focus can move away from all components
  • Modal dialogs trap focus correctly
  • Focus returns after modal closes

2.2 Enough Time

2.2.1 Timing Adjustable (Level A)

  • Session timeouts can be extended
  • User warned before timeout
  • Option to disable auto-refresh

2.2.2 Pause, Stop, Hide (Level A)

  • Moving content can be paused
  • Auto-updating content can be paused
  • Animations respect prefers-reduced-motion
@media (prefers-reduced-motion: reduce) {
  * {
    animation: none !important;
    transition: none !important;
  }
}

2.3 Seizures and Physical Reactions

2.3.1 Three Flashes (Level A)

  • No content flashes more than 3 times/second
  • Flashing area is small (<25% viewport)

2.4 Navigable

2.4.1 Bypass Blocks (Level A)

  • Skip to main content link present
  • Landmark regions defined
  • Proper heading structure
<a href="#main" class="skip-link">Skip to main content</a>
<main id="main">...</main>

2.4.2 Page Titled (Level A)

  • Unique, descriptive page titles
  • Title reflects page content

2.4.3 Focus Order (Level A)

  • Focus order matches visual order
  • tabindex used correctly

2.4.4 Link Purpose (In Context) (Level A)

  • Links make sense out of context
  • No "click here" or "read more" alone
<!-- Bad -->
<a href="report.pdf">Click here</a>

<!-- Good -->
<a href="report.pdf">Download Q4 Sales Report (PDF)</a>

2.4.6 Headings and Labels (Level AA)

  • Headings describe content
  • Labels describe purpose

2.4.7 Focus Visible (Level AA)

  • Focus indicator visible on all elements
  • Custom focus styles meet contrast
:focus {
  outline: 
how to use wcag-audit-patterns

How to use wcag-audit-patterns on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • Cursor installed and configured on your development machine
  • Node.js version 16.0+ with npm package manager (verify with node --version)
  • Active project directory or workspace where you want to add wcag-audit-patterns
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/wshobson/agents --skill wcag-audit-patterns

The skills CLI fetches wcag-audit-patterns from GitHub repository wshobson/agents and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/wcag-audit-patterns

Reload or restart Cursor to activate wcag-audit-patterns. Access the skill through slash commands (e.g., /wcag-audit-patterns) or your agent's skill management interface.

Security & Verification Notice

We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.

Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.

List & Monetize Your Skill

Submit your Claude Code skill and start earning

GET_STARTED →

Use Cases

User Story & Requirements Generation

Create detailed user stories, acceptance criteria, and feature specs

Example

Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios

Reduce spec writing time by 50%, ensure comprehensive coverage

Competitive Analysis

Research competitors, compare features, identify gaps

Example

Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities

Complete competitive research in 2 hours instead of 2 days

Roadmap Prioritization

Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs

Example

Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale

Make data-driven prioritization decisions faster

Stakeholder Communication

Draft PRDs, status updates, and stakeholder presentations

Example

Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement

Save 3-5 hours/week on communication overhead

Implementation Guide

Prerequisites

  • Claude Desktop or compatible AI client
  • Access to product documentation and roadmap tools (Jira, Notion, etc.)
  • Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
  • Stakeholder contact information and communication channels

Time Estimate

30-60 minutes to see productivity improvements

Installation Steps

  1. 1.Install product management skill
  2. 2.Start with user story generation for known feature
  3. 3.Progress to competitive analysis: research 2-3 competitors
  4. 4.Use for roadmap prioritization: apply RICE/ICE scoring
  5. 5.Draft stakeholder communications and refine based on feedback
  6. 6.Build template library for recurring PM tasks
  7. 7.Share effective prompts with product team

Common Pitfalls

  • Not validating competitive research—verify facts before sharing
  • Accepting user stories without involving engineering team
  • Over-relying on frameworks without qualitative judgment
  • Not customizing outputs to company culture and communication style
  • Skipping stakeholder validation of generated requirements

Best Practices

✓ Do

  • +Validate research and competitive analysis with real data
  • +Collaborate with engineering when generating technical requirements
  • +Customize frameworks and templates to your company context
  • +Use skill for first drafts, refine with stakeholder input
  • +Document successful prompt patterns for PM tasks
  • +Combine AI efficiency with human judgment and intuition

✗ Don't

  • Don't publish competitive analysis without fact-checking
  • Don't finalize user stories without engineering review
  • Don't make prioritization decisions solely on AI scoring
  • Don't skip customer validation of generated requirements
  • Don't ignore company-specific context and culture

💡 Pro Tips

  • Provide context: company goals, constraints, customer feedback
  • Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
  • Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
  • Use skill for 70% generation + 30% customization to company needs

When to Use This

✓ Use When

Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.

✗ Avoid When

Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.

Learning Path

  1. 1Basic: user stories, feature specs, status updates
  2. 2Intermediate: competitive analysis, prioritization frameworks, PRDs
  3. 3Advanced: product strategy, go-to-market planning, OKR setting
  4. 4Expert: product vision, market positioning, business model innovation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.544 reviews
  • Ava Mensah· Dec 24, 2024

    Solid pick for teams standardizing on skills: wcag-audit-patterns is focused, and the summary matches what you get after install.

  • Pratham Ware· Dec 20, 2024

    wcag-audit-patterns is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • Noor Chawla· Dec 12, 2024

    wcag-audit-patterns has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • Layla Bansal· Dec 4, 2024

    wcag-audit-patterns reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Ava Johnson· Nov 23, 2024

    wcag-audit-patterns has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • Sakshi Patil· Nov 11, 2024

    Keeps context tight: wcag-audit-patterns is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • William Singh· Nov 7, 2024

    We added wcag-audit-patterns from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Isabella Haddad· Nov 3, 2024

    wcag-audit-patterns reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Layla Ghosh· Oct 26, 2024

    Solid pick for teams standardizing on skills: wcag-audit-patterns is focused, and the summary matches what you get after install.

  • Noor Farah· Oct 22, 2024

    I recommend wcag-audit-patterns for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

showing 1-10 of 44

1 / 5