accessibility-auditor
NewWeb accessibility specialist for WCAG compliance, ARIA implementation, and inclusive design. Use when auditing websites for accessibility issues, implementing WCAG 2.1 AA/AAA standards, testing with screen readers, or ensuring ADA compliance. Expert in semantic HTML, keyboard navigation, and assistive technology compatibility.
Summary
This skill transforms Claude into a web accessibility specialist that audits websites for WCAG compliance, suggests ARIA implementations, and guides inclusive design.
- It helps developers identify and fix accessibility issues to meet ADA standards and improve user experience for people with disabilities.
Install & Usage
~/.claude.jsonAdd the configuration to "mcpServers": { "accessibility-auditor": { "command": "...", "args": [] } }
/mcpUse Cases
Usage Examples
/accessibility-auditor audit https://example.com for WCAG 2.1 AA violations
Analyze this HTML form for keyboard accessibility and missing labels: [paste HTML]
Check the ARIA implementation on this modal dialog and suggest improvements: [paste code]
Security Audits
Frequently Asked Questions
What is accessibility-auditor?
This skill transforms Claude into a web accessibility specialist that audits websites for WCAG compliance, suggests ARIA implementations, and guides inclusive design. It helps developers identify and fix accessibility issues to meet ADA standards and improve user experience for people with disabilities.
How to install accessibility-auditor?
To install accessibility-auditor: open your mcp config (~/.claude.json), then add the config to "mcpServers": { "accessibility-auditor": { "command": "...", "args": [] } }. Finally, /mcp in Claude Code.
What is accessibility-auditor best for?
accessibility-auditor is a mcp categorized under General. It is designed for: testing, design, security. Created by davila7.
What can I use accessibility-auditor for?
accessibility-auditor is useful for: Audit a webpage for WCAG 2.1 AA compliance and generate a prioritized fix list.; Review ARIA roles and properties on a complex widget to ensure correct screen reader announcements.; Test keyboard navigation flow on a form and identify focus management issues.; Evaluate color contrast ratios for text and interactive elements against WCAG thresholds.; Check semantic HTML structure of a document for proper heading hierarchy and landmark regions.; Simulate screen reader output for a dynamic single-page application route change..