wcag-audit-patterns

Combine automated and manual checks to audit WCAG 2.2 accessibility.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires axe, lighthouse, pa11y, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill streamlines the process of auditing web content for WCAG 2.2 compliance, providing a framework for automated checks, manual evidence collection, and prioritized remediation.

Core Features & Use Cases

  • Audit Scope Definition: Establish the scope, including URLs, components, and WCAG level.
  • Automated Checks: Run automated checks using tools like axe, Lighthouse, or pa11y.
  • Manual Checks: Perform comprehensive manual checks for keyboard access, focus order, names/roles/values, and content structure.
  • Evidence Collection: Collect and document findings with severity and remediation details.
  • Remediation Planning: Prioritize and plan remediation efforts.
  • Use Case: If you have a website or application that needs to meet WCAG 2.2 standards, this Skill can help you systematically audit and address accessibility issues.

Quick Start

Use the wcag-audit-patterns skill to audit the website 'www.example.com' and generate an accessibility report.

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 structured WCAG 2.2 audit for web content?

A WCAG 2.2 audit combines automated checks using tools like axe, Lighthouse, or pa11y with manual checks for keyboard access, focus order, names/roles/values, and content structure to collect evidence and prioritize remediation.

Do I need automated tools and manual checks for WCAG compliance?

Yes, WCAG compliance requires both. Automated tools like axe, Lighthouse, and pa11y catch common issues, while manual checks are essential for verifying keyboard access, focus order, names/roles/values, and content structure.

Can I use axe, Lighthouse, or pa11y to check web accessibility?

Yes, you can use axe, Lighthouse, or pa11y to run automated accessibility checks on websites and web applications to identify initial WCAG 2.2 compliance violations before performing manual evidence collection.

What is the best way to plan remediation for web accessibility issues?

The best way to plan remediation is to collect documented findings with severity levels during the audit, then prioritize the accessibility issues based on their severity to systematically address WCAG 2.2 compliance gaps.

How do I define the audit scope for WCAG 2.2 compliance?

You define the WCAG 2.2 audit scope by specifying the target URLs, web components, and the desired WCAG compliance level to systematically evaluate websites and web applications.