cabinet-accessibility

Evaluate .tsx UI components against WCAG guidelines for accessibility issues.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/orenmagid/claude-cabinet --skill cabinet-accessibility
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cabinet-accessibility
Source: https://github.com/orenmagid/claude-cabinet/tree/main/templates/skills/cabinet-accessibility
Command: npx skills add https://github.com/orenmagid/claude-cabinet --skill cabinet-accessibility

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Helps ensure your application is usable by people with diverse abilities by identifying keyboard navigation gaps, focus management issues, contrast deficiencies, unlabeled interactive elements, and semantic structure problems during audits and code reviews.

Core Features & Use Cases

  • Automated checks across .tsx components to surface accessibility issues such as missing ARIA labeling, improper heading order, insufficient color contrast, and inaccessible interactive elements.
  • Guidance on keyboard navigation, focus traps, landmark usage, and WCAG alignment to support audits and UI reviews.
  • Use case: integrate into the development workflow to catch regressions early and deliver inclusive software.

Quick Start

Initiate an accessibility audit on your app's UI to generate prioritized findings.

Frequently Asked Questions about cabinet-accessibility

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

FAQPage Schema
How do I audit my React tsx components for WCAG compliance?

To audit tsx components for WCAG compliance, this skill evaluates UI elements against accessibility guidelines to surface keyboard navigation, focus management, contrast, and semantic structure gaps. It generates prioritized findings to guide remediation across your codebase.

Can I check ARIA attributes and heading hierarchy during a code review?

Yes, you can check ARIA attributes and heading hierarchy during a code review. The skill assesses ARIA labeling, landmark usage, and heading order across src/**/*.tsx files to identify semantic structure problems and inaccessible interactive elements.

What is the best way to find keyboard navigation and focus trap issues in my UI?

The best way to find keyboard navigation and focus trap issues is to apply this skill during component reviews. It identifies focus management gaps and inaccessible interactive elements, providing guidance to align your application with WCAG standards.

What accessibility issues are detected in tsx files?

Detected accessibility issues in tsx files include missing ARIA labeling, improper heading order, insufficient color contrast, keyboard navigation gaps, and focus management deficiencies. The skill evaluates these against WCAG guidelines to support inclusive design.

Does this accessibility audit work on any React codebase?

This accessibility audit works on React codebases containing tsx components. It scans src/**/*.tsx files to evaluate UI components against WCAG guidelines, requiring no external dependencies to identify issues and guide remediation.