skills.rest
elsolal
elsolalCOMMUNITY
Explore all skills by this author →
GitHub

a11y-enforcer

Identify WCAG 2.2 AA accessibility issues across URLs and code paths.

1|Updated Jan 20, 2026
Search Tags:#accessibility#a11y#audit#keyboard#aria#wcag22
One-click install
npx skills add https://github.com/elsolal/Skillz-Claude-Codex-And-More --skill a11y-enforcer
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: a11y-enforcer
Source: https://github.com/elsolal/Skillz-Claude-Codex-And-More/tree/main/.claude/skills/a11y-enforcer
Command: npx skills add https://github.com/elsolal/Skillz-Claude-Codex-And-More --skill a11y-enforcer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Audit accessibility systematically. Not a nice-to-have — a gate to compliance and real UX impact.

Core Features & Use Cases

  • Scan URLs or code paths (pages, components, and forms) for WCAG 2.2 AA conformance.
  • Output structured findings with severity, location, and remediation guidance, suitable for PR reviews, QA, and pre-ship checks.
  • Provide actionable remediation guidance, including code-level fixes and validation steps for accessibility issues.

Quick Start

Run an accessibility audit on a live URL to return WCAG 2.2 AA findings with suggested fixes.

Frequently Asked Questions about a11y-enforcer

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

FAQPage Schema
How do I audit a web page for WCAG 2.2 AA compliance?▼

To audit a web page for WCAG 2.2 AA compliance, provide the URL or code path to run automated checks using Playwright and axe-core, returning a structured report with severity levels, issue locations, and remediation guidance.

Can I check my source code for accessibility issues before deploying?▼

Yes, you can check source code for accessibility issues by scanning code paths like pages, components, and forms. It applies static analysis with predefined rules to identify ARIA and keyboard issues, providing code-level fixes.

What is the best way to integrate accessibility checks into a pull request review?▼

The best way to integrate accessibility checks into a PR review is running audits on modified components to output structured findings. These findings include severity, exact locations, and actionable remediation steps suitable for QA and pre-ship checks.

Does this accessibility audit cover both live URLs and static code?▼

Yes, this accessibility audit covers both live URLs and static code. It executes dynamic checks via Playwright and axe-core for URLs, while applying static analysis with predefined rules for code paths to ensure full coverage.

What remediation guidance is provided for identified ARIA and keyboard issues?▼

The remediation guidance provided for ARIA and keyboard issues includes actionable code-level fixes and validation steps. The structured report details the exact location and severity to help systematically resolve WCAG 2.2 AA failures.

Related Skills

Explore More Legal & Compliance Skills→
joe-watkinsjoe-watkins
1

a11y-tester

Run axe-core accessibility tests on web pages via Playwright MCP.

Community
Advanced
00PrabalK0000PrabalK00
1

mobile-release-checker

Identify release blockers across iOS and Android build artifacts and configurations.

Community
Intermediate
MolcajeteAIMolcajeteAI
2

accessibility-testing

Automate axe-core accessibility audits in Playwright and Vitest for React applications.

Official
Intermediate
leboncoinleboncoin
92

check-accessibility

Automate WCAG 2.1 AA accessibility testing of Spark UI components with Playwright.

Official
Intermediate