Types of disabilities and assistive technologies on the CPACC exam

Disabilities and assistive technologies make up one of the largest sections of the CPACC Body of Knowledge. The exam does not test medical definitions — it tests whether you understand how people interact with digital products and what breaks when accessibility is not considered.

Why this section matters

Most accessibility failures are not caused by malice. They happen because the person building the product could not picture a user whose experience differs from their own. This section of the exam exists to close that gap — to make sure certified professionals can reason about real users, not abstract compliance checklists.

Disability categories on the CPACC exam

The CPACC organises disabilities into broad categories. For each one, you need to understand: what the disability involves, what barriers it creates in digital environments, and which assistive technologies address those barriers.

Visual disabilities

Blindness

Users who are blind cannot perceive any visual content. They rely entirely on non-visual output.

• Barriers: images without alt text, unlabelled form fields, content that only makes sense visually (colour-coded charts without text equivalents), inaccessible PDFs.
• Assistive technology: screen readers (JAWS, NVDA, VoiceOver, TalkBack), refreshable braille displays.

Low vision

Users with low vision can see some content but need it enlarged, recoloured, or simplified. This is a wide spectrum — from mild difficulty reading small text to functional vision limited to a narrow area.

• Barriers: fixed font sizes, poor colour contrast, layouts that break when zoomed to 200% or beyond, information conveyed only through colour.
• Assistive technology: screen magnifiers (ZoomText, built-in OS zoom), high-contrast modes, custom stylesheets, screen readers (some low-vision users combine magnification with audio).

Colour vision deficiency

Often called “colour blindness,” though total colour blindness is rare. Most affected users have difficulty distinguishing specific colour pairs — typically red/green.

• Barriers: status indicators that rely solely on colour (red = error, green = success), charts without patterns or labels, links distinguished from body text only by colour.
• Assistive technology: colour filters and overlays (built into most operating systems), but the primary solution is better design, not AT.

Auditory disabilities

Deafness

Users who are deaf cannot perceive audio content at all.

• Barriers: video without captions, audio-only content (podcasts, voice instructions), alerts that use only sound.
• Assistive technology: captions and subtitles, transcripts, visual notification systems. Sign language interpretation for live events.

Hard of hearing

Users who are hard of hearing perceive some audio but may miss speech in noisy environments or struggle with unclear audio.

• Barriers: same as deafness but less absolute — poor audio quality, background noise, and missing captions all reduce comprehension.
• Assistive technology: captions, hearing loops (in physical spaces), volume controls, audio clarity adjustments.

Motor and mobility disabilities

This category covers a wide range — from tremors and limited fine motor control to full paralysis.

• Barriers: small click targets, drag-and-drop without keyboard alternatives, time-limited interactions, hover-dependent interfaces, complex gestures required on mobile.
• Assistive technology: alternative keyboards (expanded, compact, on-screen), switch devices (single-switch or sip-and-puff), head tracking, eye tracking, voice control (Dragon NaturallySpeaking, Voice Control on macOS/iOS), mouth sticks, adaptive pointing devices.

“Motor disability is where the gap between ‘works with a mouse’ and ‘works with anything else’ becomes most visible.”

Cognitive, learning, and neurological disabilities

This is the broadest and most varied category. It includes intellectual disabilities, learning disabilities (dyslexia, dyscalculia), attention deficit disorders, autism spectrum conditions, memory impairments, and seizure disorders.

• Barriers: complex language, dense layouts, inconsistent navigation, unexpected behaviour (auto-redirects, popups), flashing content (seizure risk), time pressure, lack of error recovery.
• Assistive technology: text-to-speech tools, reading rulers, simplified interface modes, content blockers, dictation software, symbol-based communication tools. Many users in this category rely more on design choices (clear language, consistent layout, forgiving interactions) than on dedicated AT.

Speech disabilities

Users with speech disabilities may have difficulty being understood by voice-recognition systems or by other people in voice-based interactions.

• Barriers: voice-only authentication, customer support that requires a phone call, voice-controlled interfaces with no text alternative.
• Assistive technology: augmentative and alternative communication (AAC) devices, text-based communication tools, speech-generating devices.

Disability models — what the exam expects

The CPACC does not just test disability categories — it tests how you think about disability. Two models come up repeatedly:

The medical model

Views disability as a condition that belongs to the individual — something to be treated, cured, or compensated for. The focus is on what is “wrong” with the person.

The social model

Views disability as a mismatch between the person and their environment. The barrier is in the design, not in the person. A wheelchair user is not disabled by their legs — they are disabled by the staircase.

The CPACC exam leans heavily toward the social model. Accessibility work is fundamentally about removing environmental barriers, not fixing people. Expect questions that test whether you understand this distinction and can apply it.

“The social model does not deny that impairments exist. It argues that the disabling factor is the environment’s failure to accommodate them.”

Other models you should recognise

• Biopsychosocial model (WHO ICF framework) — combines medical and social perspectives. Disability results from the interaction between health conditions, personal factors, and environmental factors.
• Economic model — frames disability in terms of economic impact: lost productivity, cost of accommodation, market opportunity.
• Charity model — treats people with disabilities as objects of pity who need help. Widely criticised in the disability community.
• Identity/cultural model — some communities (particularly the Deaf community) view their disability as a cultural identity, not a deficit.

The exam expects you to compare these models and recognise which one a given statement or policy reflects.

Assistive technology — how deep do you need to go?

The CPACC does not ask you to configure a screen reader or write ARIA code. It asks you to understand:

1. What each AT category does — screen readers convert visual content to speech or braille; magnifiers enlarge portions of the screen; switch devices replace keyboard/mouse input.
2. Who uses what — which AT maps to which disability category.
3. How AT interacts with content — a screen reader relies on semantic HTML and the accessibility tree; a magnifier relies on responsive layout and sufficient contrast; voice control relies on visible labels matching accessible names.
4. What breaks when content is not accessible — the practical consequence, not the WCAG criterion number.

AT category	Primary users	Relies on
Screen readers	Blind, some low-vision users	Semantic markup, alt text, ARIA, focus management
Screen magnifiers	Low-vision users	Responsive layout, contrast, reflow
Voice control	Motor disabilities, some cognitive	Visible labels, accessible names, keyboard operability
Switch devices	Severe motor disabilities	Focus order, keyboard operability, no time limits
Captions/transcripts	Deaf, hard of hearing	Accurate synchronised text, speaker identification
Reading tools	Dyslexia, cognitive	Clear structure, plain language, consistent navigation
AAC devices	Speech disabilities	Text-based alternatives to voice interactions

How to study this section

This is the section where flashcards earn their keep. The material is wide but not deep — you need to recall mappings (disability → barrier → AT → solution) quickly and consistently. The pattern is always the same:

1. A user has a specific disability.
2. That disability creates a specific barrier in a digital product.
3. An assistive technology bridges that barrier — if the content is built accessibly.
4. If the content is not built accessibly, the AT fails and the user is excluded.

Practise by taking any interface element — a form, a video player, a navigation menu — and walking through each disability category: what breaks, for whom, and why. That exercise maps directly to how the CPACC frames its questions.