SkillHub

Skills wshobson agents

wcag-audit-patterns

Use it when:
You're auditing a site for accessibility, fixing WCAG violations, or preparing for ADA, Section 508 or VPAT requirements.
It does:
Ranks common violations by impact, and its reference file gives a checklist of 38 Level A and AA criteria, grouped by principle, about a third of them with code examples.
Automates:
axe-core inside a Playwright test, plus axe, pa11y and Lighthouse from the command line; it says automation finds only 30–50% of issues.
Fixes:
Before-and-after code for missing form labels and insufficient color contrast, and a custom dropdown made keyboard-operable.

TL;DR

A reference for accessibility audits against WCAG 2.2, the Web Content Accessibility Guidelines. Conformance comes in three levels: A is the legal baseline, AA what most regulations require, AAA enhanced accessibility. Every criterion falls under four principles, known as POUR: perceivable, operable, understandable and robust. The SKILL.md sorts common violations by impact: critical ones block users (missing alt text, no keyboard access, unlabeled form fields, autoplaying media without controls), serious ones include low contrast and missing skip links, moderate ones a missing language attribute or a broken heading order. Its reference file is a checklist of 38 Level A and AA criteria from 1.1.1 to 4.1.3, including the WCAG 2.2 addition Focus Not Obscured and noting that 4.1.1 Parsing is obsolete, each with checkboxes and about a third with HTML, CSS or JavaScript examples. It then shows axe-core running in a Playwright test, CLI checks with axe, pa11y and Lighthouse, and fixes for three common violations. Because tools catch only part of the issues, it asks for manual testing and testing with disabled users, native HTML before ARIA, visible focus outlines, zoom left on and never color alone.

Summarizes the skill at 4bde316.

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

skills.sh pageSource on GitHubAll skills from wshobson/agents

Total Downloads
13,000 on skills.sh, Nov 9, 2026
Repo stars
42,334 wshobson/agents
First seen
Jan 20, 2026 on skills.sh
Weekly Downloads
210
-9% over the 8 weeks to Nov 9
Weekly values
Week toInstalls
Sep 21231
Sep 28263
Oct 5306
Oct 12250
Oct 19205
Oct 26236
Nov 2215
Nov 9210
Category
category:designcategory:debuggingcategory:software-engineering

Taste for interfaces that don't look generated: direction, motion and accessibility.

Find root causes, review code and test what you built.

Everything for building software: planning, coding, debugging, design, frameworks, cloud, agents and skills.
Type
type:guidelines

Knowledge and rules the agent applies while it works: best practices, design principles, API references.
Effect
effect:none

Adds no side effects of its own. It shapes how the agent thinks, writes or reviews. Guidelines and routers are always effect:none, even when the task they support edits code.
Needs
needs:none

Instructions only. Works in any agent that supports skills.
Publisher
by:community

Everyone else. Unverified vendor claims default to community.
Topics
accessibilitytesting

SKILL.md

From wshobson/agents at 4bde316. Checked daily, last changed Nov 6, 2026.

Frontmatter
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