Comprehensive screen reader testing guide covering VoiceOver, NVDA, JAWS, and TalkBack with practical commands and accessibility patterns.
Automate repetitive workflows and reduce manual effort
Example: Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Learn new skills, understand complex topics, get expert guidance
Example: Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Enhance output quality through reviews, suggestions, and refinements
Example: Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
Time estimate: 15-45 minutes depending on use case complexity
Prerequisites
Submit your Claude Code skill and start earning
epx add wshobson/agents --skill screen-reader-testingCompatible with
Supported agents
Covers four major screen readers with platform-specific setup, essential keyboard commands, and testing checklists for macOS, Windows, iOS, and Android
Includes detailed testing scenarios for modals, live regions, tabs, and form validation with HTML/JavaScript examples
Provides browse vs. focus mode navigation strategies, landmark discovery, headi
No content available.
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionscreen-reader-testingExecute the skills CLI command in your project's root directory to begin installation:
epx add wshobson/agents --skill screen-reader-testingFetches screen-reader-testing from wshobson/agents and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
.cursor/skills/screen-reader-testing
Restart Cursor to activate screen-reader-testing. Access via /screen-reader-testingin your agent's command palette.
Learn more:View source on GitHubSkills CLI docsAbout CursorWhat are agent skills?
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid when
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
python-design-patterns
wshobson/agents · Frontend · same repo
microservices-patterns
wshobson/agents · Productivity · same repo
grafana-dashboards
wshobson/agents · Productivity · same repo
python-project-structure
wshobson/agents · Backend · same repo
angular-migration
wshobson/agents · Productivity · same repo
react-native-design
wshobson/agents · Frontend · same repo
screen-reader-testing has been reliable in day-to-day use. Documentation quality is above average for community skills.
screen-reader-testing fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
I recommend screen-reader-testing for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Registry listing for screen-reader-testing matched our evaluation — installs cleanly and behaves as described in the markdown.
Keeps context tight: screen-reader-testing is the kind of skill you can hand to a new teammate without a long onboarding doc.
screen-reader-testing fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
screen-reader-testing is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Solid pick for teams standardizing on skills: screen-reader-testing is focused, and the summary matches what you get after install.
Useful defaults in screen-reader-testing — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
I recommend screen-reader-testing for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
showing 1-10 of 55