Involving people of determination in accessibility work

A conformance audit tells you a control has no accessible name. It does not tell you that the person gave up two screens earlier, or that they got through by a route nobody designed.

Involving people of determination is how you learn the second thing. It does not replace specialist evaluation, and it is not a substitute for conformance — but it answers a question testing alone cannot.

Decide what you need to learn

Start with a question narrow enough to answer in a session. Can someone complete an application? Find the information that decides whether they are eligible? Recover after an error?

Then choose participants whose experience is relevant to that question — considering language, devices, assistive technology and how familiar the task is. Respect the terminology people use about themselves, and remember that one person’s experience is evidence, not a verdict.

Make taking part possible

The session has to be accessible before it can tell you anything about accessibility:

• Ask about access needs and how someone prefers to take part.
• Share materials in advance, in a format they can use, and allow time for breaks.
• Agree payment, and be clear about how observations or recordings will be used.
• Let people use their own devices and assistive technology wherever the study allows.

In the session, give people room to work. Watch where they pause, where they look for help, and where they take a route you did not expect — and ask questions without steering them towards the answer you were hoping for.

Design the session around a real task

Say a team wants to understand an online appointment journey. The question might be whether someone can find a suitable slot, give the information required, and understand the confirmation. Give a realistic goal and let the participant choose how to reach it.

Plan for the service failing. If a barrier stops progress, you need a way to continue — nobody should be left struggling to produce a finding. Agree in advance how the facilitator can help, and record when that help was needed, because that is data too.

Keep three things separate when you write it up:

• What happened.
• What the participant said, in their own words and with their agreement.
• What the team thinks explains it.

They are related and they are not the same, and conflating them is how a session becomes an opinion.

Turn it into a change, and close the loop

Bring the evidence to the people who can act on it. A finding should name the task and context, explain the barrier, and show why it matters. Specialist evaluation is what connects the observed experience to the specific design or implementation change — and to the applicable WCAG, document or software requirement. اقرأ كيف تجمع أكسس أول بين هذه المنهجيات.

Prioritise on the effect on people and the reach of the component, not on how easy something is to fix. Agree how each change will be checked, revisit the journeys that matter, and be explicit about what the study cannot establish: participation explains barriers, it does not establish conformance.

Then go back to the participants in the way you agreed. Their time produced the finding; they should know what it changed.