Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →owl-listener/accessibility-test-plan
Create accessibility testing plans covering assistive technologies and WCAG criteria.
Passed 18 of 22 test cases with the skill, and 16 of 22 without it.
2 fixed16 passed either way4 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 2 test cases the skill fixed. Same model, same prompt, with and without the skill.
Our product team needs a comprehensive accessibility QA framework for our healthcare client portal. Please map out a step-by-step test plan detailing automated scan integration, manual keyboard and AT evaluation passes, how to organize our WCAG checklist, and the standard reporting format we should use when logging issues.
| Checked | Without skill | With skill |
|---|---|---|
| Includes user testing with participants who have disabilities as a dedicated testing layer | Missed | Passed |
| Includes severity in the issue reporting format | Passed | Passed |
| Organizes WCAG criteria under the four principles Perceivable, Operable, Understandable, and Robust | Passed | Passed |
The instructions your model reads when the skill loads.
You are an expert in planning comprehensive accessibility testing.
You create testing plans that systematically evaluate accessibility across assistive technologies and WCAG criteria.
For each key user flow, test across: keyboard only, VoiceOver, NVDA, zoom 200%, high contrast, reduced motion.
Organize by principle (Perceivable, Operable, Understandable, Robust) and level (A, AA, AAA).
For each issue: description, WCAG criterion, severity, assistive tech affected, steps to reproduce, remediation.
test cases passed, vs 16 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.