How Does Disability Simulator Simulate Different Disabilities?

Disability Simulator simulates disabilities by turning each condition into a hands-on web browsing task rather than a written description. Instead of reading about screen reader navigation or tremor, you try to complete a normal web action under that constraint. The site organizes these into three live categories — Visual Impairments, Motor Impairments, and Cognitive Impairments — with six more listed as "Coming Soon." It is built for anyone who wants to feel where web barriers actually come from: designers, developers, QA testers, content authors, and educators.

Visual Impairments

The visual simulations recreate how information is received, not just how it looks.

• Blindness — screen reader navigation. You navigate a page through a screen reader, so the experience depends on whether content is structured and labeled properly. Headings, link text, and image alt text decide whether you can find anything; unlabeled controls or vague "click here" links become dead ends.
• Low Vision — blurred and limited vision. The page is rendered with reduced clarity and field of view, so you experience why large text, strong contrast, and generous spacing matter for readability.
• Color Blindness — color perception differences. Colors shift to mimic different types of color vision deficiency, exposing interfaces that rely on color alone — for example, a red/green status indicator or a link distinguished only by hue.

The common thread: each one blocks a different channel (structure, clarity, or color), and each maps to a specific fix such as semantic HTML, contrast ratios, or redundant cues like icons and text labels.

Motor Impairments

Motor simulations change how you operate the page, which is a different kind of barrier from not being able to see it.

• Keyboard Only — navigation without a mouse. You complete tasks using only the keyboard, which reveals focus order problems, missing focus indicators, and controls that simply can't be reached without a pointer.
• Limited Control. Interaction is constrained, so small click targets, tightly packed links, and hover-only menus become hard or impossible to use.
• Tremor and precision challenges. Fine motor movement is simulated, showing why precise clicking, drag-and-drop, and time-limited interactions exclude users with tremors.

These simulations make the case for large touch targets, visible focus states, full keyboard operability, and avoiding interactions that demand steadiness or speed.

Cognitive Impairments

Cognitive simulations target how text and attention are processed.

• Dyslexia — reading and text processing. Text is presented in a way that mimics reading difficulty, highlighting why plain language, short sentences, clear fonts, and uncluttered layouts reduce cognitive load.
• ADHD — attention and focus challenges. The simulation stresses focus and distraction, showing how autoplay media, dense navigation, and competing calls to action make it hard to stay on task.

The takeaway here is that cognitive barriers are often about design discipline — structure, brevity, and removing noise — rather than any single technical attribute.

What Each Simulation Is Really Testing

Every simulation converts an abstract guideline into a concrete failure you can observe:

Coming Soon Simulations

The site lists several categories as not yet available: Hearing Impairments (deaf and hard of hearing experiences), Seizure Disorders (photosensitive epilepsy triggers), Autism Spectrum (sensory processing differences), Memory Impairments (short-term memory challenges), Aging-Related needs, and Multiple Disabilities (combined challenges). Treat these as planned coverage, not current features — check the site for their status before relying on them.

How to Use the Simulations Effectively

1. Pick a simulation and a real task — for example, "find the contact form" or "complete a checkout."
2. Attempt the task under the constraint without switching back to your normal mode.
3. Note exactly where you got stuck — the specific element, label, or interaction that failed.
4. Map the failure to a fix (alt text, focus order, contrast, larger targets, simpler copy).
5. Re-test after changes to confirm the barrier is gone.

The value isn't in any single simulation but in the pattern: each one shows that accessibility barriers are usually created by ordinary design and markup decisions, and are therefore fixable by ordinary decisions too.