Assistive Technologies and Adaptive Strategies
What this domain tests
Domain 3 covers assistive technology (AT) categories, how AT depends on accessible content and interoperability, and adaptive strategies people use.
Core rules
- AT is any item, equipment, software, or product system used to maintain or improve functional capabilities (US Assistive Technology Act definition).
- Sensory: screen readers (JAWS, NVDA, VoiceOver), braille displays, screen magnifiers, hearing aids, cochlear implants, captioning, alerting devices.
- Physical/motor: switch access, eye gaze, head pointers, adapted keyboards, speech recognition, wheelchairs, prosthetics.
- Cognitive/learning: text-to-speech, word prediction, graphic organizers, memory aids.
- Communication: AAC devices and symbol systems.
- Mainstream technology (smartphones, captions, voice assistants) often contains built-in accessibility features.
- AT works only when content is interoperable: semantic HTML, accessible names, alt text, captions, keyboard access, and no traps.
Worked example
A blind employee uses a screen reader on an internal expense tool. The “Submit” control is a <div> with a click handler, no role, no accessible name. Reasoning: the screen reader announces nothing actionable; the fix is a native <button> with visible text or aria-label, plus keyboard focus. Adding a tooltip does not fix it. The AT is not “broken”; the content lacks the semantics AT needs.
Traps
Assuming one AT per disability; thinking AT compensates for inaccessible design; confusing captions (synchronized text) with transcripts (text alternative); assuming all Deaf people use hearing aids or speech; ignoring AT interoperability and user training.