98.8K+Download
Skip to the usage guide
wcag-audit-patternsby Seth Hobson

WCAG Audit Patterns Skill.

A Claude Code and Codex skill for design review: wCAG 2.2 audits with automated tests, manual checks, and remediation guidance.

  • Design Review & Accessibility
  • Review report
Download OpenDesignView usage guide
wshobson/agents · plugins/accessibility-compliance/skills/wcag-audit-patterns/SKILL.mdSKILL.md
--- 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. --- ## When to Use This Skill ## Core Concepts ## Detailed patterns and worked examples ## Best Practices
Front matter and section headings read from the upstream file on 2026-09-14 · 2,439 characters in full

01 What it does

What the wcag-audit-patterns Skill Does in Claude Code and Codex

Summary, workflow and outputs, all read from the skill's SKILL.md.

From the SKILL.mdRead 2026-09-14 · not a recorded run

In the Skill's Own Terms

This skill conducts WCAG 2.2 accessibility audits combining automated testing, manual verification, and remediation guidance. It categorizes violations by impact (Critical/Blockers, Serious, Moderate), covers three conformance levels (A for legal baseline, AA for most regulations, AAA for specialized needs), and applies POUR principles (Perceivable, Operable, Understandable, Robust).

The skill addresses common violations including missing alt text, keyboard access issues, insufficient color contrast, and improper heading hierarchy. It emphasizes semantic HTML, real-user testing with disabled users, and building accessible component libraries while recognizing that only 30-50% of issues are detectable through automation.

What it produces

  • Actionable remediation strategies for identified violations
  • Accessible component library documentation
See the example prompt ↗

How It Works

  1. 01
    Categorize Violations by Impact

    Issues are classified as Critical (blockers like missing alt text and no keyboard access), Serious (insufficient contrast, missing skip links), or Moderate (missing language attribute, unclear link text).

  2. 02
    Apply POUR Principles

    Audit against four principles: Perceivable (can users perceive content), Operable (can users operate the interface), Understandable (can users understand content), and Robust (does it work with assistive tech).

  3. 03
    Combine Automated and Manual Testing

    Automated tools detect 30-50% of issues, but manual testing is required for comprehensive coverage.

  4. 04
    Reference Detailed Pattern Documentation

    When core concepts are insufficient, the skill directs to references/details.md for worked examples and in-depth pattern guidance.

02 Find your fit

When to Use the wcag-audit-patterns Skill

Use the wcag-audit-patterns skill in Claude Code or Codex when the job is design review of this kind. Fit and limits below are taken from the skill's own file.

Good Fit

  • Conducting accessibility audits of web content
  • Fixing WCAG violations in existing interfaces
  • Meeting ADA or Section 508 regulatory requirements
  • Preparing for accessibility lawsuits
  • Achieving VPAT compliance documentation

    03 Inside the skill

    Rules the wcag-audit-patterns Skill Gives Claude Code and Codex

    8 concrete instructions, defaults and limits the SKILL.md sets for the agent — the part of the file that changes the result.

    1. Start Accessibility in Design Phase

      Accessibility must be incorporated early in the design phase rather than added as a retrofit.

    2. Use Semantic HTML First

      Native HTML elements should be the default choice because they reduce the need for ARIA and provide better accessibility support.

    3. Never Rely on Automated Testing Alone

      Manual testing is required because automated tools can only detect 30-50% of accessibility issues.

    4. Native HTML Before ARIA

      ARIA should not be used as the first solution; prefer native HTML elements whenever possible.

    5. Preserve Focus Outlines

      Focus outlines must not be hidden because keyboard users depend on them for navigation.

    6. Never Disable Zoom

      Users must be able to resize content, so zoom functionality cannot be disabled.

    7. Multiple Indicators Beyond Color

      Color alone cannot be used to convey information; multiple indicators are required.

    8. Test with Disabled Users

      Real users with disabilities provide the best feedback and should be included in testing.

    04 Put it to work

    Install wcag-audit-patterns in Claude Code or Codex

    One npx skills add command, then a first task in your agent and a checklist for the result.

    Add wcag-audit-patterns to Claude Code, Codex or Your Agent

    Run in your project; the installer asks which agent to add it to.

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

    Generic skills CLI form for plugins/accessibility-compliance/skills/wcag-audit-patterns/SKILL.md; the repository may document its own path.

    Give the Skill a First Design Review Task

    Written in the skill's own terms; replace the bracketed parts with your material.

    Starter prompt
    Audit [website URL or component name] against WCAG 2.2 AA standards. Identify all Critical and Serious violations including missing alt text, keyboard access issues, and color contrast failures. For each violation, provide the specific WCAG success criterion, the impact on users with disabilities, and concrete remediation code. Prioritize issues that would block screen reader users.

    Source: written from the SKILL.md in the skill's own terms.

    Check the First Result

    What the SKILL.md itself says a correct result looks like:

    • Verify compatibility with assistive technology for robust implementation

    In OpenDesign import wcag-audit-patterns from its SKILL.md link: Plugins → Add → Skill → Import from link, then pick it in the top bar.

    Download OpenDesignRead the quickstart

    05 Open source, traceable

    Source, License and Verification

    Where this page's facts come from, and when they were last checked.

    Author
    Seth Hobson
    Repository
    github.com/wshobson/agents Branch main
    Skill file
    plugins/accessibility-compliance/skills/wcag-audit-patterns/SKILL.md Content checksum recorded at verification; commit 4236bb9
    License
    MIT From LICENSE.
    Repository stars
    39,635 GitHub snapshot taken 2026-09-14 for the whole wshobson/agents repository, which contains 18 skills in this catalog. Not a rating or usage count for wcag-audit-patterns.
    Verified by OpenDesign
    2026-09-14 Source file, path, license text and star count were checked. Not bundled in OpenDesign main (checked 2026-08-28); a live run has not been recorded on this page.

    Inside the SKILL.md

    1. When to Use This SkillLists six scenarios including audits, fixing violations, and meeting regulatory requirements
    2. Core ConceptsDefines three conformance levels, POUR principles, and common violations by impact
    3. WCAG Conformance LevelsLevel A is legal baseline, AA is standard for regulations, AAA for specialized needs
    4. POUR PrinciplesFour principles: Perceivable, Operable, Understandable, Robust with guiding questions
    5. Common Violations by ImpactCategorizes issues as Critical blockers, Serious, or Moderate with specific examples
    6. Detailed patterns and worked examplesPoints to references/details.md for in-depth pattern documentation
    7. Best PracticesLists five Do's and five Don'ts for accessible development
    The Skill's Own 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.”

    Front-matter description from SKILL.md. The full file is about 2,439 characters. Read the full file on GitHub.

    06 Before you install

    Questions About the wcag-audit-patterns Skill

    Answers come from the SKILL.md as read on 2026-09-14, not from a recorded run.

    What WCAG conformance level should I target?

    Level AA is the standard conformance level required by most regulations. Level A is the minimum legal baseline, while Level AAA is only necessary for specialized needs. Most ADA and Section 508 requirements are satisfied with AA conformance.

    WCAG Audit Patterns

    Run wcag-audit-patterns on a Real Design Review Task.

    Download OpenDesign, import wcag-audit-patterns from its SKILL.md link, paste the prompt above, and read the plan before the result.

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

    OpenDesign Desktop

    One design system. Every output unmistakably your brand

    Inside the full Vibe Design Workspace, use the same brand rules across websites, slide decks, interactive prototypes, dashboards, images, and HTML video. Connect Codex, Claude Code, Cursor, and other coding agents already on your computer, then create locally for free.

    • Web, slides, prototypes, dashboards, images, and video
    • 140+ design systems, plus the full template and skill library
    • Connect local Codex and 21+ coding agents · Free to use
    Download free

    Available for macOS and Windows