wcag-audit-patterns

Audit web content against WCAG 2.2 guidelines with automated testing and remediation patterns.

Updated Apr 23, 2026
One-click install
npx skills add https://github.com/SanketAdlak/PDMProjectDesign --skill wcag-audit-patterns-sanketadlak
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wcag-audit-patterns
Source: https://github.com/SanketAdlak/PDMProjectDesign/tree/main/.agents/skills/wcag-audit-patterns
Command: npx skills add https://github.com/SanketAdlak/PDMProjectDesign --skill wcag-audit-patterns-sanketadlak

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires axe-core, pa11y, lighthouse, playwright.

What problem does it solve? Web accessibility violations expose organizations to legal risk under ADA and Section 508 while excluding users with disabilities, yet auditing against WCAG 2.2 success criteria is complex and error-prone without a structured methodology. ## Core Features & Use Cases - Complete WCAG 2.2 Checklist: Covers all four POUR principles (Perceivable, Operable, Understandable, Robust) with Level A and AA success criteria organized as actionable checklists. - Automated Testing Integration: Provides axe-core, Playwright, pa11y, and Lighthouse configurations to detect violations programmatically in CI pipelines. - Remediation Patterns: Supplies before-and-after code fixes for common violations like missing form labels, insufficient color contrast, and keyboard-inaccessible widgets. - Use Case: When preparing a VPAT compliance report, run the axe-core audit script against your pages, then apply the remediation patterns to fix flagged contrast and labeling issues before manual verification. ## Quick Start Audit my website's homepage for WCAG 2.2 Level AA violations and suggest fixes for any issues found.

Frequently Asked Questions about wcag-audit-patterns

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

FAQPage Schema
How do I run an automated WCAG accessibility audit on my website?

Run axe-core via CLI with npx @axe-core/cli, use pa11y, or run Lighthouse with the accessibility category flag. For programmatic testing, inject axe-core into a Playwright page and evaluate results filtered by wcag2a, wcag2aa, and wcag22aa tags.

What is the difference between WCAG Level A, AA, and AAA conformance?

Level A is the minimum accessibility baseline required legally, Level AA is the standard conformance target for most regulations like ADA and Section 508, and Level AAA provides enhanced accessibility for specialized needs and is rarely required in full.

How do I fix insufficient color contrast violations?

Adjust text colors to meet a 4.5:1 contrast ratio for normal text and 3:1 for large text (18pt+) or UI components. Verify ratios with tools like WebAIM Contrast Checker or axe DevTools before shipping changes.

Can automated tools detect all WCAG violations?

No, automated tools like axe-core detect roughly 30-50% of accessibility issues. Manual testing is required for keyboard navigation flows, meaningful alt text quality, focus order logic, and screen reader compatibility.

How do I make a custom dropdown keyboard accessible?

Add tabindex="0", appropriate ARIA roles like combobox, and keydown handlers for Enter, Space, Escape, and arrow keys. Native HTML elements are preferred over ARIA-based custom widgets whenever possible.