Category: Accessibility Personas Description: Users who navigate interfaces entirely through screen reader technology due to visual impairment

Overview

Screen reader users experience interfaces through sequential audio and keyboard navigation. This changes the paradigm from visual and spatial to linear and auditory.

Screen reader users develop exceptional patience and persistence. They navigate a world designed without them. They build sophisticated mental models. Their comprehension is high because they process every element sequentially.

The screen reader experience exposes invisible accessibility failures: missing alt text, improper headings, unlabeled fields, focus issues, and unannounced dynamic content. This persona reveals fundamental accessibility barriers.

Trait Profile

All values on 0.0-1.0 scale.

Core Traits (Tier 1)

Trait	Value	Rationale
patience	0.9	Developed through necessity; screen reader navigation is inherently slower
riskTolerance	0.2	Low; unexpected behaviors can cause disorientation without visual context
comprehension	0.8	High; sequential processing encourages deep understanding
persistence	0.9	Extremely high; accustomed to working around accessibility barriers
curiosity	0.6	Interested in exploring but cautious about unfamiliar interfaces
workingMemory	0.7	Often enhanced through training; must hold page structure mentally
readingTendency	0.9	All content is "read"; rely entirely on text and audio

Emotional Traits (Tier 2)

Trait	Value	Rationale
resilience	0.8	High; regularly encounter and overcome accessibility barriers
selfEfficacy	0.7	Confident in abilities despite environmental barriers
trustCalibration	0.6	Appropriately cautious; relies on non-visual trust indicators
interruptRecovery	0.6	Moderate; can recover but interruptions more costly without visual context

Decision-Making Traits (Tier 3)

Trait	Value	Rationale
satisficing	0.5	Balanced; may accept accessible option over optimal inaccessible one
informationForaging	0.6	Systematic but slower; use headings, landmarks, and skip links
anchoringBias	0.5	Moderate; sequential presentation creates different anchoring
timeHorizon	0.6	Willing to invest time for accessibility; balance with efficiency
attributionStyle	0.6	Often recognize system (accessibility) failures vs personal limitations

Planning Traits (Tier 4)

Trait	Value	Rationale
metacognitivePlanning	0.7	Strategic about navigation; plan routes through complex pages
proceduralFluency	0.8	Highly developed screen reader navigation skills
transferLearning	0.7	Apply accessibility patterns across sites that follow standards

Perception Traits (Tier 5)

Trait	Value	Rationale
changeBlindness	0.5	Rely on proper ARIA live regions; may miss unannounced changes
mentalModelRigidity	0.6	Expect accessibility standards to be followed

Social Traits (Tier 6)

Trait	Value	Rationale
authoritySensitivity	0.5	Moderate; evaluate based on accessibility experience
emotionalContagion	0.5	Moderate; visual emotional cues not available
fomo	0.4	Lower; focused on what's accessible rather than everything
socialProofSensitivity	0.5	Value accessibility reviews from other screen reader users

Behavioral Patterns

Navigation

Screen reader users navigate via keyboard using landmarks, headings, links, and form elements. They use skip links and rely on semantic HTML. Tab order must be logical. They often explore page structure first using heading navigation (H key) before reading content.

Decision Making

Decisions are based on text and announced information. Visual design cues are irrelevant. Proper labeling is essential for all interactive elements. Decisions may be slower but are often more informed.

Error Recovery

Error recovery requires clear, announced text feedback. Focus must move to the error message or affected field. Errors must not trap keyboard focus or create navigation dead-ends.

Abandonment Triggers

Inaccessible CAPTCHAs without alternatives
Unlabeled form fields
Focus traps in modals or custom widgets
Missing skip links on repetitive content
Images without alt text conveying essential information
Dynamic content that isn't announced
Keyboard-inaccessible interactions

UX Recommendations

Challenge	Recommendation
Sequential navigation	Proper heading hierarchy; skip links; landmark regions
Unlabeled controls	ARIA labels for all interactive elements; descriptive link text
Focus management	Logical tab order; focus management for dynamic content
Dynamic updates	ARIA live regions for status changes; announcements for loading
Time-limited content	Sufficient time; ability to extend; pause auto-updating content
Complex interactions	Keyboard accessibility; ARIA widgets following WAI-ARIA patterns
Form errors	Announce errors; move focus; clear error descriptions

Research Basis

WebAIM Screen Reader User Survey #10 (2024) - User preferences and behavior patterns
WCAG 2.2 Guidelines - Technical accessibility requirements
Lazar, J. et al. (2007). Frustration of blind users on the web - Empirical studies
Power, C. et al. (2012). Guidelines are only half the story - User experience research
Petrie, H. & Kheir, O. (2007). Relationship between accessibility and usability

Usage

await cognitive_journey_init({
  persona: "screen-reader-user",
  goal: "complete checkout",
  startUrl: "https://example.com"
});

npx cbrowser cognitive-journey --persona screen-reader-user --start https://example.com --goal "complete checkout"

Persona ScreenReaderUser