accessibility-scan

Run Pa11y, axe-core, and Lighthouse audits across web pages with JSON scores.

Updated Feb 28, 2026

Search Tags:#accessibility #web testing #lighthouse #axe-core #pa11y #a11y audit #json scoring

Ready to run

npx skills add https://github.com/cosmicdreams/claude-plugins --skill accessibility-scan

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: accessibility-scan
Source: https://github.com/cosmicdreams/claude-plugins/tree/main/improve/skills/accessibility-scan
Command: npx skills add https://github.com/cosmicdreams/claude-plugins --skill accessibility-scan

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires pa11y, @axe-core/puppeteer, puppeteer, lighthouse, chrome-launcher, and includes scripts (resource) components.

What problem does it solve?

This Skill removes guesswork from accessibility work by producing repeatable, machine-checkable measurements instead of relying on subjective review.

Core Features & Use Cases

Multi-tool accessibility audit: Runs Pa11y, axe-core, and Lighthouse accessibility checks against multiple pages.
Quantified scoring for experiments: Outputs a JSON “score tuple” plus per-page results to track improvement over time.
Local-site friendly page discovery: Finds pages via an explicit URL list, sitemap.xml, or a homepage crawl fallback (useful for DDEV-style local sites).

Quick Start

Run accessibility-scan against your local site’s base URL by providing it as the first argument, e.g., node a11y-scan.mjs https://your-site.ddev.site.

Frequently Asked Questions about accessibility-scan

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

FAQPage Schema

How do I automate web accessibility audits with Pa11y and axe-core?▼

Run automated accessibility audits by executing a Node.js script with Puppeteer-driven Pa11y and axe-core scanners against target URLs. This generates machine-checkable JSON scores and per-page breakdowns to quantify regressions.

What is the best way to quantify accessibility improvements during local development?▼

Quantify accessibility improvements by generating a JSON score tuple from multi-tool audits. Running Pa11y, axe-core, and Lighthouse against local development URLs provides a repeatable baseline for programmatic comparison over time.

Can I scan a local DDEV site for accessibility issues without a predefined URL list?▼

Yes, you can scan local DDEV sites without a predefined URL list. The tool discovers pages automatically via sitemap.xml parsing or a homepage crawl fallback when you provide your local base URL as the input argument.

Do I need Node.js and Puppeteer to run Lighthouse accessibility checks?▼

Yes, Node.js and Puppeteer are required dependencies. The tool uses Puppeteer-driven scanners alongside chrome-launcher to execute Lighthouse, Pa11y, and axe-core checks and return structured JSON accessibility results.

How does multi-tool accessibility testing compare to using a single Lighthouse audit?▼

Multi-tool testing combines Pa11y, axe-core, and Lighthouse to cross-validate findings. Unlike a single audit, it outputs a combined JSON score tuple enabling precise regression tracking across continuous experimentation workflows.