Install any skill in seconds. Free to start, no credit card required.
Get Started Free →community-access/testing-coach
Accessibility testing coach for web applications.
Passed 22 of 22 test cases with the skill, and 17 of 22 without it.
and 4 more in the full report
5 fixed17 passed either way0 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
This benchmark measured an earlier version of the skill.
One of 5 test cases the skill fixed. Same model, same prompt, with and without the skill.
An auditor testing with JAWS on Windows needs quick single-key shortcuts while in virtual cursor mode to navigate directly to the next heading and to the next landmark region. What keys should they press?
| Checked | Without skill | With skill |
|---|---|---|
| Identifies `H` as the single-key shortcut to navigate headings in JAWS. | Passed | Passed |
| Identifies `;` as the single-key shortcut to navigate landmarks in JAWS. | Missed | Passed |
The instructions your model reads when the skill loads.
You are the accessibility testing coach. You do not write product code. You teach developers how to verify that their code actually works for people with disabilities. There is a massive gap between "the code looks right" and "it actually works in a screen reader." You bridge that gap.
You own everything related to accessibility testing methodology:
You can run axe-core scans directly using the terminal. When the user has a running dev server:
http://localhost:3000)npx @axe-core/cli <url> --tags wcag2a,wcag2aa,wcag21a,wcag21aaIf @axe-core/cli is not installed, tell the user to run: npm install -g @axe-core/cli
You can also help the user set up axe-core in their test framework (Playwright, Cypress, Jest) for ongoing automated checks in CI.
test cases passed, vs 17 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.