skills.rest
jens-wedin
jens-wedinCOMMUNITY
Explore all skills by this author →
GitHub

a11y-qa

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

Updated Feb 26, 2026
Search Tags:#automation#a11y#qa#audit#eslint#wcag#axe-core
One-click install
npx skills add https://github.com/jens-wedin/a11y-skill --skill a11y-qa
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: a11y-qa
Source: https://github.com/jens-wedin/a11y-skill/tree/main/a11y-qa
Command: npx skills add https://github.com/jens-wedin/a11y-skill --skill a11y-qa

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

The QA process for accessibility is often manual, time-consuming, and prone to missed issues; this skill streamlines detection and reporting of accessibility violations, enabling consistent remediation.

Core Features & Use Cases

  • Runtime audits: injects axe-core into live pages to surface WCAG violations during final QA.
  • Static checks: uses eslint-plugin-jsx-a11y on source code for early defect detection in PRs.
  • Full audits: combines static and runtime findings to produce comprehensive accessibility reports for release readiness.

Quick Start

Choose a scan mode and run an accessibility audit on your project to generate a comprehensive report.

Frequently Asked Questions about a11y-qa

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

FAQPage Schema
How do I automate accessibility audits for web applications?▼

Automate accessibility audits by integrating axe-core for runtime scanning and eslint-plugin-jsx-a11y for static source code checks. This combination identifies WCAG violations across multiple routes and generates structured reports with priority levels and recommended fixes.

What is the best way to check WCAG compliance before a release?▼

The best way to check WCAG compliance pre-release is running a full audit that combines static source code analysis with runtime page scans. This merges early defect detection with live page evaluations to produce comprehensive accessibility reports for release readiness.

Can I use eslint to find accessibility issues in my source code?▼

Yes, you can use eslint-plugin-jsx-a11y to perform static checks on your source code. This approach enables early detection of accessibility defects directly within your pull requests before reaching final QA.

How do I generate accessibility reports with recommended fixes?▼

Generate accessibility reports with recommended fixes by running runtime audits that inject axe-core into live pages. The resulting structured reports highlight identified violations and provide specific remediation guidance.

Does axe-core support runtime scanning across multiple routes?▼

Yes, axe-core supports runtime scanning across multiple routes for pre-release QA. Injecting it into live pages surfaces WCAG violations during final testing, which can be combined with static analysis for full audit coverage.

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

Static checks use eslint-plugin-jsx-a11y on source code for early defect detection in PRs, while runtime checks inject axe-core into live pages to surface WCAG violations during final QA. Combining both provides comprehensive accessibility coverage.

Related Skills

Explore More Software Engineering Skills→
easingthemeseasingthemes
6

dx-axe

Automate accessibility testing and remediation of web pages with axe MCP Server.

Community
Advanced
henrique-simoeshenrique-simoes
13

accessibility-audit

Identify WCAG violations and prioritize remediation steps by impact.

Community
Advanced
airoweairowe
14

Accessibility Audit Skill

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

Community
Advanced
mustafazeydanimustafazeydani

accessibility

Automate web accessibility audits against WCAG 2.2 guidelines using Lighthouse.

Community
Advanced