a11y-critic

Review code accessibility design for ARIA patterns and focus management.

1|Updated Mar 2, 2026
One-click install
npx skills add https://github.com/zivtech/harsh-critic --skill a11y-critic
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: a11y-critic
Source: https://github.com/zivtech/harsh-critic/tree/main/a11y-critic/.claude/skills/a11y-critic
Command: npx skills add https://github.com/zivtech/harsh-critic --skill a11y-critic

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill provides a thorough, evidence-driven review of accessibility design decisions in code, identifying issues that automated testing may miss.

Core Features & Use Cases

  • Design Review: Evaluates ARIA pattern correctness, focus management, state communication, and multi-perspective access.
  • Use Case: For reviewing code for accessibility design quality, especially for custom interactive components and focus management in modals and drawers.

Quick Start

Run the a11y-critic skill on your code to review accessibility design decisions.

Frequently Asked Questions about a11y-critic

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

FAQPage Schema
How do I check ARIA patterns and focus management for accessibility compliance?▼

To check ARIA patterns and focus management, review the code against the WAI-ARIA Authoring Practices Guide and WCAG 2.2 criteria to identify design decisions that may not be compliant.

Why does automated accessibility testing miss some code review issues?▼

Automated accessibility testing misses design-level issues because it cannot evaluate multi-perspective access, state communication, or complex ARIA pattern correctness in custom interactive components.

How do I review accessibility design for custom interactive components like modals?▼

Review accessibility design for modals by evaluating focus management, state communication, and ARIA pattern correctness against WAI-ARIA Authoring Practices Guide standards.

What's the best way to evaluate code for WCAG 2.2 compliance after automated testing?▼

The best way to evaluate code for WCAG 2.2 compliance after automated testing is to conduct an evidence-driven review focusing on ARIA patterns, focus management, and multi-perspective access.

Do I need automated accessibility testing before reviewing code for design quality?▼

Yes, you need automated accessibility testing first because the accessibility design review operates on code that has already passed automated testing to identify deeper design-level non-compliance.

What limitations exist when reviewing state communication in accessibility design?▼

A limitation when reviewing state communication is that it requires knowledge of WAI-ARIA Authoring Practices Guide patterns and WCAG 2.2 criteria to accurately identify non-compliant design decisions.