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.mdfor 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.
Source: sickn33/agentic-awesome-skills → skills/screen-reader-testing/SKILL.md
Also appears in: sickn33/agentic-awesome-skills/plugins/agentic-awesome-skills/skills/screen-reader-testing/SKILL.md, sickn33/agentic-awesome-skills/plugins/agentic-awesome-skills-claude/skills/screen-reader-testing/SKILL.md, sickn33/agentic-awesome-skills/plugins/agentic-bundle-aas-qa-test-automation/skills/screen-reader-testing/SKILL.md, sickn33/agentic-awesome-skills/plugins/agentic-bundle-aas-accessibility-inclusive-ux/skills/screen-reader-testing/SKILL.md