accessibility-verification skillA
accessibility-verification is agent-read markdown (skill) from nahid-sparktales/agent-dispatcher: Prove an accessibility claim instead of asserting it — automated scan plus the keyboard, focus, zoom and screen-reader passes a scanner structurally cannot make. Fires before anyone says a screen is accessible or WCAG AA, when signing off UI work, or when an audit result needs checking. Not for making the fixes (accessibility), and it never upgrades a clean scan into a conformance claim..
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# Accessibility verification A clean automated scan proves that a set of machine-checkable rules found nothing. It says nothing about whether a name is meaningful, an order is logical, an announcement is useful, or a flow can be completed without a mouse. Those need a person driving the interface. ## When this fires Before any claim that a screen, component or flow is accessible, keyboard-operable, screen-reader usable or WCAG-conformant — your own work or someone else's, and when re-checking after fixes. It does not fire to write the fixes; that is `accessibility`. ## Procedure 1. **Fix the scope in writing first.** Which routes, which states (empty, loading, error, logged in), which viewport, which browser. A claim without a named scope is not a claim — everything outside it stays explicitly unverified. 2. **Render the real thing.** The running app at the route that changed, not the source, not Storybook alone if the route composes differently. A stale build verifies nothing. 3. **Run an automated scan and record it exactly.** Use whatever the project already has — an …
Read the whole file at its exact version.
How to install
mdr add nahid-sparktales/agent-dispatcher/accessibility-verification@git:20260919.a0d4f55mdr add nahid-sparktales/agent-dispatcher/accessibility-verification@sha256:de6b68edfac3e177Pin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_gjzq37una36nhymj)
1 badge views in 30 days
Versions
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (6780 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
nahid-sparktales/agent-dispatcher · 49 stars · license MIT · pushed 2026-09-23 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_gjzq37una36nhymj GET https://markdownregistry.com/api/v1/resolve?ref=nahid-sparktales/agent-dispatcher/accessibility-verification GET https://markdownregistry.com/api/v1/blob/de6b68edfac3e1779737fc3553b5b1ba28084d2af2ca55bc0284cd6d33eadba0
Your agent 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.