audit-accessibility
SkillDev toolsAudit UI against repository Quality/a11y gates; do not invent a WCAG level. Use when the user types /audit-accessibility.
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use the audit-accessibility skill
What this skill tells your AI
The instructions your AI receives, as published by blockmatic/basilic in .agents/skills/workflow/audit-accessibility/SKILL.md and read by ahel’s review.
Purpose and inputs
Audit the specified UI against _first/.../QUALITY.md, accessibility docs, and existing a11y tests. The Quality station owns the bar. Stay report-only unless the user asked to fix.
Steps
- Load
/f-qualityand the Quality overlay. Use the named a11y gate. If none exists, report that and run only existing repo tests. - Inspect semantic structure, keyboard access, names, and focus on changed UI.
- Run the repository's a11y or component tests. Do not declare WCAG A/AA/AAA unless the overlay names that level.
- If fixes are authorized, apply the smallest semantic/ARIA change that meets the overlay.
Verification
- Findings cite overlay, test, or rendered behavior.
- No WCAG level was invented.
- No unsolicited commit.
Handoff
List issues, the gate used, and remaining manual checks.
Signals
- GitHub stars
- 89
- Forks
- 11
- Last commit
- Sep 2026
Advanced
- Catalog kind
- skill
- Gateway key
audit-accessibility- Source
- github.com/blockmatic/basilic