How to recruit research participants with accessibility needs

Accessible research recruitment starts before the interview. People need to be able to read the invitation, respond, choose a time, understand the activity, and join the session. Offering support only after someone has navigated an inaccessible booking process leaves a gap at the beginning.

Ask about practical participation needs and preferred formats. Then turn the answer into an arrangement with an owner and a confirmation step. “We can accommodate accessibility needs” is less useful than “We will send the materials as structured text, and Alex will confirm that the chosen call setup works for you.”

Keep experience criteria and access arrangements separate

First define the experience you need to understand: for example, people who schedule work for a team. Then consider the range of people who perform that activity, including disabled people and those using assistive technology.

Do not assume disability is relevant only when evaluating an accessibility feature. A screen-reader user who schedules work may have important evidence about staffing decisions, approvals, and workarounds as well as interaction barriers.

GOV.UK’s participant guidance includes disabled people among actual and potential users and asks researchers to establish individual communication, technology, material-format, and travel needs. These are practical recruitment considerations, not a request to infer needs from a diagnosis. Read the participant recruitment guidance.

Use a functional question such as: “What would help you take part in the session comfortably, including communication, materials, equipment, timing, or breaks?” Make it possible to discuss the answer through an appropriate channel. People should not have to describe a medical history to request a usable document.

Audit the whole recruitment path

Walk through the path using the actual invitation, screener, booking page, confirmation, and joining instructions. If any step requires a particular mode of interaction, provide a workable route around it.

For a small team, an alternative contact option can prevent the booking form from becoming the only doorway. But someone must monitor that option. A listed email address that goes unanswered does not solve the barrier.

Check whether the invitation describes what participation involves. Will there be a conversation, a screen-based task, reading, writing, or movement between locations? Will observers attend? A participant can help select an appropriate format only if the activity is clear.

Avoid making the access check itself unnecessarily demanding. A long mandatory questionnaire may collect details your team never uses. Start with the practical question and follow up on arrangements that matter to this session.

Use an accommodation planner with owners

The following planner is an original operational aid. Adapt its categories to the activity instead of treating every row as a question every participant must answer.

Area	Arrangement to confirm	Owner’s completion check
Contact	Preferred way to receive updates	Participant received and understood the confirmation
Materials	Format and timing for reading or tasks	Materials sent in the agreed form before they are needed
Communication	Captions, interpretation, or another agreed mode	Required support is booked and the setup is checked
Equipment	Participant’s device and assistive technology	Joining and participation tools have been checked with the participant
Timing	Session length, breaks, and time constraints	Calendar and discussion guide include the arrangement
Location	Access, arrival instructions, or remote alternative	Participant knows how to arrive or join and whom to contact

If the activity evaluates a prototype, distinguish access to the session from accessibility of the prototype itself. Checking the joining tools does not establish that the interface under study will work.

Record the practical arrangement in the working schedule. Restrict sensitive personal detail to people who need it to support participation. A moderator may need to know “pause after each task,” without receiving an unrelated account of someone’s health.

A worked example: researching shift scheduling

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

The first participant’s session includes reading a sample schedule. The researcher sends a structured text version in the requested format, checks with the participant that it is usable, and checks whether the task remains meaningful. The note-taker records which version was used so the team does not later claim to have 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 must make a separate arrangement or explicitly leave that question unanswered. Changing the format can preserve participation while changing what the method can establish.

That distinction prevents a convenient adaptation from quietly becoming an unsupported conclusion.

Let the participant’s setup inform 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. Read the session guidance.

Build setup and breaks into the schedule rather than taking them out of the substantive research time. If an interpreter or support person will attend, clarify the roles in advance. Continue directing questions to the participant and record when another person contributes an answer.

If the agreed technology fails, use the fallback you discussed or reschedule. Do not pressure someone to continue through a format that prevents them from participating meaningfully. Capture the setup failure separately from product-task observations.

Do not turn one participant into a spokesperson

Ask people about their own experience. Someone can explain their interaction with a service without being responsible for representing 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 also recommends combining user involvement with standards-based evaluation; user sessions alone do not establish conformance. Read W3C’s evaluation guidance.

For a workflow interview, the corresponding reporting habit is straightforward: describe the participant context, the format used, the arrangements made, and the limits of what you observed. Avoid writing “accessible for everyone” because one adapted session went well.

Finish recruitment with confirmed arrangements, not merely completed bookings. Your session list should show who owns the materials, communication support, technology check, and fallback. That turns inclusion from a promise into a process the participant can actually use.