accessibility-auditor

Audit web applications for WCAG 2.1 Level AA accessibility compliance.

Updated Oct 27, 2025

Search Tags:#a11y #ARIA #WCAG #keyboard #screen-reader

Ready to run

npx skills add https://github.com/CrazyDubya/claude-skills --skill accessibility-auditor

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: accessibility-auditor
Source: https://github.com/CrazyDubya/claude-skills/tree/main/accessibility-auditor
Command: npx skills add https://github.com/CrazyDubya/claude-skills --skill accessibility-auditor

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Evaluates web UI for accessibility, including WCAG 2.1 AA criteria, ARIA usage, keyboard navigation, and screen reader considerations.

Core Features & Use Cases

Semantic HTML & ARIA: ensures meaningful markup and ARIA attributes are used correctly.
Keyboard navigation: checks focus order and skip links.
Screen reader readiness: tests live regions and descriptive text.

Quick Start

Run accessibility checks on UI components and apply suggested improvements to reach WCAG compliance.

Frequently Asked Questions about accessibility-auditor

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

FAQPage Schema

How do I audit a website for WCAG 2.1 compliance?▼

WCAG 2.1 compliance auditing evaluates your web UI against Level AA accessibility standards. This Skill checks semantic HTML, ARIA attributes, keyboard navigation, color contrast, focus management, and screen reader compatibility, then provides actionable remediation guidance for each issue found.

What does keyboard navigation testing cover in accessibility audits?▼

Keyboard navigation testing verifies users can access all interactive elements without a mouse. It checks focus order, skip links, and whether all functionality is reachable via keyboard, ensuring your site works for users who rely on keyboard input or assistive technologies.

How do I ensure ARIA attributes are used correctly?▼

ARIA attribute validation checks that semantic roles, live regions, and descriptive properties are applied correctly to your components. Proper ARIA usage makes your UI meaningful to screen readers and assistive technologies, improving accessibility for users with disabilities.

Can I use this to test screen reader compatibility?▼

Yes. Screen reader readiness testing evaluates live regions, descriptive text, and semantic markup so your UI works correctly with assistive technologies. The audit identifies missing labels, improper structure, and other issues that prevent screen readers from conveying content accurately.

What's the difference between semantic HTML and ARIA in accessibility?▼

Semantic HTML provides native meaning and keyboard support built-in; ARIA adds accessible labels and roles to custom components when semantic HTML isn't sufficient. Both are required for full WCAG compliance—semantic HTML first, ARIA to fill gaps.