How screen reader works in the Accessibility Widget

Screen Reader

The Screen Reader feature in the Accessibility Widget provides spoken feedback as visitors explore your store. When enabled, the browser reads aloud information about the content or control the visitor selects, using the language configured in the accessibility menu. This feature is designed as a read-aloud assistant for visitors who benefit from hearing page content. It is not a replacement for dedicated assistive technologies such as NVDA, JAWS, or VoiceOver.

Overview

Enabling Screen Reader

Visitors can turn on the Screen Reader in either of the following ways:

1. Accessibility menu — Open the accessibility menu and enable the Screen Reader option.
2. Blind profile — Selecting the Blind accessibility profile automatically enables the Screen Reader and related settings.

When Screen Reader is enabled, the visitor hears a brief confirmation (for example, “Screen reader enabled”). When it is disabled, a corresponding confirmation is announced.

The setting is stored in the visitor’s browser so it remains active on subsequent visits, unless they clear site data or turn the feature off.

How visitors use it

After Screen Reader is enabled, visitors click any element on the page—the storefront, forms, navigation, or controls within the accessibility menu itself. The tool identifies the relevant item and reads a spoken description aloud.

While content is being read, the corresponding element is visually highlighted (typically with a yellow background) so the visitor can see which item is being described.

For certain interactive elements, such as buttons, links, and text fields a short audible cue may play immediately before the spoken description, indicating that an actionable control was selected.

What is read aloud

Screen Reader is intended to provide contextual descriptions, not only raw text. Depending on the element, visitors may hear:

• Buttons and links — Visible label and element type (for example, “Add to cart, button” or “Shipping policy, link”)
• Headings — Heading text and that the element is a heading
• Checkboxes and switches — Label and state (for example, checked or unchecked)
• Dropdown menus — Field label and selected value
• Sliders and range controls — Label and current value
• Text fields — Characters or words as the visitor types; an indication when a field is empty

Elements that are decorative, hidden from assistive technologies, or lack a meaningful label are generally not announced, to avoid unnecessary or confusing output.

Controls within the accessibility menu use dedicated spoken labels so icons and compact layouts are described clearly (for example, “Contrast, dark” rather than only a visual icon).

Language support

Spoken output follows the language selected in the accessibility menu. If the visitor changes the menu language, subsequent read-aloud content, including enable and disable confirmations, uses that language, subject to browser voice availability. Role and state phrases (such as “button,” “checked,” or “expanded”) can be customized through your widget text configuration (clickToReadSpeech).

Additional behavior

Typing in form fields

When a visitor types in a supported text field, Screen Reader can announce inserted characters or words. If the field is cleared, the visitor may hear an “empty” indication.

Returning to the page

If the visitor switches to another browser tab or application and returns, Screen Reader can re-announce the element that currently has focus.

Turning the feature off

Disabling Screen Reader in the menu stops read-aloud behavior, removes highlighting, and plays a disable confirmation. The preference is updated in storage accordingly.

Intended use and limitations

Screen Reader is well suited for visitors who:

• Prefer or require auditory feedback while browsing
• Benefit from spoken labels for buttons, links, and form controls
• Use the accessibility menu’s read-aloud option without installing separate assistive software

Screen Reader is not intended to:

• Replace a full desktop or mobile screen reader for comprehensive navigation
• Read entire long-form articles without interaction (descriptions are triggered primarily by click and focus)
• Guarantee identical behavior across every browser and voice engine (output depends on the visitor’s browser and available system voices)

We recommend testing Screen Reader on your storefront with your most common customer journeys, product pages, cart, checkout, and account flows to confirm that key controls have clear visible labels and that spoken descriptions meet your expectations.

Summary

Screen Reader gives visitors spoken feedback about the content and controls they select on your site. It highlights the active element while speaking, respects the accessibility menu language, and remembers each visitor’s preference. Enable it from the Screen Reader option or the Blind profile in the Pandectes Accessibility Menu.

Updated on: 20/05/2026