wcag-audit-patterns

Audit web interfaces for WCAG 2.2 accessibility violations.

Updated Apr 5, 2026
One-click install
npx skills add https://github.com/Jhabbig/Habbig --skill wcag-audit-patterns-jhabbig
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wcag-audit-patterns
Source: https://github.com/Jhabbig/Habbig/tree/main/.claude/plugins/wshobson/accessibility-compliance/skills/wcag-audit-patterns
Command: npx skills add https://github.com/Jhabbig/Habbig --skill wcag-audit-patterns-jhabbig

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams identify, verify, and fix accessibility barriers in web experiences before they become compliance, usability, or legal risks. It turns WCAG 2.2 requirements into a practical audit workflow that combines automated checks with manual inspection and remediation guidance.

Core Features & Use Cases

  • Automated accessibility testing: Check pages and components for common WCAG failures such as missing labels, contrast problems, keyboard traps, and poor focus behavior.
  • Manual audit guidance: Review structure, reading order, headings, landmarks, dialogs, status messages, and other patterns that require human validation.
  • Remediation support: Translate findings into concrete fixes for semantic HTML, ARIA usage, forms, navigation, media, and responsive behavior.
  • Use case: A product team preparing for an accessibility review can use this Skill to assess a release candidate, prioritize violations by severity, and document fixes for engineering and compliance stakeholders.

Quick Start

Use the wcag-audit-patterns skill to audit the provided website or component and return prioritized WCAG 2.2 findings with clear remediation steps.

Frequently Asked Questions about wcag-audit-patterns

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit a web interface for WCAG 2.2 accessibility violations?

To audit a web interface for WCAG 2.2 violations, combine automated checks for common failures like missing labels with manual inspection of structure and ARIA patterns, then document prioritized remediation steps.

What is the best way to check my website for keyboard navigation and focus management issues?

The best way to check for keyboard navigation and focus issues is an accessibility audit that tests for keyboard traps and verifies focus behavior across interactive components and dialogs.

Can I use an accessibility audit to find ARIA and contrast problems for Section 508 compliance?

Yes, an accessibility audit verifies ARIA patterns and color contrast to satisfy Section 508 requirements, translating findings into concrete fixes for semantic HTML and visual compliance.

How do I plan remediation for WCAG failures found in a web app release candidate?

Plan remediation for WCAG failures by prioritizing identified violations by severity and generating concrete fixes for forms, navigation, media, and responsive behavior for engineering stakeholders.

Does a standard WCAG audit cover manual verification of headings and status messages?

Yes, a comprehensive WCAG audit includes manual verification of reading order, headings, landmarks, and status messages because these structural patterns require human validation to ensure accessibility.

Why do automated accessibility tests miss structural and ARIA pattern violations?

Automated tests miss structural and ARIA pattern violations because elements like reading order, dialog behavior, and status messaging require manual human inspection to validate proper accessibility integration.