How does a screen reader work?

A screen reader reads the content and structure of an interface aloud or sends it to a braille display, letting users without sight navigate by headings, links, and controls. It relies on the underlying content being properly labelled and structured, which is why accessible coding matters so much.

Why do mainstream apps need to support assistive technology?

Assistive technologies can only convey what an interface exposes. If buttons are unlabeled or content is not in a readable structure, a screen reader cannot describe it. Building apps with proper labels, semantics, and keyboard support lets assistive technologies do their job.

Assistive Technologies

Assistive technologies are tools and software, such as screen readers, magnifiers, and alternative input devices, that enable people with disabilities to perceive and operate computing systems.

Definition

Assistive technologies are devices and software that provide an alternative means of perceiving, controlling, or communicating with a computer for people whose abilities differ from those a standard interface assumes, such as screen readers that speak on-screen content or switches that substitute for a keyboard.

Scope

This topic covers the technologies that mediate interaction for users with disabilities: screen readers and braille displays for blind users, screen magnification and high contrast for low vision, alternative and switch input for motor disabilities, captioning for deaf and hard-of-hearing users, and research systems that extend access, including to touchscreens. It does not cover the standards that content must meet to work with these tools, treated under web accessibility, nor the broad design philosophies, treated under universal and inclusive design.

Core questions

How do screen readers convey graphical interfaces to blind users?
What input alternatives exist for users with motor disabilities?
How were touchscreens, initially inaccessible, made usable without sight?
How do mainstream interfaces need to be built to work with assistive technology?

Key concepts

screen reader
braille display
screen magnification
switch and scanning input
alternative and augmentative communication
captioning
touchscreen accessibility
human-powered assistance

Key theories

Assistive technology as mediation: Assistive technologies translate between a system's standard output and input and a user's abilities, for example turning visual content into speech or braille and physical actions into commands, which requires the underlying content to be properly structured.
Making touchscreens accessible: Touchscreens initially excluded blind users; techniques such as gesture-based exploration with audio feedback, demonstrated by Slide Rule, showed how multi-touch could be made usable without sight and influenced mainstream mobile accessibility.
Human-powered access: Some access problems exceed automation; systems like VizWiz route visual questions from blind users to remote human workers for near-real-time answers, blending automation with human assistance.

Clinical relevance

Assistive technologies are the practical means by which many people with disabilities access computers, phones, and the internet for work, education, and daily life; their effectiveness depends on mainstream products being built to interoperate with them, linking assistive technology to accessible design.

History

Screen readers and other assistive technologies developed alongside personal computing, but the shift to graphical and then touch interfaces created new barriers that research worked to overcome, as with Slide Rule for touchscreens in 2008. Systems such as VizWiz pioneered human-powered access, and mobile platforms later built screen readers and accessibility services into mainstream operating systems.

Key figures

Jonathan Lazar
Shaun K. Kane
Jeffrey P. Bigham
Jacob O. Wobbrock

Seminal works

kane2008
bigham2010
lazar2015

Frequently asked questions

How does a screen reader work?: A screen reader reads the content and structure of an interface aloud or sends it to a braille display, letting users without sight navigate by headings, links, and controls. It relies on the underlying content being properly labelled and structured, which is why accessible coding matters so much.
Why do mainstream apps need to support assistive technology?: Assistive technologies can only convey what an interface exposes. If buttons are unlabeled or content is not in a readable structure, a screen reader cannot describe it. Building apps with proper labels, semantics, and keyboard support lets assistive technologies do their job.