screen-reader-testing · git:20261111.00f9c40 · 2026-11-11 · sha256 c1ef36cc924c953e

screen-reader-testing git:20261111.00f9c40A

Immutable. This exact content never changes and is served at /api/v1/blob/c1ef36cc924c953e.

No tool to install first
claude plugin marketplace add https://markdownregistry.com/mp/a/art_hgwkp77croabyv2p/c1ef36cc924c953e8e617da4bb97a79295dd27a3381fcd023d5655ff7cc8e09d.json

Then /plugin install screen-reader-testing@markdownregistry-hgwkp77croabyv2p in Claude Code. It installs this exact version, the one graded A here, pinned to the commit it was graded at, and leaves it there.

---
name: screen-reader-testing
description: 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.