When assistive technology is recommended but not actually working

Assistive technology is often recommended with good intentions. A person may be advised to use a screen reader, magnification software, voice control, switch access, an adapted keyboard, a tablet, specialist software or a particular accessibility setting.

But a recommendation does not automatically create access.

In real life, people still have to open the device, find the right file, navigate the software, recover from mistakes, manage fatigue, remember steps, use the setup across different environments and explain what they need when something changes.

That is where many access plans break down.

The problem is not always the technology

When assistive technology is not working, it is easy to assume that the wrong tool has been chosen. Sometimes that is true. But often, the tool itself is not the main issue.

The problem may be that:

• the software has not been configured properly
• the person has not had enough structured training
• the setup only works in one situation
• the support team does not know how to maintain it
• documents, websites or workplace systems remain inaccessible
• the device is physically difficult to use
• the steps rely too much on memory, stamina or fine motor control
• nobody has written down the working route clearly

Assistive technology needs to fit the person, the task, the environment and the people around them.

A working setup needs to be tested against real tasks

A setup can look successful in a short demonstration but still fail during normal daily use.

For example, a screen reader may open correctly, but can the person use it to find an email attachment? Can they move through a form? Can they recover if they land in the wrong window? Can they use it when they are tired, under pressure or working with unfamiliar documents?

The same applies to magnification, voice control, switches, adaptive hardware and AI-supported tools. The real question is not simply “does this tool work?” The better question is:

Can this person use this setup to complete the task they actually need to do?

Training needs to be practical and repeatable

One-off training is rarely enough for complex access needs.

People need time to build confidence. They may need the same route broken into clear steps. They may need practice across different examples. They may need support staff, family members, employers or education teams to understand the method as well.

Good assistive technology support should make the route easier to repeat. This might include:

• clear shortcut lists
• step-by-step task guides
• setup notes
• error recovery strategies
• agreed routines
• staff guidance
• follow-up review points

The aim is not to make someone dependent on support. The aim is to make independence more realistic.

Handover matters

Access can fall apart when only one person understands the setup.

If the person changes school, job, device, software version or support team, the access route needs to survive that change. Clear handover notes make a difference.

A useful handover explains what has been set up, why it has been set up that way, what the person can currently do, what still needs support, and what should happen next.

This is especially important when several people are involved, such as family members, case managers, occupational therapists, rehabilitation professionals, education staff, employers, IT teams or care teams.

The gap between recommendation and real access

The most useful assistive technology work often happens after the recommendation.

It happens when the setup is tested, adjusted, explained, documented and built into daily routines.

That is the gap AGL Access Works focuses on: the space between “this should help” and “this actually works for the person using it.”

Related service: assistive technology implementation support turns a recommendation into a working everyday routine.

Back to all insights