Why Use Disability Simulator? A Practical Guide to Its Purpose and Simulations

Disability Simulator (disabilitysimulator.com) is a free-to-access web tool that lets you experience web accessibility challenges firsthand through interactive simulations. You'd use it if you want to understand how people with disabilities navigate the web, build empathy for those users, or make a case for accessible design on your own site. It's aimed at designers, developers, content creators, and anyone who wants to see barriers from the user's side rather than just read about them.

What Disability Simulator Is

The site's premise is stated directly in its heading: "See through disabled people eyes." It offers interactive simulations that help you understand how people with disabilities experience the web.

The homepage frames the stakes with three figures:

These numbers set up the core argument: accessibility barriers are near-universal across the web, the affected population is enormous, and it represents significant spending power. The simulator exists to make that abstract gap concrete.

Why Use It

The purpose is experiential rather than informational. Instead of reading a checklist of WCAG rules, you run a simulation and feel where a task breaks down. That serves four practical goals:

• Experience challenges firsthand — you hit the same friction a disabled user hits, in real time.
• Build empathy — understanding shifts from "I know this is hard" to "I felt this was hard."
• Understand why accessible design matters — barriers become a design problem you can see, not an abstract compliance requirement.
• See how barriers affect user experience — you can trace a specific failure (unreadable text, an unreachable button) back to a design decision.

If you're trying to convince a team or client to invest in accessibility, running a simulation together is often more persuasive than citing guidelines.

Available Simulations

The site groups simulations by impairment type. Currently available:

Visual Impairments

• Blindness — screen reader navigation
• Low Vision — blurred and limited vision
• Color Blindness — color perception differences

Motor Impairments

• Keyboard Only — navigation without a mouse
• Limited Control — tremor and precision challenges

Cognitive Impairments

• Dyslexia — reading and text processing
• ADHD — attention and focus challenges

Coming Soon

The site lists these as planned, 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 — age-related accessibility needs
• Multiple Disabilities — combined accessibility challenges

If you need to simulate hearing, seizure, autism, memory, aging, or combined disabilities today, this tool doesn't cover them yet.

How to Get Value From It

1. Pick a simulation that matches your audience or your site's weak points. If your product relies on mouse interaction, start with Keyboard Only.
2. Attempt a real task, not a demo. Try to complete something you'd actually ask a user to do — fill a form, find a product, read an article.
3. Note where you get stuck. The specific failure points are your accessibility backlog.
4. Repeat with a different simulation. A site that works for low vision may still fail keyboard-only users.

The tool is a starting point for awareness and prioritization, not an audit. It won't tell you which WCAG criteria you violate — it shows you the experience those violations create.