a11y

Audit web pages for WCAG 2.2 AA violations using axe-core and Lighthouse.

1|Updated Apr 14, 2026
One-click install
npx skills add https://github.com/hschne/pi-stuff --skill a11y-hschne
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: a11y
Source: https://github.com/hschne/pi-stuff/tree/main/skills/a11y
Command: npx skills add https://github.com/hschne/pi-stuff --skill a11y-hschne

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires node, @axe-core/cli, and includes scripts (resource) and references (resource) components.

What problem does it solve?

Manually auditing web pages for accessibility issues is time-consuming, error-prone, and often misses critical violations that exclude users with disabilities and expose organizations to legal compliance risks under WCAG, ADA, and Section 508.

Core Features & Use Cases

  • Automated Scanning: Run fast, parseable accessibility audits using axe-core CLI, Lighthouse, or Playwright with axe-core injection to catch common WCAG 2.2 AA violations.
  • Systematic Fix Workflow: Triage violations by severity, fix issues at the token/theme level to prevent recurrence, and re-run audits to confirm zero critical or serious issues.
  • Manual Validation: Complete keyboard navigation walkthroughs, focus trap checks, zoom tests, and reduced motion validation to catch issues automated tools miss.
  • Use Case: For a public-facing SaaS dashboard, use this skill to identify and fix contrast failures, missing alt text, and keyboard navigation gaps to meet compliance requirements before launch.

Quick Start

Use the a11y skill to run a full accessibility audit on the live staging site at https://staging.example.com and fix all critical and serious WCAG violations.

Frequently Asked Questions about a11y

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

FAQPage Schema
How do I audit a live web page for WCAG 2.2 AA violations?

Run automated accessibility scans using axe-core CLI or Lighthouse to detect WCAG 2.2 AA violations like contrast failures and missing alt text, then triage issues by severity to resolve critical and serious gaps before launch.

What's the best way to fix recurring contrast and ARIA errors in a web application?

Fix recurring contrast and ARIA errors by applying corrections at the token and theme levels, establishing a systematic workflow that prevents recurrence, and re-running automated web audits to confirm zero critical violations remain.

Can I use axe-core to check keyboard navigation and focus traps on a SaaS dashboard?

axe-core automated scanning catches common ARIA and contrast issues, but you must perform manual keyboard navigation walkthroughs, focus trap checks, and zoom tests to validate accessibility gaps that automated tools miss on a SaaS dashboard.

Do I need Node installed to run automated accessibility audits?

Yes, you need Node installed because the automated accessibility auditing workflow depends on the @axe-core/cli package to execute fast, parseable web audits and identify WCAG compliance gaps on live sites.

Why does my web accessibility audit miss keyboard navigation issues?

Automated accessibility audits miss keyboard navigation issues because tools like axe-core primarily detect structural ARIA errors and contrast failures, requiring manual POUR checklist validation and focus trap walkthroughs to catch interactive gaps.