Skip to content
Tutorials Center
My learning

Topics

Lesson 3 of 38 ยท Getting Started

Assistive Technologies

Understand how screen readers, magnifiers, switch devices, voice control and braille displays use your page, and how the accessibility tree connects them to your HTML.

Assistive technology (AT) is software or hardware that helps a person use a computer. Some of it is built in to the operating system, and some is a separate product. To build an accessible page you do not need to master every tool, but you do need to know what they need from your HTML. This lesson explains the main ones and shows the bridge between your markup and them: the accessibility tree.

As noted in lesson 1, screen readers and operating-system settings cannot run inside the editors on this site. The examples here use plain HTML to show what a tool would receive.

The main kinds of AT

  • Screen readers speak text aloud or output it to braille. Popular ones are NVDA and JAWS on Windows, VoiceOver on macOS and iOS, TalkBack on Android and Narrator on Windows. Orca is common on Linux.
  • Screen magnifiers enlarge part of the screen, often with colour inversion and cursor tracking.
  • Voice control such as Dragon, Voice Control on Apple devices and Voice Access on Android lets people say "click Save" or "show numbers".
  • Switch devices let someone with very limited movement operate a computer with one or two buttons, scanning through items one by one.
  • Alternative keyboards and pointers include head trackers, eye trackers, sip-and-puff devices and on-screen keyboards.
  • Browser and OS settings such as zoom, text-only zoom, forced colours (Windows high-contrast mode), reduced motion and captions.

How a screen reader user actually browses

Sighted users scan. Screen reader users have equivalents. They jump by headings, landmarks (navigation, main, search), links, form fields or tables, or open a list of all links on the page. They rarely listen to a page from top to bottom. Because of this, your structure is your interface: headings and landmarks are the navigation menu of a page for them.

How a screen reader browses

Headings Jump to the next section
Landmarks Skip to main or search
Links list Scan every link by name
Form fields Move between labelled inputs

Your markup becomes the page's menu.

1 / 2

From HTML to the accessibility tree

Browsers build the DOM from your HTML. In parallel they build an accessibility tree: a simplified structure containing only what AT needs. Each node has a role (what it is), a name (what it is called), a state (such as checked or expanded) and sometimes a description. The platform then exposes this tree through an accessibility API, and the screen reader reads from it.

flowchart LR
  A["HTML + CSS + JS"] --> B["DOM"]
  B --> C["Accessibility tree<br/>role, name, state"]
  C --> D["Platform accessibility API"]
  D --> E["Screen reader / voice control / switch"]

Your markup decides what lands in the tree.

This is why native elements matter. A <button>Save</button> becomes a node with role "button" and name "Save". A <div>Save</div> becomes generic text. The browser's developer tools show the tree: in Chrome and Edge open the Elements panel, then the Accessibility tab; in Firefox use the Accessibility panel.

Try it: see roles and names in code

The browser exposes some of this tree to JavaScript through computed properties in newer engines, but the portable way to inspect it is to read the semantic markup. This demo lists the elements that carry a native role and shows the role a screen reader would announce.

What roles does this markup create?

The role table is hand-written for this demo, and in real browsers header is only the "banner" role when it is not inside main or another sectioning element. The point is the mapping: each native element hands AT a role for free.

What AT needs from you

  1. Correct roles: use the right element, and ARIA only when no native one fits.
  2. Names: every interactive control needs an accessible name from a label, its text content, alt or aria-label.
  3. States: checked, expanded, selected, invalid and disabled must be real states, not only visual styling.
  4. Order: the reading order follows the DOM, so keep the source order meaningful.
  5. Notifications: dynamic changes need a way to be announced, which you will learn with live regions later.

Try it: a name makes the difference

Named and unnamed controls

The first button depends on how the screen reader treats the emoji, which is unreliable. The second states its purpose. Prefer visible text where space allows, and aria-label for icon-only controls.

Testing with AT

Real screen reader testing is the gold standard. NVDA is free, and VoiceOver ships with every Apple device. You do not need to become an expert: learn a handful of commands, listen to how your page reads, and fix what sounds wrong. The testing chapter covers this step by step.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. What is the accessibility tree?

    Browsers derive it from the DOM and expose it through platform accessibility APIs for AT to read.
  2. 2. How do screen reader users commonly move around a page?

    They use quick-navigation commands, so headings and landmarks work like a page menu.
  3. 3. Which element gives a control the role button automatically?

    Native button carries the role, keyboard behavior and focus. A div or span carries none of them.
  4. 4. An icon-only button has no text. What should you add?

    Without a name, AT can only announce "button". An accessible name tells users what it does.

Summary

  • Assistive technology includes screen readers, magnifiers, voice control, switches and OS settings.
  • Screen reader users navigate by structure, so headings and landmarks matter.
  • Browsers build an accessibility tree of roles, names and states from your markup.
  • Native elements give correct roles, names and keyboard behavior with no extra work.
  • Real testing with a screen reader reveals issues that tools cannot.

Next: Your First Accessible Page