screen-reader-testing
/screen-reader-testing
Test with real screen readers, verifying announcements, live regions, and navigation, not just automated checks. Use when validating accessibility of UI that automated tools cannot fully assess.
- Author
- Amey-Thakur ↗
- Repository
- AI-SKILLS ↗
- Licence
- MIT
- Last repository change
- 05.09.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 05.09.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Test with real screen readers, verifying announcements, live regions, and navigation, not just automated checks. Use when validating accessibility of UI that automated tools cannot fully assess.
Original author description
Test with real screen readers, verifying announcements, live regions, and navigation, not just automated checks. Use when validating accessibility of UI that automated tools cannot fully assess.
How it works
- Method
- Boundaries
SKILL.md preview
---
name: screen-reader-testing
description: Test with real screen readers, verifying announcements, live regions, and navigation, not just automated checks. Use when validating accessibility of UI that automated tools cannot fully assess.
---
# Screen reader testing
Automated accessibility checkers catch maybe a third of issues;
the rest (does it announce sensibly, does the flow make sense, do
updates get spoken) require using an actual screen reader. Testing with
one is the only way to know what a blind user actually experiences,
and it routinely surprises sighted developers.
## Method
1. **Test with the real tools users use.** NVDA (free,
Windows, most common), VoiceOver (built into macOS/iOS),
JAWS (widespread in enterprise), TalkBack (Android):
test with at least NVDA or VoiceOver, ideally the ones
your users use. Screen readers differ in behavior, so
what works in one can fail in another; the common ones
cover most users.
2. **Learn the basic navigation, then use it.** How to move
by element, by heading, by landmark, by link, by form
control (each screen reader has these modes): because
users navigate by structure, jumping between headings
and landmarks, not reading top to bottom. Testing this
way reveals whether your heading hierarchy and landmarks
(see docs-information-architecture's structure,
aria-usage) actually help navigation.
3. **Verify announcements make sense.** Tab through and
listen: is each control announced with its name, role,
and state ("Save, button", "Email, edit, required")?
Do buttons say what they do, do form fields announce
their labels and errors (see accessible-forms), do
images have meaningful or empty alt as appropriate (see
alt-text-writing)? Announcements that are missing,
wrong, or redundant ("button button") are the bugs only
this testing finds.
4. **Test dynamic updates and live regions.** Content that
changes without a page load (form errors appearing,
a cart count updating, a loading-then-loaded state, a
toast notification) must be announced: `aria-live`
regions (polite for non-urgent, assertive for
important) make updates spoken. Test that changes are
announced and not over-announced (an aria-live region
that re-reads constantly is as bad as silence): this is
invisible to visual testing entirely.
5. **Follow the whole flow, not just components.** Complete
a real task with the screen reader (sign up, check out,
submit a form): the individual pieces can each be
accessible while the flow is confusing (focus lands
somewhere unexpected after an action, an error is not
announced, a modal does not manage focus: see
focus-management). The end-to-end experience is what
matters.
6. **Combine automated and manual testing.** Run automated
checkers (axe, WAVE, Lighthouse) first to catch the
mechanical issues (missing alt, low contrast, missing
labels) cheaply, then manual screen-reader testing for
what they cannot assess (does it make sense, does it
flow). Automated tools are a floor, not a ceiling; the
manual test is where real accessibility is verified.
## Boundaries
- Screen-reader testing by a sighted developer approximates
but does not replace testing with actual blind users and
accessibility experts, who catch issues and friction a
learner misses. Involve real users for anything critical.
- Screen readers are one assistive technology; others
(switch access, voice control, magnification, braille
displays) have their own testing needs. Keyboard
accessibility (see keyboard-navigation) is the shared
foundation.
- Cross-screen-reader differences are real; test the
primary ones and follow standards (semantic HTML, correct
ARIA: see aria-usage) rather than coding to one screen
reader's quirks, which breaks the others.
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · Amey-Thakur/AI-SKILLS | 90 | MIT |
| wshobson/agents | 100 | MIT |
| thedaviddias/front-end-checklist | 100 | MIT |
Database snapshot: 13.11.2026 · package version a3600f2e81c2 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 90accessibility-testing-strategy
Plan what to test, how to test, and who should test for accessibility. Use when defining a testing approach, planning QA, setting up automated and manual testing, or deciding what level of accessibility testing a project needs. Triggers on: accessibility testing, how to test,… - 95frontend-screen-reader-testing
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. - 100a11y-analyzer
Accessibility analysis from session data — keyboard-only navigation patterns, focus order issues, screen reader compatibility, and accessibility regressions. Use when auditing a11y compliance, investigating accessibility bugs, or validating inclusive design. - 100scanning-accessibility
Validate WCAG compliance and accessibility standards (ARIA, keyboard navigation). Use when auditing WCAG compliance or screen reader compatibility. Trigger with phrases like "scan accessibility", "check WCAG compliance", or "validate screen readers". - 100scanning-accessibility
Validate WCAG compliance and accessibility standards (ARIA, keyboard navigation). Use when auditing WCAG compliance or screen reader compatibility. Trigger with phrases like "scan accessibility", "check WCAG compliance", or "validate screen readers". - 90vue-a11y
Accessibility for Vue 3 apps. Semantic templates, ARIA patterns for modal, tabs, menu and combobox, focus management with Teleport and route changes, live announcements, accessible form errors, and automated checks with axe. Use when building UI components, reviewing…