Start a fresh conversation. Replace the highlighted placeholders.
Use screen-reader-testing to create an accessibility test plan for [web application] covering [critical user flows] and [target screen readers].
Required inputs
[web application]
[critical user flows]
[target screen readers]
User-approved starter prompt based on a pinned source version; check current skill requirements before running. Task evidence ↗
SKILL.md
name: screen-reader-testingdescription: Practical guide to testing web applications with screen readers for comprehensive accessibility validation.metadata: aas-risk: safe aas-source: community aas-date-added: '2026-02-27'
Screen Reader Testing
Practical guide to testing web applications with screen readers for comprehensive accessibility validation.
Use this skill when
Validating screen reader compatibility
Testing ARIA implementations
Debugging assistive technology issues
Verifying form accessibility
Testing dynamic content announcements
Ensuring navigation accessibility
Do not use this skill when
The task is unrelated to screen reader testing
You need a different domain or tool outside this scope
Instructions
Clarify goals, constraints, and required inputs.
Apply relevant best practices and validate outcomes.
Provide actionable steps and verification.
If detailed examples are required, open resources/implementation-playbook.md.
Resources
resources/implementation-playbook.md for detailed patterns and examples.
Limitations
Use this skill only when the task clearly matches the scope described above.
Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.