skills.rest
airowe
airoweCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

Accessibility Audit Skill

Audit web projects for WCAG 2.1 violations using axe-core and eslint-plugin-jsx-a11y.

14|5|Updated Jan 24, 2026
Search Tags:#accessibility#a11y#web development#audit#compliance#wcag
One-click install
npx skills add https://github.com/airowe/claude-a11y-skill --skill accessibility-audit-skill
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Accessibility Audit Skill
Source: https://github.com/airowe/claude-a11y-skill/tree/main
Command: npx skills add https://github.com/airowe/claude-a11y-skill --skill accessibility-audit-skill

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automates the process of identifying and rectifying accessibility issues in web projects, ensuring compliance with WCAG standards and improving user experience for everyone.

Core Features & Use Cases

  • Comprehensive Audits: Conducts both runtime (browser-based) and static (code analysis) accessibility checks.
  • Multi-Standard Compliance: Verifies against WCAG 2.1 Level A and AA, plus general best practices.
  • Use Case: Before launching a new feature, run a full scan to catch potential accessibility barriers in your React application, ensuring it's usable by people with disabilities and meets legal requirements.

Quick Start

Use the accessibility skill to run a full scan on the current project.

Frequently Asked Questions about Accessibility Audit Skill

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

FAQPage Schema
How do I run an accessibility audit on my web project?▼

Run an accessibility audit by selecting from runtime, static, or full scan modes to automatically detect WCAG 2.1 Level A/AA violations and best practice issues across your web project's pages and source code.

What is the difference between runtime and static accessibility scanning?▼

Runtime accessibility scanning evaluates discoverable pages in a browser using axe-core, while static accessibility scanning analyzes source code directly using eslint-plugin-jsx-a11y to catch code-level WCAG violations.

Can I use this accessibility audit tool with my React application?▼

Yes, you can audit React applications using static analysis with eslint-plugin-jsx-a11y to identify code-level accessibility barriers, alongside runtime browser scanning to catch WCAG compliance issues.

Does this tool check WCAG 2.1 AA compliance?▼

Yes, the accessibility audit verifies compliance against WCAG 2.1 Level A and AA standards, alongside general best practices, ensuring your web project meets legal accessibility requirements.

When should I run a full accessibility scan instead of a static scan?▼

Run a full scan before launching new features to catch all potential accessibility barriers by combining runtime browser scanning with static code analysis, whereas a static scan only checks source code.

Related Skills

Explore More Software Engineering Skills→
jens-wedinjens-wedin

a11y-qa

Audit web applications for accessibility violations via axe-core and eslint-plugin-jsx-a11y.

Community
Intermediate
Montte-erpMontte-erp
6

wcag-audit-patterns

Audit web pages for WCAG 2.2 violations with automated and manual checks.

Official
Intermediate
notwillknotwillk

create-github-action

Generate GitHub Actions workflow YAML files for CI/CD automation.

Community
Advanced
Higashi-KotaHigashi-Kota

a11y

Audits UI components for WCAG 2.2 AA and ARIA compliance.

Community
Intermediate