a11y-validate

Detect accessibility violations in web and mobile project files.

161|21|Updated Mar 26, 2026
One-click install
npx skills add https://github.com/softspark/ai-toolkit --skill a11y-validate
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: a11y-validate
Source: https://github.com/softspark/ai-toolkit/tree/main/app/skills/a11y-validate
Command: npx skills add https://github.com/softspark/ai-toolkit --skill a11y-validate

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Many codebases lack comprehensive accessibility checks, risking non‑compliance with WCAG, EN 301 549, and the European Accessibility Act.

Core Features & Use Cases

  • Detect missing alt text, ARIA misuse, color‑contrast issues, and absent accessibility statements across web and mobile frameworks.
  • Supports automated scans for React, Next, Nuxt, Astro, Vue, Svelte, Remix, Angular, Flutter, and React Native projects.
  • Ideal for developers and QA teams needing a quick, read‑only report before release or legal audit.

Quick Start

Run /a11y-validate on your project root to generate an accessibility report.

Frequently Asked Questions about a11y-validate

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

FAQPage Schema
How do I check my codebase for WCAG and EN 301-549 accessibility violations?

To check for WCAG and EN 301-549 accessibility violations, scan your project files to detect missing alt text, improper ARIA usage, insufficient color contrast, and absent accessibility statements. This generates a comprehensive read-only compliance report.

Can I scan React, Vue, and Svelte projects for European Accessibility Act compliance?

Yes, you can validate European Accessibility Act compliance across React, Next, Nuxt, Astro, Vue, Svelte, Remix, Angular, Flutter, and React Native projects by scanning HTML, JSX, TSX, and mobile project files for accessibility defects.

How do I detect missing alt text and ARIA misuse in my frontend code?

Detect missing alt text and ARIA misuse by running automated read-only scans using standard Bash, Grep, and Glob utilities across your HTML and Javascript framework files. This identifies exact locations of accessibility violations without external dependencies.

Do I need to install external dependencies to run an accessibility scanner?

No external dependencies are required to run this accessibility scanner. It operates entirely read-only using standard Bash, Grep, Glob, and file reading utilities already available in your environment to identify compliance issues.

What is the best way to prepare for a legal accessibility audit before release?

The best way to prepare for a legal accessibility audit before release is to run an automated read-only scan against WCAG 2.1, EN 301-549, and European Accessibility Act standards. This quickly identifies compliance gaps across web and mobile frameworks.

Why does my accessibility validation report missing accessibility statements?

Accessibility validation reports missing accessibility statements because scanning against EN 301-549 and EAA requirements includes checking for mandatory documentation. It identifies absent compliance statements alongside code-level issues like poor color contrast.