accessibility-audit

Identify WCAG 2.2 AA compliance gaps through automated and manual audits.

2|1|Updated Apr 13, 2026
One-click install
npx skills add https://github.com/dreamingechoes/dx-toolkit --skill accessibility-audit-dreamingechoes
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: accessibility-audit
Source: https://github.com/dreamingechoes/dx-toolkit/tree/main/templates/skills/accessibility-audit
Command: npx skills add https://github.com/dreamingechoes/dx-toolkit --skill accessibility-audit-dreamingechoes

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

WCAG 2.2 AA compliance auditing is often manual, time-consuming, and error-prone; this guide provides a repeatable, comprehensive procedure that blends automated scans, manual testing, and remediation guidance to surface and fix accessibility issues.

Core Features & Use Cases

  • Consolidated methodology for automated scanning, keyboard and screen reader testing, and remediation planning.
  • Use cases include full-page audits, component-level reviews, design-system validation, and regulatory remediation projects.
  • Documentation-ready outputs that feed into audits, reports, and remediation roadmaps.

Quick Start

Run a full WCAG 2.2 AA audit on your web pages using automated scanners and guided manual checks.

Frequently Asked Questions about accessibility-audit

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

FAQPage Schema
How do I conduct a WCAG 2.2 AA audit for a web interface?

A WCAG 2.2 AA audit combines automated scans with guided manual testing. This workflow identifies compliance gaps across full pages or components and outputs documentation-ready reports for remediation planning.

What is the best way to identify WCAG 2.2 compliance gaps in a design system?

To identify WCAG 2.2 compliance gaps in a design system, apply a combined automated and manual audit workflow. This process surfaces accessibility issues early and provides repeatable, auditable results for validation.

Can I use manual testing alone for a full-page accessibility audit?

Manual testing alone is not recommended for a full-page accessibility audit. A repeatable procedure blending automated scans, keyboard and screen reader testing, and manual checks is required to surface issues accurately.

How do I create a remediation roadmap after finding accessibility issues?

To create a remediation roadmap after finding accessibility issues, use the reporting formats and remediation guidance generated by the audit workflow. These outputs deliver structured steps to fix identified compliance gaps.

When do I need a component-level accessibility review instead of a full-page audit?

A component-level accessibility review is needed when validating specific design system elements rather than an entire interface. This targeted approach surfaces localized WCAG 2.2 AA issues before full integration.

Does this accessibility audit workflow require any specific testing tools?

The accessibility audit workflow prescribes tooling recommendations for automated scanning and manual testing. It provides a comprehensive procedure without relying on external dependencies to deliver auditable results.