accessibility-code

Audits frontend code for WCAG 2.2 AAA, Section 508, and ARIA correctness.

Updated May 19, 2026
One-click install
npx skills add https://github.com/lord-vinayak/orive-reqcap --skill accessibility-code
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: accessibility-code
Source: https://github.com/lord-vinayak/orive-reqcap/tree/main/.claude/skills/audit/accessibility-code_
Command: npx skills add https://github.com/lord-vinayak/orive-reqcap --skill accessibility-code

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill provides expert-level accessibility audits, reviews, and guidance for frontend code, ensuring compliance with accessibility standards and improving the user experience for everyone.

Core Features & Use Cases

  • Accessibility Audit: Review code for compliance with WCAG, ARIA, and semantic HTML standards.
  • Best Practices: Offer best practices for improving accessibility in HTML, CSS, JavaScript, and UI frameworks.
  • Use Case: When you have a component that needs to be accessible, this Skill can help identify and fix issues related to keyboard navigation, ARIA roles, and screen reader compatibility.

Quick Start

Analyze the accessibility of the following React component code: ```jsx function MyComponent() { // Component code }

Frequently Asked Questions about accessibility-code

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

FAQPage Schema
How do I audit my frontend code for WCAG 2.2 AAA and Section 508 compliance?

A comprehensive accessibility audit reviews your frontend code for semantic structure, keyboard interaction logic, focus management, and ARIA correctness to ensure WCAG 2.2 AAA and Section 508 compliance. It identifies and resolves complex issues missed by automated tools.

What is the best way to fix ARIA roles and screen reader compatibility in HTML and JavaScript?

Fixing ARIA roles and screen reader compatibility requires applying ARIA APG patterns and checking dynamic state communication in your JavaScript and HTML. Expert code reviews identify incorrect ARIA usage and provide guidelines for accessible semantic structure.

How do I check keyboard navigation and focus management in a React component?

Checking keyboard navigation and focus management involves auditing your React component's interaction logic to ensure logical tab order and visible focus states. Code reviews evaluate dynamic state communication and ARIA correctness to resolve keyboard accessibility gaps.

Can automated accessibility tools find all semantic HTML and CSS issues in my code?

Automated tools cannot find all semantic HTML and CSS accessibility issues. An expert audit is required to evaluate keyboard interaction logic, focus management, and dynamic state communication, resolving complex issues that automated scanners consistently miss.

When do I need an expert accessibility review for my frontend code?

You need an expert accessibility review when your frontend code requires compliance with WCAG 2.2 AAA or Section 508 standards. It is essential for resolving complex keyboard navigation, ARIA correctness, and focus management issues beyond automated detection.

Does this accessibility code review work with UI frameworks like React?

Yes, accessibility code reviews work with UI frameworks like React. The audit analyzes component code to identify and fix issues related to keyboard navigation, ARIA roles, and screen reader compatibility within your specific JavaScript and HTML structure.