a11y-audit

Run axe-core audits and map accessibility violations to WCAG 2.1 AA.

Updated Apr 10, 2026
One-click install
npx skills add https://github.com/Kosmio/skeleton-test --skill a11y-audit-kosmio
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: a11y-audit
Source: https://github.com/Kosmio/skeleton-test/tree/main/.claude/skills/accessibility
Command: npx skills add https://github.com/Kosmio/skeleton-test --skill a11y-audit-kosmio

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires axe-core, puppeteer, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

Web projects often have accessibility gaps that are hard to catch with manual checks alone. This skill runs automated audits (axe-core, with optional Lighthouse) and maps findings to WCAG 2.1 AA, producing a deterministic markdown+JSON report and delta comparisons to track improvements over time.

Core Features & Use Cases

  • Automated accessibility scanning with axe-core across sitemap-defined pages or representative samples.
  • Optional Lighthouse integration to capture performance-related accessibility signals, with explicit skip notes when unavailable.
  • Deterministic reporting in markdown and JSON, plus delta analysis to surface changes between audits.
  • Template-based page discovery to efficiently sample large sites and reveal common template-level issues.
  • Portable, dependency-resilient workflow that stores project state in the workspace (e.g., .a11y-audit/PROJECT_CONTEXT.md) instead of the skill directory.

Quick Start

Run the audit against your local app by executing the bundled scan script with your URLs, then review the generated markdown and JSON reports.

Frequently Asked Questions about a11y-audit

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

FAQPage Schema
How do I run automated WCAG 2.1 AA audits for a web project?

Run automated WCAG 2.1 AA audits by executing axe-core scans against your web project URLs to identify accessibility violations. The process generates deterministic markdown and JSON reports mapping findings directly to WCAG criteria.

Can I track accessibility improvements over time with delta comparisons?

Track accessibility improvements over time by running delta comparisons between audit reports. This surfaces changes in WCAG violations across scans, helping you verify if template-level fixes reduce violations consistently.

Does the axe-core audit work with Astro and Strapi frontends?

The axe-core audit works with Astro and Strapi v5 frontends, single-page applications, and CMS-powered sites. It supports portable, reproducible workflows that resolve dependencies locally and store project state in the workspace.

What is the best way to sample large sites for accessibility violations?

Sample large sites for accessibility violations using template-based page discovery via sitemap or HTML crawl. This efficiently reveals common template-level issues without scanning every individual page URL.

Can I integrate Lighthouse accessibility signals into the audit report?

Integrate optional Lighthouse accessibility signals into the audit report to capture performance-related metrics. The scan provides explicit skip notes when Lighthouse is unavailable, ensuring the axe-core audit remains deterministic.

How do I include automated accessibility scanning in CI workflows?

Include automated accessibility scanning in CI workflows by running the portable, dependency-resilient scan script. It stores project context locally, discovers pages, and outputs reproducible JSON and markdown reports for pipeline validation.