wcag-audit-patterns

Audit web content against WCAG 2.2 criteria with automated scans and manual verification checklists.

Updated Aug 10, 2026
One-click install
npx skills add https://github.com/Eng-suso/BK-GPT --skill wcag-audit-patterns-eng-suso
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: wcag-audit-patterns
Source: https://github.com/Eng-suso/BK-GPT/tree/main/.claude/skills/wcag-audit-patterns
Command: npx skills add https://github.com/Eng-suso/BK-GPT --skill wcag-audit-patterns-eng-suso

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Web accessibility violations are hard to detect systematically, and teams often miss WCAG 2.2 requirements that expose them to ADA, Section 508, and VPAT compliance risk. This Skill provides a structured audit workflow combining automated scanning with manual verification and concrete remediation patterns. ## Core Features & Use Cases - Structured WCAG 2.2 Audit Checklists: Criterion-by-criterion checklists organized by the POUR principles (Perceivable, Operable, Understandable, Robust) covering Levels A and AA. - Automated Testing Integration: Ready-to-use axe-core, Playwright, pa11y, and Lighthouse configurations for detecting violations programmatically. - Remediation Patterns: Copy-paste code fixes for common issues like missing form labels, insufficient color contrast, and keyboard navigation failures. - Use Case: Before launching a new product page, run the audit workflow to scan for violations, manually verify keyboard navigation and screen reader flows, then apply the provided HTML/CSS/ARIA fixes and re-test to document compliance status. ## Quick Start Audit this page for WCAG 2.2 Level AA compliance and list each violation with its criterion and a remediation fix.

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 website for WCAG 2.2 compliance?▼

Run automated scans with axe-core, Lighthouse, or WAVE to collect initial findings, then perform manual checks for keyboard navigation, focus order, and screen reader flows. Map each issue to a WCAG criterion with severity and remediation guidance, then re-test after fixes.

What tools detect WCAG accessibility violations automatically?▼

axe-core integrates with Playwright for programmatic testing, while CLI tools like @axe-core/cli, pa11y, and Lighthouse scan URLs directly. Automated tools detect roughly 30-50% of issues, so manual verification is still required.

How do I fix insufficient color contrast for WCAG AA?▼

Normal text requires a 4.5:1 contrast ratio, large text (18pt+) requires 3:1, and UI components require 3:1. Darken the foreground color or add a contrasting background, then verify with WebAIM Contrast Checker or axe DevTools.

Does automated accessibility testing replace manual testing?▼

No, automated testing only catches 30-50% of accessibility issues. Manual verification of keyboard traps, focus visibility, meaningful reading order, and screen reader behavior is required for a complete WCAG audit.

When should I not rely on this WCAG audit approach?▼

Do not use it when you need legal advice or formal certification, when you only want a quick automated scan without manual verification, or when you cannot access the UI or source code to perform remediation work.