skills.rest
bingeli1379
bingeli1379COMMUNITY
Explore all skills by this author →
GitHub

accessibility

Audit web accessibility for WCAG 2.1 AA compliance using axe-core and eslint-plugin-jsx-a11y.

2|Updated Apr 6, 2026
Search Tags:#accessibility#a11y#wcag#static-analysis#axe-core#eslint-plugin-jsx-a11y
One-click install
npx skills add https://github.com/bingeli1379/eli-claude-marketplace --skill accessibility-bingeli1379
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: accessibility
Source: https://github.com/bingeli1379/eli-claude-marketplace/tree/main/plugins/eureka-sdd/skills/accessibility
Command: npx skills add https://github.com/bingeli1379/eli-claude-marketplace --skill accessibility-bingeli1379

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Audit web accessibility across projects to ensure WCAG 2.1 AA compliance and keyboard/screen-reader usability.

Core Features & Use Cases

  • Runtime accessibility scanning using axe-core to test live pages for WCAG violations and best practices.
  • Static analysis using eslint-plugin-jsx-a11y to catch JSX/JSX-like accessibility issues in source code.
  • Configurable scan modes: runtime, static, and full, to balance depth and speed in development, testing, and CI.
  • Automated reporting with violation details, affected elements, and remediation guidance for quick fixes.

Quick Start

Run an accessibility audit on your project to identify WCAG violations and improvements.

Frequently Asked Questions about accessibility

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

FAQPage Schema
How do I audit web accessibility for WCAG 2.1 AA compliance?▼

Audit web accessibility by running axe-core runtime scans and eslint-plugin-jsx-a11y static analysis to detect WCAG 2.1 AA violations, generating automated reports with remediation guidance for affected elements.

Can I use axe-core to test single-page apps for screen-reader usability?▼

Yes, axe-core runtime scanning tests live pages of dynamic single-page apps for keyboard and screen-reader usability, identifying WCAG violations and best practice issues across interactive components.

What's the best way to catch JSX accessibility issues during development?▼

Use eslint-plugin-jsx-a11y static analysis to catch JSX accessibility issues directly in source code, preventing violations before runtime and integrating smoothly into development and CI workflows.

Does this accessibility audit support both static sites and multi-page apps?▼

Yes, the audit applies to dynamic single-page apps, static sites, and multi-page apps, offering configurable runtime, static, and full scan modes to balance depth and speed across different project architectures.

How do automated accessibility reports help fix WCAG violations?▼

Automated accessibility reports provide detailed violation descriptions, identify affected DOM elements, and issue remediation guidance, enabling developers to apply quick fixes directly to the flagged 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
cslsoftwarescslsoftwares

quality-bug-triage

Convert informal bug reports into structured tickets with severity and reproduction steps.

Community
Intermediate
pedronauckpedronauck
567

a11y-testing

Automate accessibility testing with jest-axe and Playwright axe-core.

Community
Intermediate
kaeligkaelig
7

accessibility-auditor

Review generated components for WCAG 2.2 compliance and produce prioritized accessibility reports.

Community
Advanced