a11y-audit

Name: a11y-audit
Availability: InStock
Author: ReefBytes-Owner

Audits web content for WCAG 2.2 AA conformance and outputs an Accessibility Audit Report.

1|Updated Aug 16, 2025

Search Tags:#accessibility #a11y #frontend #audit #wcag #semantic-html #aria

Ready to run

npx skills add https://github.com/ReefBytes-Owner/Manifest --skill a11y-audit-reefbytes-owner

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: a11y-audit
Source: https://github.com/ReefBytes-Owner/Manifest/tree/main/configs/claude/skills/a11y-audit
Command: npx skills add https://github.com/ReefBytes-Owner/Manifest --skill a11y-audit-reefbytes-owner

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Focused accessibility audits detect WCAG 2.2 AA conformance issues across web content, helping teams improve usability for all users.

Core Features & Use Cases

Phase-based checks covering Perceivable, Operable, Understandable, and Robust categories, plus ARIA best practices guidance.
Automated discovery of issues like missing alt text, insufficient color contrast, improper focus management, and semantic HTML violations.
Output a structured Accessibility Audit Report with actionable fixes for developers, designers, and QA to remediate.

Quick Start

Run the audit on your project directory to generate a WCAG 2.2 AA report.

Frequently Asked Questions about a11y-audit

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

FAQPage Schema

How do I audit my web project for WCAG 2.2 AA conformance?▼

To audit for WCAG 2.2 AA conformance, provide a file or directory path to run automated phase-based checks covering Perceivable, Operable, Understandable, and Robust categories plus ARIA best practices, generating a structured report with actionable fixes.

Can I run accessibility audits on SPA frameworks and component libraries?▼

Yes, accessibility audits work with SPA frameworks and component libraries by validating ARIA attributes, focus management, and semantic HTML to ensure WCAG 2.2 AA compliance across dynamic web content.

What common WCAG 2.2 AA accessibility issues can automated auditing detect?▼

Automated WCAG 2.2 AA auditing detects missing alt text, insufficient color contrast, improper focus management, and semantic HTML violations, providing developers and QA with an actionable remediation report.

What's the best way to check ARIA attributes and semantic HTML for accessibility compliance?▼

The best way to check ARIA attributes and semantic HTML is running an automated phase-based audit that evaluates content against WCAG 2.2 AA criteria and ARIA best practices, outputting structured fixes for developers.

Do I need a specific file path to start an accessibility audit?▼

Yes, you need an input path pointing to a file or directory to start the accessibility audit, which then performs phase-based checks and outputs a structured Accessibility Audit Report with actionable fixes.

Why does my web content fail focus management and color contrast checks?▼

Web content fails focus management and color contrast checks when it does not meet WCAG 2.2 AA standards; an automated audit identifies these specific violations and outputs actionable fixes for developers and QA.