Index of every page on this site: llms.txt
All skills
wshobson avatar

/screen-reader-testing

@4220308
by Seth Hobsonwshobson/agents43k stars
4,518
Run it yourself

Test web applications with screen readers including VoiceOver, NVDA, and JAWS. Use when validating screen reader compatibility, debugging accessibility issues, or ensuring assistive technology support.

Use this Skill: https://skilld.dev/gh/wshobson/agents/screen-reader-testing

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

referencesvoiceover-ios.md

≈324 tokens on demand. Your agent reads this file only when SKILL.md points to it.

VoiceOver with Safari on iOS

Enable VoiceOver in Settings → Accessibility → VoiceOver. Practice the changed touch controls before testing a page; tapping an element selects it rather than activating it.

Test action Gesture
Inspect an element Touch it, or move a finger across the screen
Advance or go back through elements Swipe right or left with one finger
Activate the selected element Double-tap with one finger
Change the rotor category Rotate two fingers on the screen
Move through the chosen rotor category Swipe down or up with one finger

In Safari, use the rotor's headings, links, and form-control categories to check structural navigation. Verify accessible labels, reading order, form errors, modal focus entry/return, and dynamic announcements using the common scenarios in the main skill. Test touch exploration as well as sequential swipes; desktop keyboard behavior alone does not establish iOS coverage.

Primary references: Apple setup and practice, touch gestures, and Safari navigation.

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts22d5 checks · Risk SAFE
  • Gen Agent Trust Hub22d

    This skill provides educational resources and technical guides for web accessibility testing using major screen readers. It includes command references, testing checklists, and standard UI implementation examples.

  • Socket22d

    No alerts

  • Snyk22d

    Risk: LOW · No issues

  • Runlayer8mo

    1 file scanned · No issues

  • ZeroLeaks7mo

    Score: 93/100 · 2 sections analyzed

Signed by skilld at 4220308. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 3 days ago.

Activeupdated last month
  • Testing
  • accessibility
  • screen-readers
  • voiceover
  • nvda
  • jaws
  • aria
  • assistive-technology

README badge

README badge for wshobson/agents/screen-reader-testing

Guides testing web applications with screen readers including VoiceOver, NVDA, JAWS, and TalkBack to validate accessibility. Covers setup, keyboard commands, testing checklists, common ARIA patterns, focus management for modals and tabs, and debugging techniques for ensuring assistive technology compatibility.

Generated from the current SKILL.md.

Which screen readers does this skill cover?
The skill covers VoiceOver (macOS/iOS), NVDA (Windows), JAWS (Windows), TalkBack (Android), and Narrator (Windows), with detailed command references and testing workflows for each.
Does this skill include testing scripts or checklists?
Yes. The skill includes VoiceOver and NVDA testing checklists, an NVDA test script covering page load, landmarks, forms, and dynamic content, plus common test scenarios for modals, live regions, and tabs.
Do I need to know ARIA to use this skill?
Not initially — the skill teaches semantic HTML first and explains ARIA as supplemental. It provides code examples showing common accessibility issues and ARIA fixes alongside screen reader testing.
Does this cover mobile screen reader testing?
Yes. The skill includes TalkBack (Android) setup and gestures, and mentions VoiceOver on iOS as part of the minimum testing coverage.
What does this skill not cover?
The skill focuses on manual testing workflows with actual screen readers rather than automated testing tools or CI/CD integration for accessibility.

Generated from the current SKILL.md. These answers refresh after source changes.