a11y-audit

Audit frontend source files for WCAG violations and report findings by severity.

12|1|Updated Feb 13, 2026

Search Tags:#ui #accessibility #a11y #frontend #audit #wcag

Ready to run

npx skills add https://github.com/helderberto/skills --skill a11y-audit-helderberto

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: a11y-audit
Source: https://github.com/helderberto/skills/tree/main/a11y-audit
Command: npx skills add https://github.com/helderberto/skills --skill a11y-audit-helderberto

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Frontend accessibility issues slow down user experience and impede compliance with WCAG, making it hard to ensure inclusive UI across React, Vue, and Svelte projects.

Core Features & Use Cases

Detect accessibility issues in frontend codebases and provide actionable remediation steps.
Generate organized reports of findings grouped by severity to guide fixes.
Use during development and audits to verify WCAG conformance on interactive UI components.

Quick Start

Run an accessibility audit on your frontend project and review the prioritized list of issues to fix.

Frequently Asked Questions about a11y-audit

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

FAQPage Schema

How do I audit frontend accessibility for WCAG conformance in my UI code?▼

A frontend accessibility audit analyzes your HTML, JSX, and template source files to detect WCAG violations. It surfaces UI accessibility problems and provides actionable remediation steps to ensure inclusive user experiences.

Can I use axe-core tooling to check React, Vue, and Svelte projects for a11y issues?▼

Yes, you can check React, Vue, and Svelte projects for a11y issues using optional axe-core tooling integration. The audit analyzes your frontend codebase to verify WCAG conformance across these frameworks.

What is the best way to generate accessibility reports grouped by severity?▼

The best way to generate accessibility reports grouped by severity is to run an audit on your frontend source files. This produces an organized, prioritized list of findings to guide your WCAG fixes.

Does this accessibility audit require any external dependencies to run?▼

No external dependencies are required to run the core accessibility audit. It analyzes your frontend source files directly, though it supports integration with optional axe-core tooling for enhanced detection.

When do I need to audit UI code for accessibility problems during development?▼

You need to audit UI code for accessibility problems during development to verify WCAG conformance on interactive components. This ensures inclusive UI and prevents frontend accessibility issues from slowing down user experience.