One-click install
npx skills add https://github.com/concept2cure/ClinicalSageAI-2-replit --skill accessibility-enforcement
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: accessibility-enforcement
Source: https://github.com/concept2cure/ClinicalSageAI-2-replit/tree/main/.claude/skills/accessibility-enforcement
Command: npx skills add https://github.com/concept2cure/ClinicalSageAI-2-replit --skill accessibility-enforcement

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Accessibility is not optional for Concept2Cure's regulatory customers (FDA, EMA, PMDA, Health Canada, enterprise pharma). Many of them require WCAG 2.2 AA conformance in procurement. Every shipped component must meet this bar.

Core Features & Use Cases

  • Audit focus order and verify keyboard traps across complex components.
  • Validate ARIA correctness, semantic HTML, and accessible names for all interactive controls.
  • Enforce color contrast and respect reduced motion preferences to ensure readable UI.
  • Provide guardrails for design reviews and regulated-delivery readiness with clear pass/fail criteria.

Quick Start

Initiate a WCAG 2.2 AA compliance review for the next UI change in client/src.

Frequently Asked Questions about accessibility-enforcement

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

FAQPage Schema
How do I ensure WCAG 2.2 AA conformance for React UI components?

Keyboard accessibility is verified by auditing focus order and checking for keyboard traps across complex components. This ensures all interactive controls are fully navigable without a mouse.

Can I automate focus management and keyboard trap checks during design reviews?

Accessibility checks enforce color contrast ratios and validate motion reduction preferences to ensure readable UI. These guardrails satisfy WCAG 2.2 AA criteria for visually sensitive and motion-sensitive users.

Do I need WCAG 2.2 AA compliance for FDA or EMA regulated deliveries?

Regulated-delivery preparation is achieved by applying WCAG 2.2 AA guardrails during design reviews and component development. This provides testable conformance checks across React UI codebases for regulatory submission.

What's the best way to validate ARIA correctness and semantic HTML in React codebases?

Accessible names are verified by auditing all interactive controls for ARIA correctness and semantic HTML. This ensures every UI element meets WCAG 2.2 AA conformance standards during component development.