aria

Audit React UI components for ARIA accessibility and keyboard navigation.

888|82|Updated Aug 13, 2025
One-click install
npx skills add https://github.com/videojs/v10 --skill aria
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aria
Source: https://github.com/videojs/v10/tree/main/.claude/skills/aria
Command: npx skills add https://github.com/videojs/v10 --skill aria

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps developers identify and fix accessibility gaps in UI components by applying ARIA patterns and semantic HTML.

Core Features & Use Cases

  • Focus management and keyboard navigation review
  • ARIA roles, states, and labeling guidance
  • Screen reader compatibility and live region recommendations

Quick Start

To begin, load the ARIA reference material and run a quick accessibility audit on a sample component.

Frequently Asked Questions about aria

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

FAQPage Schema
How do I audit React UI components for ARIA and screen reader accessibility?

ARIA accessibility audits evaluate React UI components against ARIA patterns to identify gaps in semantic HTML. The audit reviews keyboard navigation, focus management, and screen reader compatibility using structured guideline references and templates.

What ARIA roles and focus management patterns do I need for accessible web components?

Accessible web components require correct ARIA roles, states, properties, and logical focus management. You apply these patterns during development and code reviews to ensure keyboard navigation works and screen readers interpret UI elements correctly.

How do I implement keyboard navigation and focus management in web applications?

Keyboard navigation and focus management are implemented by applying ARIA interaction patterns and semantic HTML. This ensures focus moves logically through UI components, satisfying keyboard accessibility requirements during code reviews.

When should I use ARIA live regions for screen reader announcements?

ARIA live regions are recommended when dynamic content updates occur and screen readers need to announce the changes. Accessibility audits identify these scenarios and provide guidance on applying appropriate live region roles.

Does this accessibility audit work for any web UI project or only React?

This accessibility audit targets React and web UI projects specifically. It guides the application of ARIA patterns, keyboard navigation, and labeling requirements for these environments during development and code reviews.

What is the best way to fix UI accessibility gaps during code reviews?

Fixing UI accessibility gaps during code reviews involves applying ARIA patterns and semantic HTML to components. This process targets focus management, keyboard navigation, and labeling issues identified through structured accessibility audits.