Why temporary impairments matter to your product
Permanent disability statistics tell one story. Add temporary impairments and the audience for accessibility quietly widens to almost everyone, at least sometimes. A user who broke their dominant arm needs one-handed operation for six weeks. A user with a migraine needs reduced motion and quiet contrast for the day. A user recovering from surgery may need extra-large text for a fortnight.
Common temporary impairments and what they need
- Arm or hand injury.
One-handed operation, larger tap targets, voice input, keyboard alternatives to mouse drag.
- Eye drops or post-surgical vision.
Larger text, higher contrast, screen reader support during recovery.
- Migraine, concussion, or fatigue.
Reduced motion, dark mode, quiet colour, longer timeouts, simpler interactions.
- Voice loss (laryngitis).
Text-based contact channels, captions instead of voice, no compulsory phone-only steps.
- Hearing loss (e.g. ear infection).
Captions on video, transcript options, visual notifications.
Design that helps
There is no separate playbook. The same accessibility patterns that help permanently disabled users help temporarily impaired users: keyboard access, screen reader support, captions, reduced motion options, generous touch targets, patient timeouts, plain language. The investment in WCAG conformance returns value to every customer, every time something goes wrong in their day.
Who else this helps
Anyone holding a baby or a coffee. Anyone walking. Anyone with a dirty screen. Anyone outdoors in bright sun. Anyone on a slow connection. Temporary impairment is one end of a spectrum that runs through situational limitations and into the everyday inconveniences of being human.
Where this fits in WCAG
Most WCAG 2.2 AA criteria apply: 2.1 Keyboard Accessible, 2.5 Input Modalities, 1.4 Distinguishable, 2.3.3 Animation from Interactions. Designing for temporary impairment is, in practice, designing to WCAG.