skills.rest
cropsgg
cropsggCOMMUNITY
Explore all skills by this author →
GitHub

accessibility-audit

Automate WCAG 2.1 AA accessibility checks with axe-core and jsx-a11y.

15|5|Updated May 17, 2026
Search Tags:#accessibility#audit#wcag#screen-reader#axe-core#keyboard-navigation#jsx-a11y
One-click install
npx skills add https://github.com/cropsgg/skills --skill accessibility-audit-cropsgg
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: accessibility-audit
Source: https://github.com/cropsgg/skills/tree/main/skills/engineering/accessibility-audit
Command: npx skills add https://github.com/cropsgg/skills --skill accessibility-audit-cropsgg

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automated UI changes often introduce WCAG 2.1 AA accessibility regressions that disrupt keyboard navigation, screen reader experiences, and visual contrast. This Skill unifies automated checks with manual verification to catch these issues early in development.

Core Features & Use Cases

  • Combines automated checks (axe-core, jsx-a11y) with guided manual verification across components (dialogs, forms, menus, tables).
  • Provides a structured remediation prioritization workflow and evidence capture to support audits and reviews.
  • Use Case: when shipping a new component or modifying an interaction, run the audit to generate a report showing blockers, major issues, and recommended fixes.

Quick Start

Run an automated accessibility scan and manual verification to identify WCAG 2.1 AA issues in updated UI components.

Frequently Asked Questions about accessibility-audit

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

FAQPage Schema
How do I audit UI components for WCAG 2.1 AA compliance before release?▼

To audit UI components for WCAG 2.1 AA compliance, run automated axe-core and jsx-a11y checks alongside manual keyboard focus and screen reader verification to catch accessibility regressions in updated interfaces.

What is the best way to catch screen reader and keyboard navigation regressions in web apps?▼

Catching screen reader and keyboard navigation regressions requires combining automated jsx-a11y scans with guided manual verification of keyboard focus and screen reader sanity checks across components like dialogs and forms.

Does this accessibility audit workflow support React components using jsx-a11y?▼

Yes, the accessibility audit workflow supports React components by integrating jsx-a11y automated checks to detect accessibility risks in JSX code before performing manual focus and contrast validation.

How do I prioritize accessibility remediation tasks identified by axe-core?▼

Prioritize accessibility remediation tasks by using the structured workflow to generate a report categorizing detected axe-core issues into blockers, major issues, and recommended fixes for evidence-based audits.

Can I validate visual contrast ratios for WCAG compliance during UI development?▼

Yes, you can validate visual contrast ratios during UI development as part of the accessibility audit, combining automated checks with manual visual contrast validation to ensure WCAG 2.1 AA conformance.

Related Skills

Explore More Software Engineering Skills→
matteocervellimatteocervelli
25

accessibility-checker

Identify and report WCAG 2.1 Level AA accessibility violations on web pages.

Community
Advanced
cosmicstack-labscosmicstack-labs
364

accessibility-testing

Audit web interfaces for WCAG 2.1/2.2 failures and usability blockers.

Official
Intermediate
naporin0624naporin0624
3

a11y-self-check

Validate generated HTML/JSX/TSX output for WCAG 2.1 AA accessibility compliance.

Community
Basic
Anuj23105Anuj23105
1

accessibility-auditing

Tests web page and UI component accessibility compliance with WCAG 2.1 AA/AAA standards.

Community
Advanced