Web a11y orchestrator

Skill klovaaxel/web-a11y-agent-skills/skills/web-a11y-orchestrator

Framework-agnostic web accessibility skills and Cursor subagents for AI coding agents.

Install

npx -y skills add klovaaxel/web-a11y-agent-skills --skill web-a11y-orchestrator

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

5 stars5 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Central routing and orchestration skill for web accessibility work. Use as the default entrypoint for accessibility-related UI tasks to select the right authoring, review, remediation, and testing workflows.

SKILL.md

2.3 KB, as published. Nobody here has run it

Web A11y Orchestrator

Goal

Coordinate accessible UI work from scope discovery through implementation, review, remediation, and validation.

Routing Map

New pages, app shells, semantic structure -> web-a11y-authoring, web-a11y-navigation, web-a11y-css
Components, controls, overlays, custom interactions -> web-a11y-authoring, web-a11y-css
Links, downloads, external destinations, images, SVG, media -> web-a11y-authoring, web-a11y-testing
Forms, validation, search, multi-step flows -> web-a11y-forms
Navigation, landmarks, breadcrumbs, skip links, menus -> web-a11y-navigation
Filtering, sorting, pagination, live updates, tables -> web-a11y-dynamic-ui
Styling, focus, contrast, motion, zoom, forced colors -> web-a11y-css
Web components or Shadow DOM -> web-a11y-web-components
Audits, triage, CI, DevTools, custom checks -> web-a11y-debugging, web-a11y-review, web-a11y-testing

Workflow

A11y workflow

- [ ] Define scope and changed user journeys
- [ ] Select relevant skill passes from routing map
- [ ] Implement semantic-first UI
- [ ] Review for accessibility defects and missing tests
- [ ] Remediate Critical/High issues
- [ ] Validate with automation, keyboard, and screen reader smoke checks

Severity Policy

Critical: blocks core task completion for keyboard or assistive technology users.
High: creates major confusion, lost state, or unreliable operation.
Medium: degrades usability but has a workable path.
Low: polish, consistency, or non-blocking robustness improvement.

Public References

Use public references for deeper decisions:

W3C WCAG
WAI Tutorials
WAI-ARIA Authoring Practices Guide
MDN Web Docs
WebAIM
axe documentation and browser DevTools accessibility docs

Output

End with:

Accessibility report

Scope:
- <pages/components/journeys>

Passes run:
- <skills/checks>

Blocking issues:
- <severity> <issue> <status>

Verification:
- Automated: pass/fail/not run
- Keyboard: pass/fail/not run
- Screen reader smoke: pass/fail/not run

Decision:
- Ready | Needs remediation | Needs follow-up