0179-wcag-audit-patterns

Audit web pages against WCAG 2.2 with automated checks and manual verification.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/MrJmpl3/codex_____data_____configuration --skill 0179-wcag-audit-patterns
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: 0179-wcag-audit-patterns
Source: https://github.com/MrJmpl3/codex_____data_____configuration/tree/main/skills/0179-wcag-audit-patterns
Command: npx skills add https://github.com/MrJmpl3/codex_____data_____configuration --skill 0179-wcag-audit-patterns

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you identify and fix website accessibility problems against WCAG 2.2 so users with disabilities can navigate content reliably and your organization can reduce compliance risk.

Core Features & Use Cases

  • WCAG 2.2 audit checklist by POUR and success criteria: Covers Perceivable, Operable, Understandable, and Robust with practical checks (e.g., text alternatives, keyboard access, focus visibility, language attributes, status messages).
  • Actionable remediation patterns: Provides before/after examples for common failures such as missing form labels, insufficient contrast, and keyboard-inaccessible custom widgets.
  • Automated testing workflows and tool guidance: Includes axe-core integration and example CLI approaches (axe, pa11y, Lighthouse) to find issues at scale while still requiring manual verification.
  • Use case fit: Ideal when auditing websites, preparing VPAT-like documentation, fixing known WCAG violations, and standardizing accessible design patterns across a component library.

Quick Start

Use the 0179-wcag-audit-patterns checklist to run an accessibility audit on your site, then apply the included remediation patterns to each violation you find.

Frequently Asked Questions about 0179-wcag-audit-patterns

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

FAQPage Schema
How do I run a WCAG 2.2 accessibility audit on my web pages?▼

To run a WCAG 2.2 accessibility audit, use a structured checklist based on POUR principles alongside automated tools like axe-core or pa11y to identify violations, followed by manual verification of flagged issues.

What are the best remediation patterns for fixing keyboard accessibility and contrast violations?▼

Effective remediation patterns for keyboard accessibility and contrast violations include applying before-and-after code examples to add missing form labels, ensure focus visibility, and adjust colors to meet WCAG 2.2 contrast success criteria.

Can I use axe-core and pa11y for automated accessibility regression testing?▼

Yes, you can use axe-core and pa11y for automated accessibility regression testing by integrating these CLI tools into your workflow to find WCAG 2.2 issues at scale, though manual verification remains required for complete coverage.

Does this WCAG audit approach support standardizing accessibility across a component library?▼

Yes, this WCAG audit approach supports component-library standardization by providing actionable design patterns and remediation examples that ensure custom widgets meet keyboard access and POUR compliance requirements consistently.

What is included in a WCAG 2.2 POUR audit checklist?▼

A WCAG 2.2 POUR audit checklist includes practical checks for Perceivable, Operable, Understandable, and Robust principles, covering text alternatives, keyboard access, focus visibility, language attributes, and status messages.