accessibility-audit
Accessibility Audit
Workflow
- Detect framework from
package.json(React, Vue, Svelte) - Run static analysis — grep JSX/TSX/HTML files for violations (see wcag-checklist.md):
- Missing
alton<img> - Missing
aria-labelon icon-only buttons and inputs without<label> - Non-semantic interactive elements (
<div onClick>,<span onClick>) - Missing
htmlFor/foron<label> - Heading hierarchy skips (h1 → h3)
- Missing landmark roles (
<main>,<nav>,<header>)
- Missing
- If dev server is running, optionally run axe-core CLI:
npx @axe-core/cli@4 http://localhost:3000 - Report findings grouped by severity
Output format
Group by WCAG criterion:
- Critical (WCAG A) — blocks assistive technology users
- Serious (WCAG AA) — significantly impacts usability
- Suggestions — best practice improvements
Use file:line references. Include the fix for each finding.
Rules
- Report
file:line+ violation + WCAG criterion + suggested fix - Never auto-fix — always show what to change and why
- Prioritize keyboard navigation and screen reader issues
Error Handling
- If
@axe-core/clifails (no running dev server) → fall back to static analysis only; note axe scan was skipped - If no JSX/HTML files found → report project structure is incompatible and stop
- If framework is undetected → scan all
.html,.jsx,.tsx,.vuefiles
More from helderberto/skills
explain-code
Explains code with visual diagrams and analogies. Use when explaining how code works, teaching about a codebase, or when the user asks "how does this work?" Don't use for modifying code, fixing bugs, or generating new implementations.
45ship
Commit and push changes using atomic commits. Use when user asks to "ship", "commit and push", or requests committing and pushing changes. Don't use for creating pull requests or reviewing changes before committing.
45refactor-plan
Create structured refactoring plans. Use when user wants to plan a refactor, needs a refactoring strategy, or mentions breaking down large changes into small commits. Don't use for implementing code changes directly, small one-line fixes, or renaming a single variable.
44safe-repo
Check for sensitive data in repository. Use when user asks to "check for sensitive data", "/safe-repo", or wants to verify no company/credential data is in the repository. Don't use for general code review, adding .gitignore entries, or scanning non-git directories.
41lint
Run linting and formatting checks. Use when user asks to "run linter", "/lint", "check linting", "fix lint errors", or requests code linting/formatting. Don't use for running tests, type-checking only, or projects without a lint script in package.json.
40tdd
Guides test-driven development with red-green-refactor loop. Use when user wants to build features or fix bugs using TDD, mentions "red-green-refactor", wants test-first development, or requests TDD workflow. Don't use for writing tests after implementation, adding tests to existing untested code, or one-off test fixes.
40