accessibility-audit

Audit React/TypeScript applications for WCAG 2.2 Level AA conformance issues.

7|3|Updated Oct 19, 2025
One-click install
npx skills add https://github.com/cskiro/annex --skill accessibility-audit-cskiro
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: accessibility-audit
Source: https://github.com/cskiro/annex/tree/main/skills/accessibility-audit
Command: npx skills add https://github.com/cskiro/annex --skill accessibility-audit-cskiro

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires eslint, jest-axe, @axe-core/playwright.

What problem does it solve?

Comprehensive accessibility auditing for React/TypeScript apps with a risk-based severity rubric.

Core Features & Use Cases

  • Multi-layer Auditing: Static, runtime, and manual validation
  • Severity-based Prioritization: Critical, High, Medium, Low
  • MUI Awareness: Reduces false positives on common UI libraries

Quick Start

Trigger an accessibility audit for a page or component to generate a gap report.

Frequently Asked Questions about accessibility-audit

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

FAQPage Schema
How do I audit React components for WCAG 2.2 AA accessibility issues?

WCAG 2.2 AA audits identify conformance gaps in React apps using static analysis (ESLint), runtime validation (jest-axe), and manual checks. This Skill combines these layers to detect issues like missing labels, color contrast failures, and keyboard navigation problems, then prioritizes them by risk-based severity.

Can I use accessibility auditing with Material-UI components?

Yes. This Skill includes MUI awareness to reduce false positives on Material-UI components while still catching real accessibility gaps. It validates MUI implementations against WCAG 2.2 Level AA standards alongside generic React patterns.

What's the difference between static analysis and runtime accessibility testing?

Static analysis (ESLint) catches code-level issues like missing attributes before runtime. Runtime testing (jest-axe, Playwright) validates actual DOM behavior and interactions. This Skill layers both to find gaps static tools miss and confirm fixes work in real browser environments.

How does risk-based severity scoring work for accessibility issues?

Risk-based severity combines Impact (how many users are affected) and Likelihood (how often the issue occurs) to score issues as Critical, High, Medium, or Low. This lets you prioritize remediation on the gaps that matter most to your users.

What output formats does an accessibility audit generate?

Audits produce JSON and Markdown reports. JSON enables programmatic integration with CI/CD pipelines and dashboards; Markdown provides human-readable gap reports with remediation priorities and specific WCAG criteria references.

Do I need ESLint, jest-axe, and Playwright all installed to run an audit?

Yes. This Skill depends on ESLint (static checks), jest-axe (runtime DOM validation), and Playwright (browser automation) to perform the full multi-layer audit. All three are required for comprehensive WCAG 2.2 coverage.