Assistive Technology

Concept facts

Assistive technology is hardware, software, equipment, or a system feature that helps people with disabilities or functional limitations access, understand, operate, or communicate with digital and physical services.

Also known as: AT, access technology, adaptive technology, support technology.
Used in: Accessibility, inclusive design, screen-reader testing, keyboard access, service delivery, public-sector systems, education platforms, health systems, and digital product evaluation.
Interpret with: Accessibility, screen reader testing, keyboard accessibility, focus order, alternative text, accessible name, cognitive accessibility, and inclusive design.

Plain-language explanation

Assistive technology helps people interact with services when standard interaction patterns are not enough. Examples include screen readers, screen magnifiers, speech recognition, switch devices, alternative keyboards, captioning systems, hearing support tools, and built-in operating-system accessibility features.

In digital UX work, assistive technology matters because a product can look usable to one user but remain difficult or impossible for another user who relies on different input or output support.

Assistive technology should not be treated as an edge case. It is part of the real service environment.

Why it matters

Many public, financial, education, health, and civic services require users to complete high-stakes tasks. If a form, status message, dashboard, document, or mobile flow does not work with assistive technology, users may lose access, miss deadlines, submit incorrect information, or need help from staff or family members.

Assistive-technology barriers can also create privacy and independence problems. A user who cannot complete a task independently may have to disclose personal, financial, health, or eligibility information to someone else.

Use contexts

Assistive technology is relevant when evaluating:

public-service application forms
banking, fintech, and KYC flows
health appointment and referral systems
education and training enrollment platforms
dashboard and case-management tools
document upload, payment, and verification journeys
mobile apps and web portals used by diverse users
service content, status messages, and support channels

Application guidance

Evaluate assistive-technology compatibility through standards-aware review and practical testing. Automated accessibility checks can identify some issues, but they do not confirm whether a real task works with assistive technology.

Check that controls have accessible names, focus order is logical, status changes are communicated, headings support navigation, forms provide understandable instructions, and errors can be found and corrected.

Include assistive-technology users in research where appropriate and ethical. When that is not possible, use expert review and standards-based testing as a minimum step, while clearly noting the limitation.

Do not assume that all assistive-technology users have the same needs. The same service may need to support screen readers, magnification, keyboard navigation, voice input, captions, simplified content, or multiple forms of support.

Practical example

A public scholarship application portal requires applicants to upload identity documents, choose an institution, and confirm eligibility. The page appears visually clear, but the upload control does not have a usable accessible name and the confirmation status is only shown visually.

An applicant using a screen reader cannot confirm whether the document was uploaded. The UX consequence is not only inconvenience. The applicant may miss the deadline, submit an incomplete application, contact support repeatedly, or lose eligibility because the system did not communicate task status through assistive technology.

Interpretive boundaries

Assistive technology is not limited to screen readers. It includes many tools and settings that support perception, input, communication, and cognition.

Compatibility with assistive technology does not guarantee that the overall service is usable or inclusive. Content clarity, workflow, trust, support, language, and policy interpretation still matter.

Assistive-technology testing should not be used as a substitute for broader accessibility and usability work.

Applied at Userhub

Userhub considers assistive technology when evaluating whether digital services can be used across varied abilities, devices, literacy levels, and support conditions.

In UX Lab work, assistive-technology review helps identify barriers that affect service access, independent task completion, accessibility compliance, and user confidence in high-friction journeys.

See Userhub UX Lab for applied UX research and evaluation context.

Sources and references

World Wide Web Consortium. (n.d.). Introduction to web accessibility. W3C Web Accessibility Initiative. https://www.w3.org/WAI/fundamentals/accessibility-intro/

World Wide Web Consortium. (2024). Web Content Accessibility Guidelines (WCAG) 2.2. W3C Recommendation. https://www.w3.org/TR/WCAG22/

World Wide Web Consortium. (2021). Making content usable for people with cognitive and learning disabilities. W3C Working Group Note. https://www.w3.org/TR/coga-usable/

Cook, A. M., Polgar, J. M., & Encarnação, P. (2019). Assistive technologies: Principles and practice (5th ed.). Elsevier. https://doi.org/10.1016/C2016-0-02627-X

Desmond, D., Layton, N., Bentley, J., Boot, F. H., Borg, J., Dhungana, B. M., Gallagher, P., Gitlow, L., Gowran, R. J., Groce, N., Mavrou, K., Mackeogh, T., McDonald, R., Pettersson, C., & Scherer, M. J. (2018). Assistive technology and people: A position paper from the first global research, innovation, and education on assistive technology summit. Disability and Rehabilitation: Assistive Technology, 13(5), 437–444. https://doi.org/10.1080/17483107.2018.1471169

Userhub. (2026). Assistive Technology. UX Reference. https://userhub.com.bd/reference/assistive-technology/

Reference entry content