a11y-check

Detect accessibility issues in TSX/JSX code and provide remediation guidance.

Updated Mar 18, 2026
One-click install
npx skills add https://github.com/mikecubed/agent-orchestration --skill a11y-check-mikecubed
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: a11y-check
Source: https://github.com/mikecubed/agent-orchestration/tree/main/plugins/ccc/skills/a11y-check
Command: npx skills add https://github.com/mikecubed/agent-orchestration --skill a11y-check-mikecubed

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Accessibility pattern enforcement for TypeScript (TSX) and JavaScript (JSX). Detects missing alt text, non-semantic HTML, absent ARIA roles, keyboard-inaccessible interactive elements, and click-only event handlers. Wired into the conductor's review operation.

Core Features & Use Cases

  • Continuous accessibility checks for TSX/JSX components across codebases.
  • Detect missing alt text, non-semantic HTML, absent ARIA roles, keyboard-inaccessible controls, and unlabeled form controls.
  • Supports guided remediation with suggested ARIA attributes, semantic replacements, and keyboard enhancements.

Quick Start

Run an accessibility scan on your TSX/JSX project to surface issues and generate remediation guidance.

Frequently Asked Questions about a11y-check

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

FAQPage Schema
How do I check React components for missing alt text and ARIA roles?

To check React components for accessibility issues, you can scan TSX and JSX codebases to detect missing alt text, absent ARIA roles, and non-semantic HTML. The tool provides structured rules and actionable remediation guidance to fix flagged elements.

What is the best way to enforce web accessibility patterns in a TypeScript UI codebase?

Enforcing web accessibility in a TypeScript UI codebase involves applying automated linting rules to TSX files. This process flags keyboard-inaccessible interactive elements and unlabeled form controls, supporting continuous accessibility checks across your project.

How do I fix keyboard-inaccessible elements detected during an accessibility scan?

To fix keyboard-inaccessible elements detected during a scan, apply the provided guided remediation steps. The tool suggests specific keyboard enhancements and semantic replacements to make interactive elements operable via keyboard navigation.

Can I configure the severity of accessibility issues in TSX files?

Yes, you can configure the severity of accessibility issues detected in TSX files. Configurable severity levels allow you to prioritize remediation efforts and integrate automated checks smoothly into your existing developer workflows.

Does click-only event handler detection work for standard JavaScript JSX files?

Yes, click-only event handler detection works for standard JavaScript JSX files as well as TypeScript TSX. The scanner identifies these handlers to help you implement proper keyboard event alternatives for interactive elements.