How to recruit research participants with accessibility needs, starting with the invite

Recruiting research participants with accessibility needs goes wrong at the invitation, long before the interview. People have to read the invite, reply, pick a time, understand the activity and join the session. If one of those steps is inaccessible, support offered at the session arrives too late for anyone who gave up earlier.

So ask about practical participation needs and preferred formats, then turn each answer into an arrangement with an owner and a confirmation step. "We can accommodate accessibility needs" is a promise. "We will send the materials as structured text, and Alex will confirm the call setup works for you" is a plan.

1. Recruit for the experience, then plan the access

Define the experience you need first, such as people who schedule work for a team. That group includes disabled people and people who use assistive technology, and their evidence matters beyond accessibility features. A screen-reader user who schedules work knows about staffing decisions, approvals and workarounds, as well as interaction barriers.

GOV.UK's participant guidance includes disabled people among actual and potential users. It asks researchers to establish each person's communication, technology, material-format and travel needs. These are practical recruitment questions, not a request to infer needs from a diagnosis.

Ask a functional question: "What would help you take part in the session comfortably, including communication, materials, equipment, timing, or breaks?" Make it possible to answer through a suitable channel. Nobody should have to describe a medical history to get a usable document.

2. Walk the whole recruitment path yourself

Go through the real invitation, screener, booking page, confirmation and joining instructions. Wherever a step requires one mode of interaction, provide a route around it.

For a small team, an alternative contact option stops the booking form from being the only way in. Someone has to monitor it, though. A listed email address that nobody answers is still a barrier.

Say what participation involves: a conversation, a screen-based task, reading, writing or moving between locations, and whether observers attend. People can only help choose a format if they know the activity.

Keep the access check light. A long mandatory questionnaire collects details your team never uses.

3. Give every arrangement an owner

This planner is our own aid. Adapt the rows to the activity; they are not questions every participant must answer.

If the session evaluates a prototype, keep access to the session separate from accessibility of the prototype. A checked joining setup says nothing about whether the interface under study works.

Record the arrangement in the schedule, and share sensitive detail only with people who need it. A moderator may need to know "pause after each task" without hearing an unrelated account of someone's health.

4. A worked example: an adapted format changes what you can conclude

Here is a made-up example. A team is interviewing shift coordinators about handling schedule changes. One participant uses screen magnification and asks for materials in advance. Another prefers a phone conversation with written follow-up, because the proposed video setup is difficult for them. These are individual preferences, not rules about groups of people.

The first session includes reading a sample schedule. The researcher sends a structured text version in advance, checks with the participant that it is usable, and checks the task still makes sense. The note-taker records which version was used, so nobody later claims the team tested the original visual layout.

The second participant can discuss a recent scheduling incident by phone. If the study also needs to observe an interface task, the team needs a separate arrangement, or must say plainly that the question is unanswered. Changing the format keeps the person in the study, and it also changes what the method can establish. Write that down.

5. Let the participant's own setup shape the session

GOV.UK's guidance for sessions with disabled people notes that personalized assistive-technology settings can be difficult to reproduce on another device. It also advises addressing the participant directly and asking before offering help.

Schedule setup and breaks on top of the research time. If an interpreter or support person attends, agree roles in advance, keep directing questions to the participant, and note when someone else answers.

If the agreed technology fails, use the fallback you discussed or reschedule. Do not pressure someone to continue in a format that stops them taking part meaningfully. Log the setup failure separately from observations about the product.

6. Don't turn one participant into a spokesperson

Ask people about their own experience, not on behalf of everyone who shares a disability label. W3C warns against generalizing a small number of disabled users' experiences to all disabled people. For web accessibility evaluation, it recommends combining user involvement with standards-based evaluation, because user sessions alone do not establish conformance.

For a workflow interview, the matching habit is to report the participant context, the format used, the arrangements made and the limits of what you observed. Don't write "accessible for everyone" because one adapted session went well.

Finish with confirmed arrangements, not bookings

Your session list should show who owns each participant's materials, communication support, technology check and fallback. A booking means someone said yes. A confirmed arrangement means they can take part.