What assistive technology is
Assistive technology is a broad term for tools that help a person do something they would otherwise find hard. In education it covers software, hardware and settings: screen readers that speak on-screen text, magnifiers, speech recognition for people who cannot type easily, switch devices for those with limited movement, captioning for people who are deaf or hard of hearing, and text-to-speech tools used by many readers with dyslexia.
None of these tools can do much with material they cannot interpret. That is where open education enters the picture, because the people who produce and reuse open materials can often change how those materials are built.
Why open materials can suit these tools
Three features of open resources help.
First, editable source files. If a resource is shared as a document or web page, rather than only as a locked file, someone can fix a missing heading or add a description to an image. Second, open formats, which are documented publicly and generally supported by a wide range of tools. Third, permission to adapt. An open license that allows changes means a school’s support team does not need to ask a publisher before producing a more compatible version.
These are possibilities, not guarantees. A free textbook published as a scan of printed pages gives a screen reader nothing to read, however generous its license.
What makes content compatible
Assistive tools rely on structure and text. The following features matter most.
- Real headings and lists. A screen reader user often navigates by heading. Text that is only made bold and larger looks like a heading but is not one to the software.
- Text alternatives for images. A short description lets a blind learner understand a diagram. Purely decorative images can be marked so they are skipped.
- Captions and transcripts. Captions help deaf and hard-of-hearing learners, and transcripts help people who prefer to read or who use braille displays.
- Meaningful link text. “Read the guide to fractions” works when links are listed out of context; “click here” does not.
- Keyboard operation. Anyone who cannot use a mouse needs every control to be reachable by keyboard, or through a switch or voice tool that imitates one.
- Labeled form fields and buttons. Quizzes and interactive items need clear labels so users know what to enter.
- Readable color and size. Good contrast and text that can be enlarged without breaking the layout help low-vision users.
The more formal expectations, such as the Web Content Accessibility Guidelines, are summarized in another article on this site; the list above covers the everyday essentials.
Common trouble spots
Some content types cause problems more often than others.
Scanned PDFs. A scan is a picture. Without text recognition, tools see nothing. Even recognized text can come out in the wrong reading order. Where possible, offer the original editable file.
Mathematics and scientific notation. Equations stored as images are unreadable by screen readers. Markup designed for math can usually be read aloud, though support varies between tools, so it is worth testing.
Charts and diagrams. A graph may need both a short description and the data in a table so that the key information is available in text.
Video and audio. Auto-generated captions are a start but often contain mistakes, particularly with technical terms and names. They usually need a human check.
Interactive widgets. Drag-and-drop exercises can be unusable by keyboard unless built with that in mind. Offering an alternative way to complete the task is wise.
Testing with real tools
The most reliable way to learn whether a resource works is to try it. Most computers include a basic screen reader and a way to navigate using only the keyboard. A short test can reveal obvious gaps: does the page read in a sensible order, can you reach every link with the Tab key, do images announce something useful?
Testing yourself is not a substitute for asking learners who rely on these tools daily. They often know which settings and combinations work in practice and which quietly fail. Tool behavior also differs between software and between versions, so a result in one setting does not always carry over to another.
Choosing and supporting the tools
For a student, the best assistive technology is usually the one they are already comfortable with. A learner who uses a particular screen reader should not be asked to switch because a course platform only works well with another. Schools and colleges often have a disability or learning support service that can advise on tools and sometimes provide them. That advice depends on the individual and the setting, so this article cannot replace it.
For educators, a practical rule is to ask early. A short note at the start of a course inviting students to say what format works for them lets you prepare adaptations before a problem arises, rather than after a week of missed content.
Realistic expectations
Open education cannot make every resource compatible with every tool. It can make improvement possible and cheaper, because the right people can edit and share fixes. Compatibility is mostly a matter of careful construction, checking and responding when something fails. Outcomes vary between learners, and a resource that works well for one person using one tool may still be awkward for another.