Individual skill
audit-a11y
Run axe-core against every pracht route in a headless browser and report alt text, contrast, landmark, focus, and form-label issues by severity. Use for "audit a11y", "check accessibility", "WCAG compliance", "axe my app".
skills/audit-a11y/SKILL.md
Source commit e7c088a615e0bc16659d7a307fe92910ae6bd546
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Not checked yet
- Last checked
- Nov 8, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 106
- Repository last updated
- Nov 9, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- agent-skills Repository topic
- ai-agents Repository topic
- cloudflare-workers Repository topic
- framework Repository topic
- full-stack Repository topic
- llms-txt Repository topic
- mcp Repository topic
- preact Repository topic
- ssg Repository topic
- ssr Repository topic
- legal Derived category
- security Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
Read excerpt
# Pracht Audit A11y
Static linting cannot prove a route is accessible — many issues only appear
in the rendered DOM. This skill renders each route in a real browser and
runs axe-core against the result.
## Step 1: Boot the app
Prefer the production build/runtime — production HTML is what users actually
receive. `pracht preview` builds and serves it for **Node and Cloudflare**
targets. It refuses Vercel targets (it prints guidance and exits nonzero):
for a Vercel app, run `vercel dev` yourself or point `BASE_URL` at a deployed
preview instead. Fall back to `pracht dev` only if the user can't build.
