wcag-audit-patterns

Audit websites against WCAG 2.2 with automated testing and remediation guidance.

4|Updated Jan 10, 2026
One-click install
npx skills add https://github.com/EngineerWithAI/engineerwith-agents --skill wcag-audit-patterns-engineerwithai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wcag-audit-patterns
Source: https://github.com/EngineerWithAI/engineerwith-agents/tree/main/plugins/accessibility-compliance/skills/wcag-audit-patterns
Command: npx skills add https://github.com/EngineerWithAI/engineerwith-agents --skill wcag-audit-patterns-engineerwithai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires axe-core, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill addresses the critical need for web accessibility by providing a comprehensive framework for auditing websites against WCAG 2.2 guidelines, identifying violations, and offering actionable remediation strategies.

Core Features & Use Cases

  • WCAG 2.2 Auditing: Detailed checklists covering Perceivable, Operable, Understandable, and Robust principles.
  • Automated Testing Guidance: Includes examples for integrating tools like axe-core and CLI utilities.
  • Remediation Patterns: Provides concrete code examples for fixing common accessibility issues (e.g., missing labels, color contrast).
  • Use Case: A web developer needs to ensure a new feature meets accessibility standards before launch. They use this Skill to systematically check against WCAG 2.2, identify contrast issues, and implement keyboard navigation fixes.

Quick Start

Use the wcag-audit-patterns skill to audit the provided website URL for WCAG 2.2 compliance.

Frequently Asked Questions about wcag-audit-patterns

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

FAQPage Schema
How do I conduct a WCAG 2.2 accessibility audit for a website?

To conduct a WCAG 2.2 accessibility audit, use automated testing tools like axe-core and manual verification checklists covering POUR principles to identify violations. This process systematically checks web content for compliance issues and provides actionable remediation guidance.

What are the common WCAG 2.2 violations and how do I fix them?

Common WCAG 2.2 violations include missing labels and insufficient color contrast. You fix these web accessibility issues by applying concrete remediation patterns, such as adding ARIA attributes and adjusting CSS contrast ratios to meet compliance standards.

Can I integrate axe-core into my web development workflow for compliance testing?

Yes, you can integrate axe-core into your web development workflow for compliance testing using CLI utilities. This automated testing guidance helps identify accessibility issues early, ensuring web content meets ADA and Section 508 standards before launch.

Does web accessibility auditing require manual verification or is automated testing enough?

Web accessibility auditing requires both automated testing and manual verification. While tools like axe-core catch common violations, manual checklists are essential to fully evaluate Perceivable, Operable, Understandable, and Robust principles for complete WCAG 2.2 compliance.

What is the best way to ensure my new web feature meets ADA and Section 508 accessibility standards?

The best way to ensure ADA and Section 508 accessibility compliance is running a systematic WCAG 2.2 audit. This involves checking your web feature against established guidelines using automated tools and manual checklists to identify and fix violations.

Why does automated accessibility testing miss certain WCAG compliance issues?

Automated accessibility testing misses WCAG compliance issues because tools like axe-core cannot evaluate subjective POUR principles contextually. Manual verification checklists are required to assess keyboard navigation flows and content understandability for full compliance.