accessibility-audit

Audit web pages for WCAG 2.1/2.2 compliance and report issues.

2|Updated May 15, 2026
One-click install
npx skills add https://github.com/bdbch/ai-dotfiles --skill accessibility-audit-bdbch
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: accessibility-audit
Source: https://github.com/bdbch/ai-dotfiles/tree/main/skills/accessibility-audit
Command: npx skills add https://github.com/bdbch/ai-dotfiles --skill accessibility-audit-bdbch

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill unit provides a structured method to conduct thorough WCAG 2.1/2.2 accessibility audits of web pages or components, ensuring compliance with accessibility standards.

Core Features & Use Cases

  • Accessibility Audit: Offers a step-by-step process to evaluate web accessibility, covering keyboard navigation, screen reader output, color contrast, ARIA usage, and semantic HTML.
  • Customizable Audit Dimensions: Includes checks for Perceptibility, Operability, Understandability, and Robustness, aligning with WCAG principles.
  • Output Reporting: Generates a summary report with findings, compliance status, and actionable recommendations.

Quick Start

Run the accessibility-audit skill with the URL of the webpage you want to audit.

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 accessibility audit for a web page?

To conduct a WCAG 2.2 accessibility audit, evaluate keyboard navigation, screen reader output, color contrast, ARIA usage, and semantic HTML. The audit assesses Perceptibility, Operability, Understandability, and Robustness to generate a detailed compliance report with actionable recommendations.

What does a WCAG compliance check cover for keyboard navigation and screen readers?

A WCAG compliance check evaluates keyboard navigation by testing focus management and operability. It also analyzes screen reader output, ARIA implementation, and semantic HTML structure to ensure web content is accessible and robust for assistive technologies.

Can I audit color contrast and ARIA usage on any web page URL?

Yes, you can audit color contrast and ARIA usage by providing a web page URL. The audit evaluates these dimensions alongside semantic HTML and keyboard navigation to produce a detailed report on WCAG 2.1/2.2 compliance issues and recommendations.

What's the best way to report WCAG 2.1 compliance issues?

The best way to report WCAG 2.1 compliance issues is to generate a structured summary detailing specific findings across keyboard, screen reader, color contrast, and ARIA dimensions. This report includes the current compliance status and actionable recommendations for remediation.

Does a web accessibility audit check semantic HTML and ARIA together?

Yes, a web accessibility audit checks semantic HTML and ARIA together. It evaluates how ARIA attributes complement semantic HTML structure to ensure proper screen reader output, verifying both Operability and Robustness principles for WCAG 2.1/2.2 compliance.