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.

referencesnvda.md

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

NVDA (Windows)

Setup

Download: nvaccess.org
Start: Ctrl + Alt + N (when the Windows shortcut is enabled)
Quit: Insert + Q

Essential Commands

Navigation:
Insert = NVDA modifier

Down Arrow         Next line
Up Arrow           Previous line
Tab                Next focusable
Shift + Tab        Previous focusable

Reading:
NVDA + Down Arrow  Say all
Ctrl               Stop speech
NVDA + Up Arrow    Current line

Headings:
H                  Next heading
Shift + H          Previous heading
1-6                Heading level 1-6

Forms:
F                  Next form field
B                  Next button
E                  Next edit field
X                  Next checkbox
C                  Next combo box

Links:
K                  Next link
U                  Next unvisited link
V                  Next visited link

Landmarks:
D                  Next landmark
Shift + D          Previous landmark

Tables:
T                  Next table
Ctrl + Alt + Arrows Navigate cells

Elements List (NVDA + F7):
Shows all links, headings, form fields, landmarks

Browse vs Focus Mode

NVDA automatically switches modes:
- Browse Mode: Arrow keys navigate content
- Focus Mode: Arrow keys control interactive elements

Manual switch: NVDA + Space

Watch for:
- "Browse mode" announcement when navigating
- "Focus mode" when entering form fields
- Application role forces forms mode

Testing Script

## NVDA Test Script

### Initial Load

1. Navigate to page
2. Let page finish loading
3. Press Insert + Down to read all
4. Note: Page title, main content identified?

### Landmark Navigation

1. Press D repeatedly
2. Check: All main areas reachable?
3. Check: Landmarks properly labeled?

### Heading Navigation

1. Press Insert + F7 → Headings
2. Check: Logical heading structure?
3. Press H to navigate headings
4. Check: All sections discoverable?

### Form Testing

1. Press F to find first form field
2. Check: Label read?
3. Fill in invalid data
4. Submit form
5. Check: Errors announced?
6. Check: Focus moved to error?

### Interactive Elements

1. Tab through all interactive elements
2. Check: Each announces role and state
3. Activate buttons with Enter/Space
4. Check: Result announced?

### Dynamic Content

1. Trigger content update
2. Check: Change announced?
3. Open modal
4. Check: Focus trapped?
5. Close modal
6. Check: Focus returns?

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.