aa71e76eb9
- Add date_added to all 950+ skills for complete tracking - Update version to 6.5.0 in package.json and README - Regenerate all indexes and catalog - Sync all generated files Features from merged PR #150: - Stars/Upvotes system for community-driven discovery - Auto-update mechanism via START_APP.bat - Interactive Prompt Builder - Date tracking badges - Smart auto-categorization All skills validated and indexed. Made-with: Cursor
37 lines
1.1 KiB
Markdown
37 lines
1.1 KiB
Markdown
---
|
|
name: screen-reader-testing
|
|
description: "Test web applications with screen readers including VoiceOver, NVDA, and JAWS. Use when validating screen reader compatibility, debugging accessibility issues, or ensuring assistive technology supp..."
|
|
risk: unknown
|
|
source: community
|
|
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.
|