Protocol

Include the people whose access needs your tests miss

An accessibility score is not a person completing the task.

About 1 min read

Before you use it

Use when
  • An interface passes automated checks but some people still cannot use it.

Keep this limit in mind

  • Do not ask people to simulate a disability as a replacement for involving users. Participation must be accessible and voluntary.

An idea to explore.

Try this idea.

Inspect the example, try the idea in your situation, then check your next move.

Keep reading

Why it matters

Include participants with relevant disabilities and assistive technologies in realistic task evaluation. Ask about their usual setup and access needs before the session. Combine their findings with standards-based checks instead of making either stand for the other.

Steps

  1. Recruit across the relevant needs rather than treating one participant as representative of everyone.
  2. Support the participant’s familiar tools and agreed accommodations.
  3. Record barriers, successful workarounds and untested combinations explicitly.

An example

A keyboard check passes, but a screen-reader user cannot tell whether a recording has finished processing.

Check your result

Can the team connect each finding to a task, setup and observed barrier, while stating what was not tested?

Save and practise this idea

My learning

Read. Recall. Repeat.

Save this idea and return to it on any device.

Use email
Keep exploring

Connected ideas

You are readingInclude the people whose access needs your tests miss

Evidence and sources
Supports

W3C recommends involving users with disabilities alongside standards-based accessibility evaluation.

Neither a small user sample nor an automated scan certifies complete accessibility.

Involving Users in Evaluating Web Accessibility · Combining user involvement with conformance evaluation.

All sources (1)
Edition and review

Version 0.1.0

No review details are supplied for this edition.

Read this idea as JSON · Release details