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.md

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

VoiceOver (macOS)

Setup

Enable: System Settings → Accessibility → VoiceOver
Toggle: Cmd + F5
Quick Toggle: Hold Command while quickly pressing Touch ID three times

Source: Apple VoiceOver setup.

Essential Commands

Navigation:
VO = Ctrl + Option (VoiceOver modifier)

VO + Right Arrow   Next element
VO + Left Arrow    Previous element
VO + Shift + Down  Enter group
VO + Shift + Up    Exit group

Reading:
VO + A             Read all from cursor
Ctrl               Stop speaking
VO + P             Read current paragraph

Interaction:
VO + Space         Activate element
VO + Shift + M     Open menu
Tab                Next focusable element
Shift + Tab        Previous focusable element

Rotor (VO + U):
Navigate by: Headings, Links, Forms, Landmarks
Left/Right Arrow   Change rotor category
Up/Down Arrow      Navigate within category
Enter              Go to item

Web Specific:
VO + Cmd + H       Next heading
VO + Cmd + J       Next form control
VO + Cmd + L       Next link
VO + Cmd + T       Next table

Testing Checklist

## VoiceOver Testing Checklist

### Page Load

- [ ] Page title announced
- [ ] Main landmark found
- [ ] Skip link works

### Navigation

- [ ] All headings discoverable via rotor
- [ ] Heading levels logical (H1 → H2 → H3)
- [ ] Landmarks properly labeled
- [ ] Skip links functional

### Links & Buttons

- [ ] Link purpose clear
- [ ] Button actions described
- [ ] New window/tab announced

### Forms

- [ ] All labels read with inputs
- [ ] Required fields announced
- [ ] Error messages read
- [ ] Instructions available
- [ ] Focus moves to errors

### Dynamic Content

- [ ] Alerts announced immediately
- [ ] Loading states communicated
- [ ] Content updates announced
- [ ] Modals trap focus correctly

### Tables

- [ ] Headers associated with cells
- [ ] Table navigation works
- [ ] Complex tables have captions

Common Issues & Fixes

<!-- Issue: Button not announcing purpose -->
<button><svg>...</svg></button>

<!-- Fix -->
<button aria-label="Close dialog"><svg aria-hidden="true">...</svg></button>

<!-- Issue: Dynamic content not announced -->
<div id="results">New results loaded</div>

<!-- Fix -->
<div id="results" role="status" aria-live="polite">New results loaded</div>

<!-- Issue: Form error not read -->
<input type="email" />
<span class="error">Invalid email</span>

<!-- Fix -->
<input type="email" aria-invalid="true" aria-describedby="email-error" />
<span id="email-error" role="alert">Invalid email</span>

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.