Menu

Accessibility

Inclusive Usability Testing

A practical UX method for evaluating usability across diverse abilities, contexts, and user backgrounds to reduce exclusion.

How to run inclusive usability testing to identify barriers and improve equitable usability for a broad audience.

4 min read

What it is

Inclusive is a UX method that evaluates how well a product works for a diverse range of users, including people with disabilities, older adults, and those with different cultural or technological backgrounds.

It combines standard with considerations to ensure the experience is usable, understandable, and engaging for all users.

Participants are selected to represent a variety of abilities, devices, and , and tasks are observed to identify barriers or points.

The focus is on removing exclusion and ensuring equitable access to the product.

The goal is to make the product usable and enjoyable for the widest possible audience.

Inclusive usability testing improves products by reflecting real user diversity rather than an average user assumption.

When to use it

Use this method when inclusivity matters.

It is most useful when:

you are designing for a broad and diverse audience
accessibility and usability must go hand-in-hand
you want to identify barriers for underrepresented groups
you are preparing for public-facing products
you want to reduce exclusion and frustration

It is less useful when:

the product is highly specialised for a narrow audience
you are still exploring very early concepts
Inclusive usability testing is often used alongside accessibility audits and standard usability testing.

Key takeaway

Use this method when you need confidence that key journeys work for different people, not just typical users.

How to run it

Set up properly

Decide what range of participants you need before you write the tasks. Inclusive testing means recruiting for the range of ability, and circumstance your product actually meets, not adding one participant at the end.

Plan the accommodations in advance: assistive technology, extra time, breaks, a support person, materials in another format. Asking on the day means someone will decline rather than explain.

Run the method

Inclusive is structured and observational. It is ordinary with the and the logistics taken seriously.

  1. Give tasks that reflect real use, and let people use their own devices and settings wherever possible. Their setup is part of what you are testing.
  2. Observe people completing tasks without stepping in. The instinct to help is strongest exactly where the finding is.
  3. Note barriers, errors and frustration, and separate the ones caused by your product from the ones caused by their tools.
  4. Make sure accommodations are actually available and working before the , not offered during it.
  5. Ask about inclusivity and directly at the end. People will often name something they worked around without mentioning it at the time.

Focus on how different people experience the product, not on averaging them. The average user is the one person you will never meet.

Capture and make sense of it

The value comes from understanding a range of experiences. After testing, document:

  • grouped by participant rather than by task
  • of exclusion or difficulty, and who they affected
  • Critical issues that stopped someone completing at all
  • Recommendations that fix the barrier rather than adding a workaround

Use this to make decisions that work for everyone. Findings from the edges of your audience almost always improve the middle of it too.

What to look for

Focus on:

Usability: can all users complete tasks effectively
Accessibility: are assistive technologies supported
Comprehension: do instructions and content make sense for everyone
Friction: where users struggle or get stuck
Inclusion: whether the product feels equitable and usable

Where it goes wrong

Most issues come from:

If only a subset of users is considered, the test is incomplete.

Recruiting the same participants as always and calling the study inclusive
Excluding assistive technology users because the session setup is harder
Testing in conditions nobody actually uses the product in
Designing for a range of people you have imagined rather than met
Collecting findings about exclusion and shipping anyway

What you get from it

Done properly, this method gives you:

Evidence about how people at the edges of your audience actually cope
The specific points where the product excludes somebody
Fixes that remove the barrier rather than adding a workaround
Improvements that usually help the middle of your audience too

Key takeaway

It helps you build experiences that everyone can use and enjoy.

Get in touch

If this sounds like something you need, we can help you run inclusive usability tests and identify barriers that may prevent users from completing tasks or enjoying your product.

No guesswork. No assumptions. Just design that works for all.

FAQ

Common questions

A few practical answers to the questions that usually come up around this method.

What is inclusive usability testing in UX?

It is usability testing that evaluates the product across a diverse set of users, including those with disabilities or different needs.

When should you use inclusive usability testing?

During usability testing phases, especially for public-facing products.

Who should participate?

Users representing a variety of abilities, devices, and contexts.

How is it different from standard usability testing?

It specifically focuses on inclusivity and accessibility.

Does inclusive usability testing improve UX?

Yes. It ensures your product works for everyone, not just the typical user.

Quick take

If your product is for everyone, test it with everyone.

LET'S WORK TOGETHER

Ready to improve your product?

UX, research and product leadership for teams tackling complex digital services.

Previous feedback

I had a fantastic experience working with Andy. One of his most impressive achievements during our time at NHS HEE was masterminding a deeply complex information architecture for a new platform that brought together a large number of legacy websites.

Will Parkhouse

Senior Content Designer