w-a11y
Audit UI against repository a11y docs and tests; do not invent a WCAG level.
Install
npx skills add https://github.com/blockmatic/basilic-skills --skill w-a11ySKILL.md
Audit the specified UI against accessibility docs and existing a11y tests. Stay report-only unless the user asked to fix.
- Read testing and frontend docs for 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 repository docs name that level.
- If fixes are authorized, apply the smallest semantic/ARIA change that meets the documented gate.
- Docs:
/w-docsif behavior or commands changed.
Related skills
improve-codebase-architecturemattpocock1MScan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.codebase-designmattpocock691KShared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.web-design-guidelinesvercel-labs676KReview UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".code-reviewmattpocock631KReview the changes since a fixed point (commit, branch, tag, or merge-base) along two axes: Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating issue/spec asked for?). Runs both reviews in parallel sub-agents and reports them side by side. Use when the user wants to review a branch, a PR, work-in-progress changes, or asks to \"review since X\".