Design Thinking and Accessibility: Empathy as a Design Driver

Design thinking — the iterative, human-centered methodology popularized by IDEO and Stanford’s d.school — has become one of the dominant design frameworks in business and technology. Its emphasis on empathy, experimentation, and iteration makes it a natural vehicle for universal design thinking, provided that empathy extends to the full range of human diversity.

Design Thinking’s Five Stages

Design thinking is typically described through five stages (though implementations vary):

1. Empathize: Understand users’ needs, experiences, and motivations through observation and engagement.
2. Define: Synthesize research into clear problem statements.
3. Ideate: Generate a wide range of potential solutions.
4. Prototype: Build tangible representations of solutions.
5. Test: Evaluate prototypes with users and refine.

Each stage has accessibility implications, and each becomes more powerful when informed by universal design principles.

Empathize: Expanding Who We Learn From

The empathy phase determines whose needs the design will address. If the research sample includes only non-disabled, young, tech-savvy users, the resulting design will serve that narrow population.

Inclusive empathy means:

• Recruiting research participants with diverse disabilities, ages, language backgrounds, and technology proficiency levels
• Engaging people with disabilities as experts on their own experience, not as research subjects to be observed
• Spending time in the environments where people with disabilities live and work, not only in controlled lab settings
• Recognizing the limits of simulation (wearing a blindfold for an hour does not replicate blindness)

Microsoft’s Inclusive Design practice has formalized this through their “learn from diversity” principle: design insights from people at the margins of ability reveal opportunities that benefit everyone. The Xbox Adaptive Controller — designed with and for gamers with limited mobility — emerged from this approach.

Define: Framing Problems Inclusively

How a problem is framed determines what solutions are considered:

Exclusive framing: “How might we design a checkout process for our core demographic?” This framing excludes anyone outside the assumed “core.”

Inclusive framing: “How might we design a checkout process that works for anyone, regardless of how they interact with technology?” This framing opens the solution space.

The W3C WAI recommends that accessibility be integrated into problem definition rather than added as a constraint later. When accessibility is a bolt-on requirement, it produces bolt-on solutions. When it is part of the problem definition, it produces integrated solutions.

Ideate: Generating Accessible Solutions

Ideation sessions benefit from accessibility thinking in several ways:

Constraint-driven creativity: Designing for specific constraints (one-handed use, no vision, limited cognition) generates creative solutions that often benefit all users. Voice interfaces, swipe gestures, and auto-complete all originated from accessibility needs.

“Solve for one, extend to many:” Microsoft’s inclusive design mantra. When you design for a person who cannot use their hands, you create solutions that also work for a person holding a coffee, wearing gloves, or driving.

Cross-pollination: Including team members with disability expertise (or better, team members with disabilities) in ideation sessions introduces perspectives that homogeneous teams miss. Deque and AbilityNet both advocate for disability-competent design teams.

Prototype: Building for Testing

Prototypes must be accessible enough to test with diverse users:

• Paper prototypes can be described verbally for blind testers
• Digital prototypes should support basic keyboard navigation and screen reader compatibility
• Physical prototypes should include tactile and spatial features for testing with mobility-impaired users
• Multiple fidelity levels allow testing different aspects with different user groups

The key principle: if your prototype cannot be used by the people you need feedback from, your testing is invalid.

Test: Diverse Evaluation

Testing with diverse users is where inclusive design thinking produces its greatest dividends:

• Include participants who use screen readers, switch access, voice control, and other assistive technologies
• Test in realistic environments (noisy, bright, distracting) not only controlled labs
• Measure both task performance and subjective experience
• Look for disparities between user groups, not just aggregate success rates

For detailed research methodology, see universal design research methods.

Common Failures

Empathy without inclusion: Design thinking workshops that use empathy exercises (blindfold simulations, wheelchair rides) without ever involving actual disabled users produce superficial understanding and often inaccurate insights.

“Edge case” dismissal: Labeling disabled users as “edge cases” gives permission to ignore them. When 16% of the population has a disability, plus aging populations and temporary conditions, “edge cases” collectively form the majority.

Post-hoc accessibility: Running the full design thinking process and then “checking” accessibility at the end. By that point, fundamental design decisions have been made, and remediation is expensive and incomplete.

Homogeneous teams: Design thinking teams composed entirely of non-disabled, young, tech-fluent members will have blind spots regardless of their empathy efforts.

Integrating Design Thinking with Universal Design

The integration is straightforward: run the design thinking process with universal design principles as a persistent lens. At every stage, ask:

• Are we empathizing with the full range of human diversity?
• Is our problem definition inclusive?
• Do our ideas serve the widest possible audience?
• Can our prototypes be tested by diverse users?
• Does our testing reveal equity gaps?

For the principles that should guide this process, see our seven principles overview. For how this compares to other approaches, see user-centered vs. universal design.

Key Takeaways

• Design thinking’s five stages (empathize, define, ideate, prototype, test) each become more powerful when informed by universal design principles.
• The empathy phase determines whose needs the design addresses — inclusive recruitment is essential.
• Problem framing that includes accessibility from the start produces integrated solutions; bolt-on framing produces bolt-on results.
• Testing with diverse users reveals equity gaps that aggregate metrics hide.

Sources

• W3C WAI — Involving Users in Evaluating Web Accessibility: https://www.w3.org/WAI/test-evaluate/involving-users/
• W3C WAI — Planning and Managing: https://www.w3.org/WAI/planning-and-managing/
• Centre for Excellence in Universal Design — Design Process: https://universaldesign.ie/what-is-universal-design
• W3C — WCAG 2.2: https://www.w3.org/TR/WCAG22/