Build and fix interfaces so they meet WCAG 2.2 AA in practice — native semantics, keyboard paths, focus order and visibility, accessible names, contrast, form errors, live regions, target size. Fires while writing or reviewing UI code, when a component is keyboard- or screen-reader-hostile, or when an audit finding has to be turned into a change. Not for proving the result (accessibility-verification), not for viewport layout work (responsive-design), and not a recital of the standard.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Accessibility in practice
Most barriers are created by replacing something the platform already made accessible. The cheapest
accessible component is the one you did not rebuild.
## When this fires
While building or changing any interactive UI, and when turning an audit finding into a fix. It does
not fire to *prove* a screen is accessible — that is `accessibility-verification`, and it needs a
keyboard and a screen reader, not a code read.
## Procedure
1. **Use the native element first.** `button`, `a[href]`, `input`, `label`, `select`, `details`,
`dialog`, `table`. Each arrives with a role, keyboard behaviour, focus handling and state
reporting you would otherwise have to write and maintain. A `div` with a click handler has none
of it. If the project already has an accessible component for this, reuse that instead.
2. **Get the structure right before the styling.** One `h1` per view, headings in descending order
with none skipped, real landmarks (`header`, `nav`, `main`, `footer`), lists marked up as lists,
a unique page title per route. Screen reader users navigate by these; they are the table of
contents, not decoration.
…
The line at the top of this page pins the label git:20260919.a0d4f55, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
GET https://markdownregistry.com/api/v1/artifacts/art_uxuswgd75daecpt3
GET https://markdownregistry.com/api/v1/resolve?ref=nahid-sparktales/agent-dispatcher/accessibility
GET https://markdownregistry.com/api/v1/blob/3b6e1b2d9584f9e19f3826c9ef968343fab4813c1a7efd65b6451077e265331f
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
nahid-sparktales/agent-dispatcher · skills/agent-dispatcher/SKILL.md · Handle requested Agent Dispatcher work with direct execution or prepared specialist guidance. Includes named roles…
nahid-sparktales/agent-dispatcher · skills/ai/agent-design/SKILL.md · Scope an agent or subagent before it is built — the one job it owns, the smallest tool set that closes that job, what…
nahid-sparktales/agent-dispatcher · skills/ai/agent-evals/SKILL.md · Build an eval suite that can actually detect a regression — cases pulled from real traffic, graders that check…
nahid-sparktales/agent-dispatcher · skills/ai/context-engineering/SKILL.md · Decide what actually occupies the model's window — progressive disclosure through an index, retrieval versus inlining…
nahid-sparktales/agent-dispatcher · skills/ai/llm-observability/SKILL.md · See what an agent actually did — one trace per run with nested model, tool and retrieval spans, token and latency…
nahid-sparktales/agent-dispatcher · skills/ai/mcp-design/SKILL.md · Build an MCP server, or bring an existing one into a project — choosing the transport, deciding which tools, resources…
nahid-sparktales/agent-dispatcher · skills/ai/memory-design/SKILL.md · Decide what an agent should remember, which layer holds it, who it is scoped to, and how a stale or contradicted memory…
nahid-sparktales/agent-dispatcher · skills/ai/model-routing/SKILL.md · Pick a model per job and degrade sensibly when one fails — a quality bar per call site, candidates compared on the same…
nahid-sparktales/agent-dispatcher · skills/ai/prompt-engineering/SKILL.md · Write or revise a prompt so it holds up — output contract, instruction placement, examples that earn their place, an…
nahid-sparktales/agent-dispatcher · skills/ai/prompt-injection-defense/SKILL.md · Treat everything an agent reads but did not author as data rather than instructions — an explicit trust boundary, a…
nahid-sparktales/agent-dispatcher · skills/ai/retrieval-rag/SKILL.md · Build and fix retrieval that actually returns the right passage — structure-aware chunking, one pinned embedding model…
nahid-sparktales/agent-dispatcher · skills/ai/structured-output/SKILL.md · Get parseable, trustworthy structured results out of a model — schema design, the enforcement mechanism the provider…
tech-leads-club/agent-skills · packages/skills-catalog/skills/(quality)/web-accessibility/SKILL.md · Audit and improve web accessibility following WCAG 2.1 guidelines. Use when asked to "improve accessibility", "a11y…
ericrisco/rsc-harness · skills/accessibility/SKILL.md · Use when making a web UI conform to WCAG 2.2 Level AA — axe-core or Lighthouse a11y violations, keyboard operability…
aicodedecode/awesome-muse-skills · skills-imported/accessibility/SKILL.md · Audit and improve web accessibility following WCAG 2.1 guidelines. Use when asked to "improve accessibility", "a11y…
