liveBook · Manning

Screen reader

A screen reader is assistive software that presents digital content and interface information through synthesized speech, refreshable braille, or other nonvisual output.

How 3 Manning books explain it

D3.js in Action, Third Edition

A screen reader is assistive software that converts accessible digital content into speech or refreshable Braille.

How it is used
Supports equivalent access to web pages and data visualizations through speech or Braille.
How deep it goes
Descends from assistive-technology definition to semantic HTML, SVG labeling, generated descriptions, keyboard interaction, and alternative tables.
Examples
Uses ChromeVox, a cetacean scatterplot, semantic page regions, SVG descriptions, filter buttons, and a chart-to-table alternative.
What you can do after
Build it from scratch by labeling visualizations, exposing data descriptions, and providing keyboard-accessible controls and tables.

Read how D3.js in Action, Third Edition explains screen reader →

Everyday Data Visualization

A screen reader is assistive software that converts displayed content into synthesized speech or braille output.

How it is used
Supports accessible data visualization by translating displayed content into speech or braille for people with limited or no vision.
How deep it goes
Defines the tool and gives practical alt-text and ARIA-label guidance without detailing screen-reader operation or implementation internals.
Examples
Uses bar-graph descriptions, per-bar ARIA labels, social-media images, Tableau workbooks, Power BI reports, and HTML image tags.
What you can do after
Apply it via concise alt text and meaningful ARIA labels for images, charts, and individual chart elements.

Read how Everyday Data Visualization explains screen reader →

WordPress Power Toolkit: Harness AI to build next-level websites

A screen reader is assistive software that converts digital interface content into synthesized speech or braille for people who cannot rely on visual display.

How it is used
Supports accessible website planning, theme selection, interface inspection, multimedia labeling, and automated accessibility checks.
How deep it goes
Explains spoken labeling, ARIA roles, inspection tools, Lighthouse testing, video titles, and autoplay risks without detailing screen-reader software operation.
Examples
Uses accessible WordPress themes, inspected ARIA roles, Lighthouse reports, descriptive iframe titles, and non-autoplaying YouTube videos.
What you can do after
Evaluate websites with browser tools and improve screen-reader clarity through roles, labels, video titles, and audio controls.

Read how WordPress Power Toolkit: Harness AI to build next-level websites explains screen reader →

Related concepts

These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.