screen-reader-testing
Test screen reader support fast
Screen reader issues are hard to reproduce and validate. This skill gives clear test steps and fixes for VoiceOver, NVDA, JAWS, and TalkBack.
Download the skill ZIP
Upload in Claude
Go to Settings â Capabilities â Skills â Upload skill
Toggle on and start using
Test it
Using "screen-reader-testing". Provide a checklist to test a modal dialog with NVDA.
Expected outcome:
- Confirm the dialog title and description are announced on open
- Verify focus moves into the dialog and is trapped inside
- Check that Escape closes the dialog and focus returns
- Ensure all buttons announce role and state
Using "screen-reader-testing". What VoiceOver commands help test heading structure?
Expected outcome:
- VO + Cmd + H to jump to next heading
- Use Rotor (VO + U) to navigate by headings category
- Check logical heading level progression
- Verify all section headings are discoverable
Security Audit
SafePure documentation skill containing only instructional content for screen reader testing. Contains no executable code, no file system access, no network calls, and no external command execution. All static findings are false positives caused by the scanner misinterpreting documentation patterns.
Risk Factors
đ Network access (5)
âī¸ External commands (35)
Quality Score
What You Can Build
Manual regression pass
Run repeatable screen reader checks before a release.
Fix ARIA issues
Debug missing announcements and focus behavior in components.
Team test guide
Standardize screen reader testing coverage across teams.
Try These Prompts
Create a VoiceOver test checklist for my landing page with headings, landmarks, and forms.
Give me an NVDA script to test a checkout form, including error handling and focus movement.
List steps to verify live region announcements for search results updates.
Review my tab and modal behavior and list the critical screen reader checks to run.
Best Practices
- Test with real screen readers on supported platforms
- Use semantic HTML before adding ARIA
- Verify keyboard only flow before screen reader tests
Avoid
- Relying on a single screen reader for approval
- Testing only happy paths without errors
- Ignoring mobile screen reader behavior