Assistive technology (AT) is an umbrella term covering the systems and services related to assistive products. It can include tools people use themselves (like screen readers) and features built into devices, operating systems and websites (such as keyboard navigation or captioning). Both people with and without disabilities use AT. For example, speech recognition software (like Siri or Alexa) is a form of AT. This page introduces what assistive technology is, who uses it, and why it’s important to consider when designing, writing and building digital services.
Many assistive technologies are already built into everyday devices like phones, tablets and computers. Operating systems and browsers include features such as screen readers, magnification, captions, voice control and keyboard navigation at no additional cost.
Because these tools are built in, people may use assistive technology without realizing it, for example, increasing text size, using captions on videos or navigating with a keyboard instead of a mouse.
While some people use specialized or customized tools, assistive technology does not always require expensive equipment. Designing and building accessible digital content ensures these built-in tools work as intended for everyone.
Assistive technology is not used by a single group of people for a single set of needs. We all use it, even if we don’t realize it. Some people need to use assistive technology, and others choose to use it because it makes things easier. For example:
Because needs vary from person to person, many people use a combination of assistive technologies and accessibility features depending on the task or environment.
Understanding assistive technology helps designers, developers and content creators build experiences that work for a wider range of people.
Keyboard navigation allows users to navigate through content using only their keyboard and is one of the most important aspects of web accessibility. We all use it at some point, but it is essential for people who use screen readers or alternative input devices.
Screen readers are software applications that read digital content aloud. Screen readers are essential for people who are blind, but are also useful for people with low vision, low literacy or learning disabilities.
Screen magnifiers are software applications that increase the size of text and graphics on a computer screen. Screen magnifiers are typically used by people with low vision.
Voice recognition systems enable users to interact with technology by speaking to it. They're often used by people with limited motor skills but are also useful for people with learning disabilities or low vision.
Captions display spoken content and important sounds as text, while transcripts provide a text version of audio or video content. They're essential for people who are Deaf or hard of hearing and are also useful in noisy or quiet environments.
Text-to-speech tools read written content aloud. They are commonly used by people with learning disabilities, low vision or cognitive disabilities, and by anyone who benefits from listening instead of reading.
Browsers and operating systems include accessibility settings such as high contrast modes, reduced motion, text resizing and color adjustments. These settings help users customize their experience to meet their visual, cognitive or motor needs.
Alternative input devices allow people to interact with technology without using a standard mouse or keyboard. These include switches, eye-tracking systems and adaptive keyboards, and are often used by people with motor disabilities.
While this toolkit focuses on digital accessibility, assistive technology also includes non-digital tools, such as:
You can learn more about assistive technology by reading:
The best way to evaluate accessibility is by testing with people who need to use assistive technology (AT). Whenever possible, teams should plan and budget for accessibility testing with people with disabilities or qualified accessibility professionals.
At the same time, not every organization has regular access to native users of AT, and if they do, the same people are often asked to help with testing again and again. Building basic AT testing skills within your team helps identify common barriers earlier in the design and development process and reduces reliance on a small group of testers. This is not a replacement for working with people who have lived experience, but it can complement it and improve overall accessibility outcomes.
Examples of basic testing include: