Assistive Technology: Tools People Use to Browse
Also called: AT, Assistive technologies, Assistive tools, Adaptive technology
Definition
Assistive technology (AT) is software and hardware that people with disabilities use to improve their interaction with the web, such as screen readers, screen magnifiers, speech recognition, switches and refreshable braille displays. It works through the information a website exposes to the browser and operating system.
Assistive technology is the umbrella term for the tools people with disabilities use to read, navigate and operate websites – from a screen reader that speaks a page aloud to a switch operated with one breath. Your website does not control these tools, but it decides whether they can do their job. Clean code lets assistive technologies work; missing names, roles and keyboard support break them.
What it means
W3C defines assistive technologies as "software and hardware that people with disabilities use to improve interaction with the web". It sets them apart from adaptive strategies – techniques such as increasing text size, reducing mouse speed or turning on captions, which often use standard browsers and devices.
| Assistive technology | Who uses it | What your site must provide |
|---|---|---|
| Screen reader | Blind people and people who cannot read text | Alt text, an accessible name for every control, real headings |
| Refreshable braille display | Blind and deafblind people, usually with a screen reader | The same text information as a screen reader |
| Screen magnifier | People with some types of low vision | Layouts that reflow, focus that stays visible when zoomed |
| Speech recognition (voice control) | People who cannot use a keyboard or mouse | Visible labels that match the code – label in name |
| Switches (single-key, sip-and-puff) | People with severe motor impairments | Full keyboard navigation, no time pressure |
| Eye tracking | People who cannot use their hands | Large, well-spaced targets |
| On-screen keyboard | People who use a pointer instead of keys | Working keyboard events and visible focus |
Most of these tools do not see your design. They read the accessibility tree the browser builds from your HTML. That is why WCAG 4.1.2 Name, Role, Value requires that the name and role of every component can be programmatically determined, and that state changes are passed on to assistive technologies. W3C's overview of tools and techniques describes many more of them.
Examples
<!-- Voice control users say "click Subscribe" – the name matches the visible text -->
<button type="submit">Subscribe</button>
<!-- Switch and keyboard users can reach and toggle it; screen readers hear the state -->
<button type="button" aria-expanded="false" aria-controls="menu">Menu</button>
<!-- Invisible to most assistive technology: no role, no name, no keyboard access -->
<div class="btn" onclick="subscribe()"></div>Use native elements, label every control with visible text, keep focus visible, support zoom and reflow, and let users finish tasks without a time limit or precise mouse moves.
Build controls from div elements without roles, require drag-and-drop or hover only, hide focus outlines, or block zoom with user-scalable=no.
How to test with assistive technology
Questions
What are examples of assistive technology?
Screen readers, refreshable braille displays, screen magnifiers, speech recognition, switches (including sip-and-puff), eye tracking, on-screen keyboards, alternative keyboards and mice, and word prediction software.
What is the difference between assistive technology and accessibility features?
Assistive technology is a separate tool, like a braille display or a screen reader. Accessibility features are built into content or devices – captions, zoom, text-to-speech. Many people use both.
Does my website need to support assistive technology by law?
Laws such as the European Accessibility Act point to WCAG through EN 301 549, and WCAG requires content to be compatible with assistive technologies, for example through criterion 4.1.2.
How do I find out if my website works with assistive technology?
Combine a manual test with a screen reader and the keyboard with an automated check for missing names, labels and alt text. The free WCAG scanner runs that automated check on any page.
Related terms
Screen Reader: How It Reads Websites and What It Needs
A screen reader is assistive software that reads the content and controls of a screen aloud or outputs them on a braille display. It relies on the names, roles and states that a website exposes through the browser's accessibility tree.
Read definition: Screen Reader: How It Reads Websites and What It NeedsKeyboard Navigation: WCAG 2.1.1 Explained
Keyboard navigation means that every function of a website can be reached and operated with a keyboard alone – usually with Tab, Shift+Tab, Enter, Space and the arrow keys. WCAG 2.1.1 requires it at Level A.
Read definition: Keyboard Navigation: WCAG 2.1.1 ExplainedAccessible Name: What It Is and How It Is Computed
The accessible name is the text that browsers pass to assistive technology to identify an element – for example the words a screen reader announces for a button, link or form field. WCAG 4.1.2 requires a programmatically determinable name for every user interface component.
Read definition: Accessible Name: What It Is and How It Is ComputedName, Role, Value: Controls Screen Readers Understand
Name, Role, Value is WCAG success criterion 4.1.2: for every user interface component, the name and role can be programmatically determined, user-settable states, properties and values can be programmatically set, and changes are announced to assistive technologies. It is Level A.
Read definition: Name, Role, Value: Controls Screen Readers Understand