accessibility-audit

Audit frontend code for WCAG 2.1 AA accessibility issues.

8|4|Updated Feb 7, 2026
One-click install
npx skills add https://github.com/adrien-barret/claude-kit --skill accessibility-audit-adrien-barret
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: accessibility-audit
Source: https://github.com/adrien-barret/claude-kit/tree/main/project-template/.claude/skills/accessibility-audit
Command: npx skills add https://github.com/adrien-barret/claude-kit --skill accessibility-audit-adrien-barret

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Frontend teams often struggle to ensure WCAG 2.1 AA accessibility across components, pages and widgets. This Skill provides a structured audit to identify semantic, ARIA, keyboard, color contrast, and screen reader issues, enabling rapid remediation.

Core Features & Use Cases

  • Semantic HTML checks for landmark usage, heading order, labels for form controls, and table semantics.
  • ARIA & interactive widgets validation to ensure appropriate roles, states, and labeling.
  • Keyboard navigation & focus management verification to guarantee reachable controls and visible focus indicators.
  • Contrast & screen reader compatibility checks to meet color contrast thresholds and alt text coverage.
  • Use Case: QA engineers can run this audit on a new frontend feature and generate a prioritized issue list for developers.

Quick Start

To run an accessibility audit on a frontend project, point the skill at the project directory and review the generated findings. For example: audit accessibility-audit path/to/project.

Frequently Asked Questions about accessibility-audit

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

FAQPage Schema
How do I audit my frontend code for WCAG 2.1 AA accessibility?

You can audit frontend code for WCAG 2.1 AA accessibility by pointing the audit tool at your project directory. It analyzes semantic HTML, ARIA roles, keyboard navigation, and color contrast to produce a prioritized issue report for remediation.

What does a WCAG 2.1 AA accessibility audit check for in React or Vue components?

A WCAG 2.1 AA accessibility audit checks React or Vue components for semantic landmark usage, ARIA widget roles, keyboard focus management, visible focus indicators, color contrast thresholds, and screen reader compatibility.

Can I use this accessibility audit on an HTML codebase without framework dependencies?

Yes, you can apply this accessibility audit to any frontend codebase including plain HTML. It requires no external dependencies to evaluate semantic structure, form labels, table semantics, and color contrast.

How do I verify keyboard navigation and focus management for accessible widgets?

To verify keyboard navigation and focus management, the audit examines your interactive widgets to ensure all controls are reachable via keyboard and maintain visible focus indicators, enforcing WCAG 2.1 AA standards.

What is the best way to identify ARIA roles and screen reader issues in my frontend?

The best way to identify ARIA roles and screen reader issues is running an automated audit that validates appropriate roles, states, labeling, and alt text coverage, generating a prioritized list for rapid developer remediation.