Recruit Disabled Participants for Accessibility Research
Build an ethical, accessible recruitment plan based on functional needs, assistive technology, suitable screeners and participant accommodations.
Start with the research question, not a disability list
Recruiting disabled participants for accessibility research starts with the task you need to understand. Recruit people whose lived experience, functional needs and usual way of using the product are relevant to that task—not a broad quota such as “five disabled users”.
A disability label does not define one user group. People have different experiences, expectations, preferences, technologies and strategies, as the W3C Web Accessibility Initiative explains. A defensible recruitment brief therefore states who you need, why they are relevant and how the session will work.
Participant research and standards-based audits answer different questions. An audit assesses defined accessibility requirements. Research with participants shows how people approach a journey and respond to barriers in context. Use both where the decision requires compliance evidence and lived experience. Our guide to inclusive UX research methods covers the wider approach.
Turn research goals into functional recruitment criteria
Start with the priority journey, then identify the functions involved. An account-management journey may require someone to perceive information, operate controls, remember details, concentrate through a form or use keyboard, switch or voice input.
Record the behavioural context that determines what evidence a participant can provide:
- Relevant product or task experience
- Usual device and browser
- Input and output methods
- Assistive technology or settings used in daily life
- Familiarity with that technology
- Typical environment for the task
Section 508 advises teams to screen for functional needs rather than diagnoses, including assistive-technology use, typical devices and comfort level in its usability-testing guidance.
Classify each criterion as must-have, useful variation or out of scope. A must-have changes the decision the research must support. Useful variation broadens the evidence when capacity permits. This prevents one participant from being treated as representative of everyone with a similar diagnosis or impairment category. Apply the same discipline used in general participant recruitment planning.
Use the functional-needs recruitment worksheet
This completed matrix is a hypothetical planning illustration for an online account-management usability study. It is not a universal quota or a claim about every person with a particular functional need.
| Research question | Participant segment and functional interaction | Eligibility evidence | Usual technology or strategy and proficiency | Product familiarity | Sourcing channel | Access needs and moderator handoff | Priority |
|---|---|---|---|---|---|---|---|
| Can people find and understand an outstanding balance? | People who usually access account information non-visually | Has managed an online account or bill in the past 12 months | Regular screen-reader use on their usual desktop or mobile device; confirm their usual setup | Online account or billing experience | Specialist panel or customer research panel | Confirm preferred remote platform; allow the participant to use their own setup | Must-have |
| Can people update payment details without pointer input? | People who routinely operate websites by keyboard | Has completed an online payment or account task | Keyboard navigation with usual browser settings; confirm routine use | Relevant account or payment experience | Specialist panel or transparent direct outreach | Check keyboard operation in the prototype before the session | Must-have |
| Are account messages understandable with enlarged text? | People who use enlarged display settings | Reads account notices online | Browser zoom, magnification software or another usual enlargement method | Online account-notice experience | Community partner or customer channel | Provide usable digital materials | Useful variation |
| Can people recover from failed sign-in? | People who use a preferred pacing or memory-support strategy | Has recovered access to an online account | Password manager, reminders or another usual strategy | Relevant sign-in experience | Customer channel or community outreach | Agree breaks and flexible pacing | Useful variation |
Test the prototype with every interaction method in scope before recruitment. If an avoidable blocking defect prevents a participant from using their normal method, the session may only confirm that known blockage rather than answer the research question.
Copy this worksheet into the recruitment brief:
| Research question | Participant segment and functional interaction | Eligibility evidence | Usual technology or strategy and proficiency | Product familiarity | Screener question | Sourcing channel | Access needs | Moderator handoff | Priority |
|---|---|---|---|---|---|---|---|---|---|
Remove any field that does not change whom you recruit or how you prepare the session. Research Operations guidance can help assign ownership for the handoff.
Write screener questions without requesting diagnoses
Ask candidates how they complete the relevant activity. Do not default to requesting a diagnosis. You will rarely need medical information to establish whether someone fits a usability study.
Use neutral questions such as:
- Which device do you usually use to manage accounts, bills or subscriptions online?
- How do you usually move through and operate controls on websites: keyboard, mouse, touch, voice input, switch device or another method?
- Do you use any tools or settings to access online information? You can describe them in your own words.
- How often do you use this device, method or tool for online account tasks?
- In the past 12 months, have you viewed a balance, changed payment details, downloaded a statement or recovered access to an account?
- Is there a format, communication method or arrangement that would help you take part?
Offer free text and, where appropriate, “prefer not to say”. Use branching only for interactions within scope. Keep qualification separate from accommodation: needing breaks, an interpreter or a different platform does not itself make someone unsuitable. Tie any exclusion to the research goal, such as lacking relevant account-management experience. See screener questions and branching logic.
Choose recruitment channels and build trust
Choose channels according to the functional variation required. Specialist recruiters and panels can help with precise criteria. Disability-led organisations and community groups may offer relevant context and established trust. Customer channels can be useful where current product experience matters, while direct outreach needs a clear and respectful invitation.
Use more than one channel where practical so the study does not depend on one panel or only on people familiar with research. Tell community organisations the study purpose, eligibility, session format, incentive, available access arrangements and the support you are requesting. Budget for substantial recruitment support. Do not ask organisations for private member or customer lists; they should decide whether and how to share an invitation.
Track which channels produce each required segment during fieldwork. Change the sourcing mix if a gap appears. A maintained opt-in panel may also support future studies; see building and maintaining a research panel.
Plan accommodations before confirming the session
Ask every qualified participant how they prefer to communicate and what would help them participate. Do not infer arrangements from a disability label.
GOV.UK advises recruiters to check preferences for contact, communication support, technology, material format, travel and location in its guidance on finding user research participants. Arrangements may include accessible digital materials, communication support, use of the participant’s own assistive technology, breaks, a longer session, travel support, venue access or a support person.
Treat access arrangements as study costs, not deductions from the participant incentive. For remote research, offer workable phone or meeting technologies and check compatibility before the session. GOV.UK recommends having several technologies available and allowing participants to choose what works best in its remote-research guidance.
Pass the moderator only the operational details needed to run the session: contact method, platform, support arrangements, breaks, materials and relevant setup information.
Handle consent and disability data responsibly
Disability information may reveal health information and may therefore be special-category personal data under UK GDPR. The Information Commissioner’s Office guidance explains this connection. Confirm the lawful basis and handling process with your organisation’s data-protection adviser; this is not universal legal advice.
Collect only the information needed to establish eligibility, arrange participation and answer the research question. GOV.UK similarly advises teams to collect the minimum necessary information in its participant-privacy guidance.
Send consent information before the session in language and a format the participant can use. Cover purpose, recording, observers, storage, sharing, retention and withdrawal. GOV.UK’s consent guidance supports this standard.
Restrict access to full screener responses, define deletion points and share accommodation details only with people who need them to run the session.
Run a final recruitment readiness check
Do not open recruitment until you can answer yes to each question:
- Do the criteria trace directly to the research questions?
- Can each channel reach the required segments?
- Are screener and consent materials usable with relevant technology?
- Are access arrangements and costs funded?
- Has the session technology been checked?
- Is sensitive-data handling approved?
- Does the moderator have the necessary operational handoff?
Review the sample during fieldwork. If a required segment is missing, correct the gap rather than filling the place with a near match. Keep verification proportionate, using guidance on spotting fraudulent research participants.
Frequently asked questions
Should a screener ask participants for their disability diagnosis?
Usually, no. Screen for the functional interaction, relevant experience and assistive-technology use the study requires. Collect diagnosis information only when it is necessary, justified and handled through the applicable data-protection process.
What accessibility research screener questions should I ask?
Ask how candidates complete the target activity, which device and input or output methods they use, how often they use them, their relevant journey experience and what arrangements would help them participate.
Where can I recruit assistive-technology users?
Consider specialist panels, disability-led or community organisations, relevant customer channels and transparent direct outreach. Assess each source for audience fit, trust, privacy and participant diversity.
How early should I recruit disabled research participants?
Allow more lead time when community relationships, uncommon criteria, communication support, travel or accessible materials are required. Check those dependencies before setting the timetable.
Are remote accessibility research sessions always more inclusive?
No. Remote sessions can remove travel and venue barriers, but they can also introduce inaccessible software, connectivity problems or communication barriers. Offer workable formats and test the chosen setup with the participant.
About Glasgow Research — Glasgow Research helps B2B SaaS teams turn customer and market research into product decisions. Work with us.
Author
About Vadim Glazkov
Vadim Glazkov is the founder of Glasgow Research and a product research expert working with founders and B2B SaaS teams on customer interviews, JTBD, market validation, and decision-ready research.