The situational, temporary, and permanent spectrum

What it is

A parent holding a baby in one arm, a person with a broken arm in a cast, and a person with a congenital single-arm limb difference are in an identical position with respect to one fact: they can only use one hand to operate a phone. This is what's meant by situational impairment — the functional limit is set by whether a given input channel is available right now, not by a diagnostic label. Situational, temporary, and permanent impairment are not three unrelated user groups; they are the same constraint sitting at three different points on a duration axis: permanent (lifelong), temporary (weeks to months, e.g. recovering from a fracture), and situational (seconds to hours, often recurring, e.g. hands full while doing chores). All three share the identical functional consequence; what differs is how long that consequence lasts and whether the person has already built compensating strategies around it.

Why it happens

When an interface executes an interaction, what it can actually detect is which channel is available right now — how many fingers are free, whether audio feedback can be heard, whether the eyes can stay fixed on the screen, whether fine motor control is steady — never why that channel is unavailable, whether from birth, injury, or context. This means any functional bottleneck an interface has to handle — one hand only, no sound, can't sustain visual attention, unsteady fine motor control — can be triggered by any point on the spectrum, and the interface has to address the bottleneck itself, not its cause. This mechanism leads to a counterintuitive conclusion: user models cannot treat "able-bodied" and "disabled" as two mutually exclusive categories, because nearly every user will, repeatedly and briefly, slide into some point on this spectrum over a lifetime (carrying luggage, standing in a noisy train car, holding a rail with one hand) — almost no one sits permanently off the spectrum entirely. The correct modeling variable is "which channels are available right now," not "which category this person belongs to."

Studying it

• Paradigm: a common approach artificially restricts an able-bodied participant's channel to simulate situational impairment — immobilizing one hand, wearing blurring lenses, walking on a treadmill while operating a device, running a voice task against background white noise — then observing task completion time, error rate, and abandonment.
• Variables: the independent variable is which channel is restricted and to what degree; the dependent variables are typically completion time, error count, and subjective workload.
• Use in interface research: this method is used before formal accessibility testing, as a cheap way to expose which interaction steps depend too heavily on a single channel.
• Methodological caveat: simulated restriction is not the same as real permanent impairment — an able-bodied participant briefly wearing blurring lenses knows it's "just a test" and has none of the compensatory skill built up over years (e.g. a blind user's fluency with screen-reader gestures), so simulation data tends to read worse than real permanent users' actual performance and worse than real situational users' adaptive capacity. It should never be treated as a performance baseline for any real population on the spectrum — only as a rough screen for "does a bottleneck exist here."

Where it stops holding

The three points on the spectrum are equivalent at the level of functional consequence, but not along two other dimensions. First, compensatory experience: permanent-impairment users have typically built mature alternative operating paths and muscle memory, while situationally impaired users are suddenly and briefly constrained without training, so even an identical functional bottleneck can produce different actual efficiency. Second, predictability: permanent and most temporary states are known before a task begins, while situational states often appear or disappear mid-task (a hand frees up halfway through typing to answer a call), which changes how far ahead a design can adapt. The spectrum also only covers "channel unavailability" — it doesn't explain every kind of individual difference; comprehension difficulty from language or cultural background falls outside this frame.

Applying it

• In user research and requirements work, record "which channel is unavailable right now, and for how long" instead of "is this user disabled" — list permanent, temporary, and situational triggers side by side in the same requirements document rather than picking one;
• Audit existing personas or requirement docs: wherever a diagnostic label ("visually impaired user," "older user") is used to describe a need, rewrite it as a functional description ("cannot rely on color alone to distinguish state," "cannot keep visual attention fixed on the screen while operating it") — a functional description covers the whole spectrum, a diagnostic label covers only one point on it;
• Which specific accessibility techniques to implement is an execution-layer question outside the scope of this entry;
• Verification: sample the team's requirements docs or bug reports and count what fraction describe user needs with a diagnostic label rather than a functional one — a high fraction signals the team is still modeling users as a binary category.

Related

• Same group: A11.08.2 one-handed contexts: holding, carrying, gripping · A11.08.6 situational accommodations can reuse permanent-disability solutions
• Nearby: A8.15 physiological tremor · A8.16 pathological and intention tremor
• Search terms: situational impairment · persona spectrum · curb-cut effect