a11y-local

Audit a running frontend for WCAG violations using axe-core CLI.

140|20|Updated Jun 20, 2026
One-click install
npx skills add https://github.com/zekiriabd/SDD-Pro --skill a11y-local
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: a11y-local
Source: https://github.com/zekiriabd/SDD-Pro/tree/main/.sdd/skills/a11y-local
Command: npx skills add https://github.com/zekiriabd/SDD-Pro --skill a11y-local

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill gives Tech Leads a consistent way to audit a running frontend for accessibility issues locally before pushing changes, without modifying generated application code or duplicating CI verdict logic.

Core Features & Use Cases

  • Local axe-core scanning: Audits one or more frontend URLs using the axe-core CLI and saves a temporary report.
  • Unified telemetry ingestion: Sends the report through the existing accessibility ingestion bridge into console.db for the audited FEAT.
  • Actionable verdicts: Renders green, warning, or red results with severity counts and WCAG-related classifications.
  • Use Case: Before opening a pull request, a Tech Lead can scan a locally served React frontend, record the findings for a FEAT, and determine whether frontend work needs to be rerun.

Quick Start

Ask the Skill to run a local accessibility audit against the running frontend for FEAT number 12 and report the verdict.

Frequently Asked Questions about a11y-local

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

FAQPage Schema
How do I run a local accessibility audit before pushing frontend changes?

Run a local accessibility audit by requesting a scan against your running frontend URL for a specific FEAT. The Skill uses axe-core CLI to scan, persist results to console.db, and render a green, warning, or red verdict.

What is a local WCAG compliance check and how does it classify violations?

A local WCAG compliance check scans a running frontend for accessibility violations using axe-core, classifies findings by severity counts and WCAG-related categories, and records a consistent local verdict before pushing code.

Do I need Node and axe-core CLI installed to run local accessibility testing?

Yes, local accessibility testing requires Node and axe-core CLI availability. It also relies on existing ingest_axe and query_console_db tooling to scan, persist, classify, and render the audit results.

Can I use this accessibility scanner outside of my standard CI pipeline?

Yes, you can use this accessibility scanner outside of your standard CI pipeline. It applies specifically to explicit Tech Lead requests for local WCAG, axe, or accessibility checks outside the standard SDD pipeline.

How does frontend telemetry ingestion work after an axe-core scan?

Frontend telemetry ingestion sends the temporary axe-core report through an existing ingestion bridge into console.db for the audited FEAT. This unified telemetry process ensures findings are persisted for actionable verdicts.

When should I not use a local axe-core audit for frontend testing?

You should not use a local axe-core audit within the standard SDD pipeline, as this Skill handles only explicit Tech Lead requests for local checks outside of it. It also requires a known FEAT and a reachable frontend URL.