Screen reader
A screen reader is assistive software that converts on-screen content into synthesized speech or refreshable braille, enabling blind and low-vision users to navigate websites, apps, and documents.
Detailed explanation
Screen readers translate the structure and content of a webpage into a linear, audible experience. They rely on the underlying HTML semantics — heading levels, list structure, link text, form labels, ARIA — not on visual styling.
The most-used screen readers are JAWS (commercial, Windows), NVDA (free, Windows), VoiceOver (built into macOS and iOS), and TalkBack (Android). Each has subtle differences in announcement behavior, but all rely on the same accessibility tree exposed by the browser.
Screen readers use the browser accessibility tree, which can change as HTML and JavaScript update the rendered page. Runtime changes therefore need testing across load timing, page states, script failure, and relevant assistive technology; they do not by themselves update the underlying theme or prove conformance.
How this applies to Shopify stores
On a Shopify storefront, a screen reader user may navigate through headings, product lists, forms, and cart controls. Automated accessibility-tree checks can identify some name, role, and structure issues, but a person must test the complete journey with relevant assistive technology.
What merchants should check next
Treat this term as a practical audit prompt, not just a definition. Check the storefront pages where the concept shows up in real customer journeys: product discovery, add-to-cart, cart drawer, checkout handoff, account login, and support contact flows. If the issue affects code, verify the rendered HTML and computed browser output after the theme change. If it affects copy or media, keep the merchant-facing wording accurate and easy to maintain.
Primary source: webaim.org