# Assistive Technology: Tools People Use to Browse

Source: https://allyway.ai/glossary/assistive-technology

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](https://allyway.ai/glossary/screen-reader) | Blind people and people who cannot read text | [Alt text](https://allyway.ai/glossary/alt-text), an [accessible name](https://allyway.ai/glossary/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](https://allyway.ai/glossary/reflow), focus that stays visible when zoomed |
| Speech recognition ([voice control](https://allyway.ai/glossary/voice-control)) | People who cannot use a keyboard or mouse | Visible labels that match the code – [label in name](https://allyway.ai/glossary/label-in-name) |
| Switches (single-key, sip-and-puff) | People with severe [motor impairments](https://allyway.ai/glossary/motor-impairments) | Full [keyboard navigation](https://allyway.ai/glossary/keyboard-navigation), no time pressure |
| Eye tracking | People who cannot use their hands | Large, well-spaced [targets](https://allyway.ai/glossary/target-size) |
| 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](https://www.w3.org/WAI/WCAG22/Understanding/name-role-value.html) 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](https://www.w3.org/WAI/people-use-web/tools-techniques/) describes many more of them.

> **Tip:** > **One rule covers most tools**
> If everything works with the keyboard alone and every element has a clear name and the right role, screen readers, [switches](https://allyway.ai/glossary/switch-control), voice control and braille displays usually work too. Native HTML elements give you both for free.

## Examples

```html title="Example"
<!-- 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>
```

**Do:** Do

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.

**Don't:** Don't

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

Q: What are examples of assistive technology?
A: 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.

Q: What is the difference between assistive technology and accessibility features?
A: 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.

Q: Does my website need to support assistive technology by law?
A: Laws such as the [European Accessibility Act](https://allyway.ai/regulations/eaa) point to WCAG through EN 301 549, and WCAG requires content to be compatible with assistive technologies, for example through criterion 4.1.2.

Q: How do I find out if my website works with assistive technology?
A: 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](https://allyway.ai/free-wcag-accessibility-scanner-for-websites) runs that automated check on any page.
