AI Agent Hub
Back to skills
🔒

WCAG 2.2 Audit and Repair Guide

IT Ops & Security Updated 2026.08.30

Paste the following prompt into your AI chat to install this skill:

Please install @org-02qudk26/wcag-audit-patterns into the current AI assistant by following https://skillhub.cn/install/skillhub.md.

About this skill

Problem

Web accessibility audits often stop at automated reports: axe, Lighthouse, or WAVE can flag some issues, but keyboard navigation, focus order, and screen-reader flows still require manual verification. When a team must fix WCAG violations, build accessible components, or prepare for ADA / Section 508 and VPAT readiness, what is missing is a structured process that maps findings to standards, severity, and remediation actions.

How It Works

The skill provides audit and remediation patterns for WCAG 2.2. Its core workflow includes:
- running automated scans to collect initial findings
- performing manual checks for keyboard operation, focus order, and screen-reader paths
- mapping each issue to a WCAG criterion, severity level, and fix guidance
- retesting after fixes and recording residual risk and compliance status

resources/implementation-playbook.md adds checklists, templates, and implementation patterns, which helps turn audit results into actionable tickets and acceptance materials.

Boundaries

The skill does not replace legal advice or formal certification. If the UI or source code is unavailable, remediation decisions are limited. Keep testing steps, evidence, and review records, and avoid claiming legal compliance without expert review.

Use Cases

  • When a page cannot receive keyboard focus before launch, locate the WCAG 2.2 issue and define a fix
  • After axe and Lighthouse scans, map violations to WCAG criteria and prioritize remediation
  • Preparing Section 508 evidence by documenting keyboard navigation and screen-reader test results
  • Retesting focus order after form controls are fixed and recording residual risk and compliance status

Best For

  • Frontend engineers: verify keyboard navigation, focus order, and screen-reader behavior after component changes
  • QA engineers: turn automated scan findings into repeatable accessibility acceptance checks
  • Product owners: confirm key flows meet WCAG 2.2 and ADA / Section 508 readiness before release
  • Compliance or operations staff: organize accessibility test records, residual-risk notes, and acceptance materials