Researcher – Quick Guide

Mission Statement

An accessibility role researcher, also known as a UX researcher with a focus on accessibility, focuses on understanding how people with disabilities interact with a product or service and ensuring it is accessible to all. They conduct research, often involving individuals with disabilities and assistive technology users, to identify usability issues and potential barriers. This role also involves understanding and applying accessibility standards and regulations like WCAG to create inclusive and equitable experiences.

The role of the researcher

1. Core Responsibilities

User Understanding & Inclusion

  • Represent a wide spectrum of abilities, contexts und device constraints
  • Recruit and engage participants using screen readers, magnifiers, voice control, switch devices
  • Incorporate situational impairments (Glare, one- hand use, stress) into test design

Methodology & Test Design

  • Develop test scripts that work with assistive technologies
  • Ensure prototypes are accessible enough for research use
  • Design tasks that expose navigational, cognitive und interaction- based barriers
  • Avoid biasing instructions — neutral, inclusive moderation

Research Execution

  • Conduct remote and in- person studies with AT users
  • Observe reading order, focus indicators, keyboard behavior
  • Capture patterns of confusion, cognitive load, misinterpretation

Analysis & Synthesis

  • Identify barriers mapped to WCAG principles (Perceivable, Operable, Understandable, Robust)
  • Prioritize insights based on severity, frequency, and user impact
  • Translate raw behavior into structured, actionable design/engineering guidance

Collaboration

  • Align with Design on structure, layout clarity, interaction patterns
  • Align with Engineering on AT compatibility and testing feasibility
  • Provide PO/PM risk visibility and severity scoring for accessibility gaps

2. Fast Checklist (Before Any Research Begins)

Top 10 Researcher Checks

  1. Prototype usable via keyboard (at least enough for testing)
  2. Screen reader can access key paths (VoiceOver/NVDA smoke test)
  3. All tasks are written in plain, bias- free language
  4. Test materials include alternatives for visual- only content
  5. Consent forms readable and screenreader- friendly
  6. Meeting platform supports AT (Zoom, Teams Screenreader Mode)
  7. Research script avoids “click the green button” wording
  8. Task descriptions include goal, not method (“Find X”, nicht “Click Y”)
  9. Accessibility barriers tagged in Notion/Figma/Miro
  10. Recruitment includes at least one AT user per major feature stream

Escalation & Support – If you’re stuck

  • Contact the Accessibility Guild/Champions
  • Involve the Design System Team for structural patterns
  • Consult with Engineering regarding AT limitations
  • Involve the Product Owner/Project Manager for prioritization and risk visibility

3. Templates & Deliverables

Research Script Template (A11y- Ready)

  • Intro & consent
  • Neutral task phrasing
  • AT- specific navigation instructions
  • Error capture field
  • Observational notes: visual, cognitive, auditory, motor
  • WCAG- mapping field

Accessibility Findings Template

  • Summary
  • Barrier description
  • Severity
  • Affected users
  • WCAG reference
  • Recommended fix
  • Expected user outcome

Recruiting Template

  • AT user profile
  • Disability spectrum segmentation
  • Remote setup instructions

Template for Accessibility Evaluation Reports

W3.org Researchers report template

4. Tools & Resources

How to Conduct Usability Studies for Accessibility

The UX researcher’s guide to getting started with accessibility research

The Designer’s Guide to Accessibility Research

Microsoft Inclusive Toolkit

WAI Personas

Providers of tests with people with disabilities:
Stiftung Pfennigparade München

How to meassure digital accessibility success (PDF from levelaccess)

Keyboard Navigation & Focus

A11yCasts What is focus?

A11yCasts explains Keyboard Navigation Part 1

A11yCasts explains Keyboard Navigation Part 2

A11yCasts explains Headings and Landmarks

Screen Reader

Shortcuts Screen Reader (VoiceOver) Desktop

VoiceOver (macOS) Official guide & shortcuts

  • Command + F5: Start/ End VoiceOver
  • Control: Stop reading
  • Control + Option + Command + H: Next heading
  • Control + Option + Command + J: Next form field
  • Control + Option + U – opens: VoiceOver- Menue In Menue Jump between sections & landmarks, headings, links, form fields, etc.

A11yCasts explains Screen reader basics VoiceOver MacOS

A11yCasts explains VoiceOver Mobile iOS

Talkback (Adroid Screenreader)

A11yCasts explains TalkBack Mobile

Windows Screenreader


Kommentare

Schreibe einen Kommentar

Deine E-Mail-Adresse wird nicht veröffentlicht. Erforderliche Felder sind mit * markiert