Website review
This review may include AI-generated content and is not individually verified. Domain, certificate and other facts come from the observed data on this page.
What is Disability Simulator?
Disability Simulator is a browser-based tool that lets you experience some of the barriers disabled users encounter on websites. Its tagline — "See through disabled people eyes" — frames the goal as empathy through direct experience rather than explanation. Instead of reading about screen-reader navigation or tremor-related clicking difficulty, you try tasks under those constraints yourself.
What it covers
The site organises simulations by impairment type:
- Visual — blindness (screen reader navigation), low vision (blurred and limited vision), colour blindness (altered colour perception)
- Motor — keyboard-only navigation, limited control, tremor and precision challenges
- Cognitive — dyslexia (reading and text processing), ADHD (attention and focus)
Additional categories are listed as coming soon: hearing impairments, seizure disorders, autism spectrum, memory impairments, aging-related needs, and combined multiple disabilities.
Who it is for
Designers, developers, QA testers and product managers get the most value. A concrete scenario: before a sprint review, a designer runs the keyboard-only simulation on their own checkout flow and discovers the "Apply discount" button is unreachable without a mouse. That finding is more persuasive to a team than a checklist item, because the person who built the screen felt the failure themselves.
Educators and students can also use it to make accessibility coursework tangible.
Trade-offs to keep in mind
Simulations approximate a single dimension of an impairment at a moment in time. A screen-reader simulation does not reproduce the skill and speed of an experienced screen-reader user, and a blur filter is not the same as real low vision, which varies by condition, lighting and fatigue. Treat these exercises as a starting point for empathy and bug-finding, not as a substitute for testing with disabled users or for automated and manual accessibility audits.
Next step
Open the site, pick the simulation closest to your product's risk area — for most web apps that is keyboard-only or screen reader — and run it against a page you already know well. Note where you get stuck, then check those spots against the relevant WCAG success criteria before filing fixes. For broader guidance on the standards behind these barriers, see W3C Web Accessibility Initiative.
How can I test my website for accessibility issues using Disability Simulator?
Disability Simulator is a set of interactive exercises that let you experience common web barriers firsthand, so you can spot problems in your own site more quickly. It is best used as a diagnostic warm-up and empathy tool, not as a replacement for formal accessibility testing.
How to use it as a practical test
- Pick a simulation that matches a real user need. The site currently offers simulations for visual impairments (blindness/screen reader navigation, low vision, color blindness), motor impairments (keyboard-only navigation, limited control, tremor), and cognitive impairments (dyslexia, ADHD).
- Recreate the task in your own site. While the simulation is active, try a core journey: sign up, search, checkout, submit a form. Note where you get stuck.
- Record the barrier, not just the feeling. "I couldn't tell which field had focus" is actionable; "this was hard" is not.
- Fix and retest. Use the simulation again after changes to confirm the specific barrier is gone.
What each simulation is good for
| Simulation | Typical issue it exposes | Useful for |
|---|---|---|
| Screen reader navigation | Missing headings, unlabeled buttons, poor reading order | Content pages, forms, navigation |
| Low vision / blurred vision | Small text, low contrast, layouts that break when zoomed | Marketing pages, dashboards |
| Color blindness | Status conveyed only by color, e.g. red/green errors | Forms, charts, alerts |
| Keyboard only | Focus traps, invisible focus outlines, mouse-only menus | Menus, modals, checkout flows |
| Limited control / tremor | Tiny tap targets, hover-only interactions | Mobile layouts, buttons |
| Dyslexia | Dense paragraphs, justified text, poor line spacing | Long-form content, help pages |
| ADHD | Distracting animation, cluttered layouts, unclear next steps | Onboarding, landing pages |
Important limits
These simulations approximate an experience; they do not verify conformance with accessibility standards. A simulator cannot tell you whether your markup is correct, whether a screen reader announces your custom widget properly, or whether a real user with a specific combination of assistive technology and browser can complete a task. Treat every finding as a hypothesis to verify with real testing.
A sensible next step
Run a keyboard-only pass on your most important page today: unplug or ignore the mouse, press Tab from the top, and try to complete one task. Then compare your findings with the simulation. For standards-based checks, pair this with established guidance from W3C Web Accessibility Initiative and, if you use component libraries, the relevant patterns in WAI-ARIA Authoring Practices. If you want structured manual test scripts, WebAIM publishes practical checklists, and for automated scanning alongside manual testing, Deque documents common rule sets.
Choose Disability Simulator when you need fast, memorable insight for a team or stakeholder; choose formal audits and real-user testing when you need defensible compliance evidence.
What types of disabilities can I simulate with Disability Simulator?
Disability Simulator focuses on web accessibility scenarios. Based on its listed simulations, you can try these categories:
- Visual impairments — blindness (screen reader navigation), low vision (blurred and limited vision), and color blindness (color perception differences).
- Motor impairments — keyboard-only navigation without a mouse, plus limited control such as tremor and precision challenges.
- Cognitive impairments — dyslexia (reading and text processing) and ADHD (attention and focus).
- Coming soon — hearing impairments, seizure disorders (photosensitive epilepsy triggers), autism spectrum (sensory processing), memory impairments, aging-related needs, and multiple disabilities.
How to choose one
Pick the simulation that matches a real user constraint in your product. If your interface depends on drag-and-drop or hover menus, start with keyboard-only and tremor simulations. If content is dense, try dyslexia and ADHD. If color carries meaning in charts or status badges, run color blindness first.
A practical next step: open your own site in one simulation at a time and note where you get stuck, then check whether that barrier is a design decision or a missing alternative. For broader guidance on accessible patterns, see W3C Web Accessibility Initiative.
Is Disability Simulator free to use?
Disability Simulator does not advertise a price, subscription or payment option on its page, and it presents its content as interactive simulations you can run in the browser. On that evidence, it reads as a free-to-try educational site rather than a paid product — but treat that as an observation about the page, not a formal "free forever" guarantee, since nothing on it states licensing or usage terms.
What you can actually try
The page lists these simulations as available:
- Visual impairments — blindness with screen reader navigation; low vision with blurred and limited vision; colour blindness
- Motor impairments — keyboard-only navigation and limited control, including tremor and precision challenges
- Cognitive impairments — dyslexia (reading and text processing) and ADHD (attention and focus)
Further categories — hearing impairments, seizure disorders, autism spectrum, memory impairments, aging-related needs and combined multiple disabilities — are marked "Coming Soon", so don't plan training around them yet.
A practical way to use it
Pick one simulation that matches a real complaint about your own site. If your analytics or support tickets show people abandoning a form, run the keyboard-only or tremor simulation and try completing that form yourself. Note where you get stuck, then fix that specific barrier rather than treating the exercise as general awareness training.
If you need a broader, standards-based view of the same issues, compare with W3C Web Accessibility Initiative guidance on WCAG, or run an automated audit alongside it — simulations build empathy, while audits and assistive-technology testing catch the concrete failures.
How do the simulations in Disability Simulator help me improve web accessibility?
They help most directly by making a barrier concrete: you try to complete a task under a constraint, and you feel where your interface breaks down. Disability Simulator groups its exercises by impairment type, so you can target the part of your design you are least sure about.
What the simulations cover
The site lists available simulations for:
- Visual impairments — blindness and screen reader navigation, low vision with blurred or limited vision, and color blindness.
- Motor impairments — keyboard-only navigation without a mouse, plus limited control and tremor/precision challenges.
- Cognitive impairments — dyslexia (reading and text processing) and ADHD (attention and focus).
Hearing, seizure, autism, memory, aging-related and multiple-disability simulations are marked "Coming Soon," so don't plan a review around those yet.
How to turn a simulation into an actual fix
A simulation is a prompt, not a test result. Use it to generate specific questions, then verify against real assistive technology and, ideally, people with disabilities.
| Simulation | What it exposes | Practical follow-up |
|---|---|---|
| Screen reader navigation | Whether structure survives without visuals | Check heading order, link text, form labels, alt text |
| Keyboard only | Whether everything is reachable and operable | Tab through each flow; check focus visibility and order |
| Low vision / blurred | Whether content survives zoom and poor contrast | Test zoom, text resizing, contrast ratios |
| Color blindness | Whether color alone carries meaning | Add text, icons or patterns to status and errors |
| Dyslexia / ADHD | Whether reading and focus are overloaded | Shorten lines, simplify copy, reduce distraction |
A concrete scenario
If you run the keyboard-only simulation on your signup form, you may find the submit button is unreachable or the focus ring disappears against the background. That is a fixable defect, not a vague concern. The simulation gives you the experience; your audit checklist and code review give you the remedy.
Next step
Pick the one simulation matching your riskiest flow — usually keyboard-only or screen reader navigation for a transactional page — run it yourself, and log every point where you get stuck. Treat that list as your first accessibility backlog. For authoritative guidance on the underlying standards, see W3C Web Accessibility Initiative and WebAIM.
Can I simulate multiple disabilities at once in Disability Simulator?
Not currently. The site lists "Multiple Disabilities — Combined accessibility challenges" under its Coming Soon section, so simulating several disabilities at once is planned rather than available now. Today's simulations are single-category experiences: visual impairments (blindness, low vision, color blindness), motor impairments (keyboard-only navigation, limited control, tremor), and cognitive impairments (dyslexia, ADHD). Hearing, seizure, autism, memory, and aging-related simulations are also marked coming soon.
What you can do meanwhile: run each simulation separately on the same page and note where barriers overlap. For example, test keyboard-only navigation first, then a low-vision or blurred-vision simulation on the same flow — a form that fails both is a stronger accessibility signal than either failure alone.
For combined testing now, dedicated tools are more practical: screen readers such as NVDA paired with keyboard-only browsing, or browser-based checks like WAVE and Deque's accessibility tools. These complement, rather than replace, the empathy-focused approach Disability Simulator takes.
User reviews (0)