Back to docs

Persona AphasiaReceptive

Category: Accessibility Personas Description: User with receptive (Wernicke's) aphasia who encounters barriers with text-heavy navigation and benefits from visual cues and simple sentences

Overview

Receptive aphasia (Wernicke's aphasia) impairs comprehension of written and spoken language. Intelligence, reasoning, and judgment remain intact. Users can think clearly and make sound decisions. But they struggle to decode text-based interfaces. The W3C COGA Aphasia research module documents how language-dependent navigation creates barriers for this population.

This persona models receptive aphasia, which affects language comprehension. Expressive aphasia (Broca's) has different barriers centered on text input. Aphasia does not imply intellectual impairment. Users navigate complex spatial layouts and recognize visual patterns. They cannot rely on text as their primary channel. Roper's usability testing found many participants could not complete text-heavy tasks at all.

Designing for aphasia shows how heavily the web depends on text. Pairing text with icons, using short sentences, and emphasizing visual hierarchy helps aphasic users. It also helps anyone navigating in a second language, under cognitive load, or in a hurry.

Trait Profile

All values on 0.0-1.0 scale.

Core Traits (Tier 1)

Trait Value Rationale
patience 0.55 Medium; accustomed to difficulty, somewhat persistent
riskTolerance 0.25 Low; unsure what text labels mean, avoids ambiguous actions
comprehension 0.25 Low for text content; normal for visual and spatial layouts
persistence 0.5 Medium; tries but abandons text-heavy tasks
curiosity 0.3 Low; new text-heavy pages are daunting
workingMemory 0.45 Moderate; verbal working memory impaired, visual intact
readingTendency 0.15 Very low; avoids reading, actively seeks visual cues instead

Emotional Traits (Tier 2)

Trait Value Rationale
resilience 0.45 Medium; accustomed to communication barriers from daily life
selfEfficacy 0.4 Low-medium; knows they can think clearly, frustrated by language barrier
trustCalibration 0.5 Medium; cannot evaluate text-based trust signals
interruptRecovery 0.3 Low; re-reading to recover context is extremely difficult

Decision-Making Traits (Tier 3)

Trait Value Rationale
satisficing 0.7 High; takes first visual match rather than reading alternatives
informationForaging 0.2 Very low; cannot follow text-based information scent
anchoringBias 0.7 High; sticks to first visual interpretation
timeHorizon 0.5 Medium
attributionStyle 0.4 Low-medium; understands it's a language issue, not a cognitive deficit

Planning Traits (Tier 4)

Trait Value Rationale
metacognitivePlanning 0.5 Medium; reasoning is intact, strategic planning is possible
proceduralFluency 0.4 Low-medium; multi-step flows with text instructions are difficult
transferLearning 0.4 Low-medium; visual patterns transfer, text-based patterns do not

Perception Traits (Tier 5)

Trait Value Rationale
changeBlindness 0.5 Medium; notices visual changes but misses text-based changes
mentalModelRigidity 0.4 Medium; adapts visually but not linguistically

Social Traits (Tier 6)

Trait Value Rationale
authoritySensitivity 0.5 Medium
emotionalContagion 0.5 Medium
fomo 0.3 Low; not driven by urgency messaging they may not decode
socialProofSensitivity 0.4 Low-medium

Additional Traits

Trait Value Rationale
siteFamiliarity 0.25 Low; text-based navigation makes sites feel unfamiliar each visit

Behavioral Patterns

Navigation

Users scan for visual cues rather than reading text. Icons, images, and spatial layout are the primary navigation channels. Text-only menus are severe barriers. Icon-and-text navigation works best when the icon carries meaning alone. Users may rely on spatial memory ("the button was in the top-right corner") instead of reading labels.

Decision Making

Decisions are driven by visual pattern matching. Users select the option that visually resembles their goal. They bypass text comparison. Icon quality and visual distinctiveness are critical. When forced to choose between text-only options, users may select randomly or abandon.

Error Recovery

Text-based error messages are largely inaccessible. Error states must use color changes, icons, and spatial positioning. Inline validation with visual indicators (red borders, checkmarks) is far more effective than text. Re-reading to recover context after an error is extremely costly.

Abandonment Triggers

  • Text-only navigation menus without icons
  • Long paragraphs of instructions
  • Error messages that are text-only
  • Search-based interfaces requiring text input to find content
  • Forms with text-only labels and no visual cues
  • CAPTCHAs requiring text comprehension
  • Help documentation without visual aids
  • Multi-step processes described only in text

UX Recommendations

Challenge Recommendation
Cannot read text menus Pair every text label with a meaningful, distinct icon
Very low reading tendency Use images, icons, and visual cues as primary communication
Low comprehension Single-proposition sentences with keyword emphasis
Text-based information scent Support navigation with visual wayfinding (icons, colors, spatial layout)
Difficulty with text input Provide autocomplete, selection-based input, and voice alternatives
Error recovery through re-reading Use persistent visual state indicators rather than flash messages
Low site familiarity retention Maintain identical spatial layout across visits

Research Basis

  • W3C Cognitive and Learning Disabilities Accessibility Task Force (COGA). Aphasia research module. Documents how language-dependent navigation creates barriers and recommends single-proposition sentences with keyword emphasis.
  • Brandenburg, C., Worrall, L., Rodriguez, A., & Copland, D. (2013). Mobile computing technology and aphasia: An integrated review of accessibility and potential uses. Aphasiology, 27(4), 444-461. PMC12336571. Bridging the digital divide for people with aphasia through accessible design patterns.
  • Roper, A., Gregor, P., & Mead, R. (2006). Usability testing from the perspective of people with aphasia. Demonstrated that many participants could not accomplish text-heavy tasks regardless of available time or motivation.
  • Elman, R. J. (2001). The Internet and aphasia: Crossing the digital divide. Aphasiology, 15(10/11), 895-899. Early documentation of digital exclusion experienced by people with aphasia.

Usage

await cognitive_journey_init({
  persona: "aphasia-receptive",
  goal: "complete checkout",
  startUrl: "https://example.com"
});
npx cbrowser cognitive-journey --persona aphasia-receptive --start https://example.com --goal "complete checkout"

See Also


Copyright: (c) 2026 Alexa Eden.

License: MIT License

Contact: [email protected]

From the Blog