liveBook · Manning

Disability

As explained in Architecting Accessibility

A disability is a physical, sensory, cognitive, or other condition that can affect a person's ability to interact with technology.

Disability describes barriers that arise when physical environments or technologies do not accommodate a person’s differences. An impairment is a difference in the person; accessibility focuses on removing the barriers. section 2.1

Access needs may be permanent, temporary, or situational, and can involve vision, hearing, motor skills, speech, or cognition. People may also have co-occurring disabilities. section 2.1

A workflow that loses its way

Sam is recovering from a brain injury and finds complex, multi-step tasks overwhelming. Clear language, consistent layouts, and visible checkpoints help Sam stay on task. section 2.1

Table 2.1 Overview of user personas with visual access needs, the barriers they encounter, and the tools or strategies they use to access digital content.
Person
About
Challenges
Silvey
Silvey is a financial analyst with red-green color blindness (Deuteranomaly). When color alone signals errors or status updates, it's easy for Silvey to miss critical information - causing a fear of missing out (FOMO). Silvey uses browser extensions to adjust color palettes and relies on icons, text, and patterns alongside color in financial dashboards and reports.
Color blindness
Adrian
Adrian is a shop assistant with low vision due to cataracts. Adrian's vision is blurry, making it difficult to read small fonts or text with low contrast. System-wide font sizes and browser zoom levels are typically increased to improve readability. In turn, Adrian expects content to scale dynamically without breaking functionality or hiding important information. Responsive layouts and relative font sizes allow for content and interactive components to scale and reflow gracefully, keeping Adrian productive without getting lost.
Low-vision
Jess
Jess is a client success agent who is blind. She uses a screen reader and keyboard for all her tasks. Since Jess relies on a screen reader to understand pages and access content, proper semantic markup, minimized audio clutter, logical flows, and options to skip repeated content are very important. Poorly labeled elements and skipped heading levels make pages hard to understand. With solid HTML and logical workflows, Jess can confidently handle support tickets.
Blind

Explore visual-access personas to see how specific barriers shape the tools and strategies people use. section 2.1

How Architecting Accessibility covers it

How deep it goes
Distinguishes impairment from disability and identifies permanent, temporary, situational, and co-occurring access needs.
Examples
Uses Sam’s difficulty with complex workflows and visual-access personas’ barriers and strategies.
What you can do after
Evaluate technology by identifying barriers and considering how design decisions affect people’s interactions.
How it connects
Connects disability with impairment and access needs involving vision, hearing, motor skills, speech, and cognition.

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Architecting Accessibility. The section links point to the parts of the book it draws on.