ui-a11y

Run axe-core accessibility audits via Playwright against a dev server.

1|Updated Apr 1, 2026

Search Tags:#automation #accessibility #a11y #wcag #playwright #axe-core

Ready to run

npx skills add https://github.com/charleshall888/cortex-command --skill ui-a11y-charleshall888

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ui-a11y
Source: https://github.com/charleshall888/cortex-command/tree/main/plugins/cortex-ui-extras/skills/ui-a11y
Command: npx skills add https://github.com/charleshall888/cortex-command --skill ui-a11y-charleshall888

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Run a browser-rendered WCAG 2.1 AA audit against the running dev server to surface accessibility issues that are visible only in a live render.

Core Features & Use Cases

Automated a11y testing: Validate rendered accessibility using axe-core via Playwright.
Targeted checks: Scan the base URL or a specific path and emit a compact report to ui-check-results/a11y.json.
Use Case: Ideal for integrating accessibility verification into local development and CI to catch issues early.

Quick Start

Run the a11y audit on the running dev server and write the results to ui-check-results/a11y.json.

Frequently Asked Questions about ui-a11y

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

FAQPage Schema

How do I run automated WCAG 2.1 AA accessibility checks on a local dev server?▼

You run automated accessibility checks by executing an axe-core audit through Playwright against your running dev server, which surfaces live-render WCAG 2.1 AA issues and outputs a compact report to ui-check-results/a11y.json.

What is browser-rendered accessibility testing and why use it for WCAG compliance?▼

Browser-rendered accessibility testing audits a live DOM to surface issues invisible to static code analysis. It validates WCAG compliance dynamically by running axe-core via Playwright against your running dev server.

Do I need Playwright and uv installed to run axe-core a11y audits?▼

Yes, running axe-core a11y audits requires uv, Playwright binaries, and the axe-core library installed locally to execute browser-rendered audits against your running dev server.

Can I target a specific path for accessibility testing instead of the base URL?▼

Yes, the accessibility audit can auto-detect the base URL or use a configured path for targeted checks, allowing you to focus the axe-core Playwright scan on specific web app routes.

What is the best way to integrate a11y verification into local development and CI?▼

Integrate a11y verification into local development and CI by running automated axe-core audits through Playwright against your running dev server, catching accessibility issues early and outputting a compact JSON report.

Why does my accessibility audit require a running dev server to detect WCAG issues?▼

The accessibility audit requires a running dev server because it uses Playwright to execute a browser-rendered audit, catching WCAG issues that only surface in a live render rather than static source code.