void-accessibility-check

Validates React components against a 7-point accessibility checklist covering semantics, ARIA, keyboard, and contrast.

Updated May 29, 2026
One-click install
npx skills add https://github.com/voidcorp-core/void-harness --skill void-accessibility-check-voidcorp-core
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: void-accessibility-check
Source: https://github.com/voidcorp-core/void-harness/tree/main/packages/cli/core-assets/packs/pack-react/skills/void-accessibility-check
Command: npx skills add https://github.com/voidcorp-core/void-harness --skill void-accessibility-check-voidcorp-core

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? React components often ship with accessibility defects—missing labels, broken keyboard navigation, low contrast, or tiny touch targets—that block users relying on assistive technology. This Skill applies a concrete 7-point gate to every component you create or edit so violations are caught before they ship. ## Core Features & Use Cases - 7-Point Accessibility Gate: Checks semantic HTML, programmatic labels, keyboard navigation, focus management, WCAG AA contrast, 44x44px touch targets, and reduced-motion support. - Radix-First Guidance: Steers you toward Radix primitives that handle roles, keyboard behavior, and focus trapping correctly by default. - Verification Workflow: Directs Lighthouse audits (target score 100), manual keyboard walkthroughs, and screen reader testing with VoiceOver, NVDA, or TalkBack. - Use Case: When you ask an agent to add a dialog or icon button to a React app, this Skill auto-applies and ensures the result has an accessible name, focus trap, Escape handling, and sufficient contrast. ## Quick Start Ask the agent to add a new button or card component to your React app and it will apply the accessibility checklist automatically.

Frequently Asked Questions about void-accessibility-check

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

FAQPage Schema
How do I make a React component accessible?

Apply a checklist covering semantic HTML tags, programmatic labels via aria-label or label elements, keyboard operability with Tab and Enter, focus management on context changes, WCAG AA contrast ratios, 44x44px touch targets, and prefers-reduced-motion support.

What contrast ratio does WCAG AA require for text?

WCAG AA requires 4.5:1 contrast for normal text and 3:1 for large text (18px bold or 24px and above). Interactive elements like button borders and focus rings need 3:1 against adjacent colors.

Does Radix UI handle accessibility automatically?

Radix primitives set correct ARIA roles, keyboard navigation, and focus trapping for components like dialogs and menus. You still must provide accessible names, maintain contrast, and avoid stripping focus outlines in custom styling.

Why is placeholder text not a valid input label?

Placeholders disappear on focus and are not announced as labels by screen readers, leaving the input unnamed. Use a real label element linked with htmlFor or an aria-label attribute instead.

When should I test with a screen reader?

Test at least one new component per pull request using macOS VoiceOver, Windows NVDA, Android TalkBack, or iOS VoiceOver. Combine this with a Lighthouse audit targeting a score of 100 and a manual keyboard walkthrough.