audit-a11y

Run WCAG 2.2 AA accessibility audits on Angular frontends with axe-core and ESLint.

4|2|Updated Nov 28, 2018
One-click install
npx skills add https://github.com/esassoc/wadnrforesthealth --skill audit-a11y-esassoc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: audit-a11y
Source: https://github.com/esassoc/wadnrforesthealth/tree/main/.claude/skills/audit-a11y
Command: npx skills add https://github.com/esassoc/wadnrforesthealth --skill audit-a11y-esassoc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The audit-a11y skill helps developers and QA teams identify WCAG 2.2 AA accessibility issues across a web app by combining runtime and static checks and delivering prioritized results.

Core Features & Use Cases

  • Runtime accessibility scans using Playwright + axe-core across pages in the running app.
  • Static accessibility checks on HTML templates using an ESLint template rules config.
  • Generates a summarized report with overall score, grade, per-page scores, and prioritized fix recommendations.
  • Use Case: A team wants to verify accessibility across an Angular frontend before release and quickly identify critical violations.

Quick Start

Run the accessibility audit against the running app to produce a11y results.

Frequently Asked Questions about audit-a11y

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

FAQPage Schema
How do I run a WCAG 2.2 AA accessibility audit on an Angular frontend?

To run a WCAG 2.2 AA accessibility audit, this skill executes runtime axe-core scans via Playwright and static ESLint template checks against your running Angular dev server to identify violations and output a JSON summary report.

What is the difference between runtime axe-core scans and static ESLint template checks?

Runtime axe-core scans use Playwright to detect live DOM accessibility violations in the running app, while static ESLint template checks analyze HTML templates directly to catch accessibility issues during development before runtime.

Do I need a running dev server to check for WCAG 2.2 AA violations?

Yes, a running dev server is required. The accessibility audit uses Playwright to execute runtime axe-core scans against live web pages, alongside static ESLint template checks, to produce comprehensive violation reports.

Can I automate accessibility testing with Playwright and axe-core before release?

Yes, you can automate accessibility testing by running Playwright with axe-core across your application pages. This skill combines those runtime scans with static ESLint checks to generate scores, grades, and prioritized fixes for QA workflows.

How do I get prioritized accessibility fix recommendations from an automated audit?

To get prioritized accessibility fix recommendations, this skill runs runtime and static scans, then generates a summarized JSON report containing an overall score, per-page grades, and a prioritized list of critical WCAG 2.2 AA violations to address.

What limitations exist when using ESLint template configs for static accessibility analysis?

Static ESLint template checks are limited to analyzing HTML templates and cannot catch dynamic DOM changes or runtime accessibility issues, which require running Playwright and axe-core scans against the live application.