Screen Reader
// Definition
Assistive technology software that converts on-screen content into synthesised speech or Braille output, enabling users who are blind or have low vision to navigate and interact with digital interfaces. Common screen readers include NVDA and JAWS (Windows), VoiceOver (macOS and iOS), and TalkBack (Android). QA testers use screen readers to verify that interactive elements have meaningful names, heading and landmark structure is navigable, dynamic content changes are announced, and no information is conveyed visually only.
// Why it matters
A screen reader narrates the page to blind/low-vision users via the accessibility tree. QA cares because it's the ground truth no automated tool replaces: axe can flag a missing label, but only a screen-reader pass tells you whether the page is usable — whether focus order makes sense, announcements fire, and dynamic updates are heard.
// How to test
This is a manual, tool-assisted procedure (NVDA/JAWS on Windows, VoiceOver on Mac): • Tab through the whole flow eyes-closed — does the narration make sense? • Confirm every control announces a name, role, and state • Trigger dynamic changes (toasts, validation) — are they announced via live regions? • Check focus order matches visual order; no keyboard traps Automated tests assert prerequisites (labels, roles); they cannot judge the experience.
// Common mistakes
- Assuming an axe pass means screen-reader-usable (it doesn't)
- Dynamic content (errors, toasts) that updates silently with no live region
- Testing one screen reader and assuming the rest behave identically
// Related terms
ARIA (Accessible Rich Internet Applications)
A W3C specification that adds roles, states, and properties to HTML elements to expose semantics to assistive technologies when native HTML alone is insufficient. The first rule of ARIA is: do not use ARIA — prefer native HTML elements (button, input, nav) that carry the correct semantics implicitly. Incorrect ARIA can make an interface less accessible than no ARIA at all. QA testers check that ARIA roles match the component's actual behaviour, required states (aria-expanded, aria-selected, aria-checked) update dynamically, and aria-label or aria-labelledby provides meaningful names for elements that lack visible text.
Semantic HTML
The practice of using HTML elements according to their intended meaning — heading elements (h1–h6) for headings, button for interactive controls, nav for navigation regions, main for the primary content area — rather than using generic div and span elements for everything. Semantic elements convey role, structure, and sometimes state to browsers, search engines, and assistive technologies without requiring additional ARIA attributes. QA testers check that pages use a logical heading hierarchy, landmark regions are present, and interactive controls use native elements rather than div or span with click handlers.
Assistive Technology
The umbrella term for hardware and software that helps people with disabilities use computers and digital devices — including screen readers (NVDA, VoiceOver, JAWS, TalkBack), screen magnifiers, switch-access devices, voice-control software (Dragon NaturallySpeaking), refreshable Braille displays, and eye-tracking systems. In QA, assistive technology testing means verifying that the product works with the specific AT combinations most relevant to the target user base, since behaviour can vary significantly across AT and browser pairings. Automated accessibility tools do not replicate AT behaviour; manual testing with real AT remains essential.
Alt Text (Alternative Text)
A text description provided via the HTML alt attribute on img elements that conveys the meaning or function of an image to users who cannot see it — including screen-reader users and users with images disabled. Meaningful images require descriptive alt text that communicates the content or purpose of the image, not its appearance. Decorative images (pure visual embellishment) should use an empty alt attribute (alt="") so screen readers skip them entirely. QA testers check that every meaningful image has accurate, concise alt text, decorative images are marked correctly, and complex images (charts, infographics) have extended descriptions.