agentsclimarketplace

Screen reader testing

Skill Ghosteken/agent-harness/archive/skills-community/screen-reader-testing

Practical guide to testing web applications with screen readers for comprehensive accessibility validation.From its SKILL.md

Install
npx -y skills add Ghosteken/agent-harness --skill screen-reader-testing

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

1.4 KB, 220 tokens by cl100k_base, as published. Nobody here has run it

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.

What ships with it: 1 file

12.0 KB alongside SKILL.md

Keep looking

Skills are one crate of 325,949. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.