mcpField
S
screen-reader-testing

screen-reader-testing

github.com/sickn33Testing & quality48.8k166 installsUpdated today
Repository

About screen-reader-testing

A practical skill for testing web applications with screen readers, intended for accessibility validation. It covers ARIA, forms, dynamic announcements, navigation, and assistive technology issues.

Key features

  1. 01Screen reader compatibility checks
  2. 02ARIA implementation testing
  3. 03Form accessibility checks
  4. 04Dynamic content announcement testing
  5. 05Navigation accessibility validation

Use cases

  1. 01Checking screen reader support in a web app
  2. 02Troubleshooting assistive technology issues
  3. 03Validating accessible forms and dynamic content

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/sickn33/agentic-awesome-skills --skill screen-reader-testing

After installing, type/screen-reader-testingin Claude Code to confirm it loaded.

Bundled filesresources/implementation-playbook.md

Details

From the project README

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.

Comments

Markdown supported