Assistive Technology

What is assistive technology?

Assistive technology (AT) is any hardware or software that helps a person with a disability use a computer or access digital content. In web accessibility, it refers to tools that let people with visual, hearing, motor, cognitive, or speech impairments interact with websites and applications.^[1]

Why does assistive technology matter for website owners?

Accessibility laws define "accessible" in practical terms: a product is accessible when it works with common assistive technologies. If your website breaks when someone uses a screen reader, voice control, or a switch device, it may not meet WCAG — and that means it may not meet legal requirements in the EU, UK, or US.

For organizations with high-traffic, regulated sites — government portals, banking platforms, healthcare systems, university websites — supporting assistive technology is not optional. It is a legal baseline.

What types of assistive technology exist?

For visual impairments:

• Screen readers — Software like JAWS, NVDA, and VoiceOver that reads content aloud or sends it to a braille display.
• Braille displays — Hardware devices that show text as tactile dots, updated line by line as the user navigates.
• Screen magnifiers — Tools like ZoomText that enlarge parts of the screen for people with low vision.
• High contrast modes — System settings that override colors to maximize contrast.^[2]

For motor impairments:

• Switch devices — Single- or multi-button controls that let users cycle through options and select them, for people who cannot use a standard keyboard.
• Eye tracking — Camera systems (e.g., Tobii Dynavox) that let users control a cursor with eye movement.
• Head mice and mouth sticks — Devices that translate head or mouth movement into cursor control.
• Voice control — Software like Dragon NaturallySpeaking that lets users operate a computer by speaking.

For hearing impairments:

• Captioning tools — Software that displays text captions for audio content in real time or synced with recordings.
• Visual alerts — Systems that replace sound notifications with visual ones.

For cognitive and learning disabilities:

• Text-to-speech — Reads text aloud to help people with dyslexia or reading difficulties. Unlike a full screen reader, it does not replace the visual interface.
• Word prediction — Tools that suggest words to reduce typing effort.
• Reading aids — Tools that adjust fonts, spacing, and color overlays to reduce visual stress.^[2]

How does assistive technology interact with web content?

Assistive tools do not process the visual layout of a page. They read the Accessibility Tree — a structured version of the page that the browser builds from HTML and ARIA attributes. The browser exposes this tree through the operating system's accessibility API.^[3]

This has a clear consequence: a visually polished website can be completely broken for assistive technology users if the HTML is not semantic. And a plain site with clean markup can work perfectly with every tool on the market.

IT teams need to understand this. The Accessibility Tree is what matters — not the pixels on screen.

How should organizations test with assistive technology?

The W3C recommends involving people with disabilities throughout design and development, not just at the end. WCAG conformance is necessary but not enough for a genuinely good experience. Subtle issues — confusing announcements, missing context, poor focus management — only surface when real users test with real tools.^[1]

At a minimum, testing should cover:

• A screen reader on desktop (NVDA or JAWS with Chrome or Firefox)
• A screen reader on mobile (VoiceOver on iOS or TalkBack on Android)
• Keyboard-only navigation
• Screen magnification at 200% and 400%

For content teams, this means writing text that makes sense when read linearly, without visual context. For legal teams, it means audit reports should document which assistive technologies were used in testing.

How Askem Helps

The structural issues that most commonly block assistive technology users — missing ARIA attributes, absent alt text, unlabeled form fields, and incorrect roles — can appear across hundreds of pages when a template is updated. Continuous monitoring tools scan for these problems automatically. Tools like Askem run scheduled scans and send alerts when new barriers appear, so IT and content teams can act before users are affected. For large regulated organizations with multiple domains, centralizing this monitoring in one platform keeps the workload manageable.

Sources

1. W3C WAI — How People with Disabilities Use the Web: https://www.w3.org/WAI/people-use-web/
2. W3C — User Agent Accessibility Guidelines (UAAG) 2.0: https://www.w3.org/TR/UAAG20/
3. W3C — Accessibility API Mappings (Core-AAM) 1.2: https://www.w3.org/TR/core-aam-1.2/