Usability testing for users with disabilities: a practical guide

Around one in six Australians live with some form of disability, according to the Australian Bureau of Statistics. Yet digital products, from government portals to banking apps, are often tested only with users who do not face these everyday barriers. Usability testing that genuinely includes people with disabilities uncovers friction that lab-based reviews miss and helps teams meet obligations under the Disability Discrimination Act 1992. The practice also aligns with the principles behind the National Disability Insurance Scheme, which places choice and control in the hands of participants.

Running these sessions well requires planning, empathy and a willingness to adapt the script rather than the participant. The guidance below draws on field-tested approaches used by accessibility consultants across Australia and shows how a free platform such as UCDmanager can keep the entire process organised, from recruitment through to reporting.

Why inclusive usability testing matters in Australia

Public sector bodies in Melbourne, Sydney and Brisbane are increasingly required to demonstrate that their digital services meet the Web Content Accessibility Guidelines. The Australian Human Rights Commission has repeatedly called out inaccessible websites, and private companies face reputational and legal risk when their apps exclude users. Usability testing with people who rely on screen readers, switch controls, captions or voice input reveals whether the design choices on paper actually work in practice.

There is also a commercial argument. Australia's ageing population means more customers experience low vision, reduced dexterity or cognitive change over time. Designing for the edges benefits everyone, including people using a phone one-handed on a crowded Perth commuter train or a parent navigating a noisy Adelaide café.

Planning sessions with diverse participants

Begin by mapping the range of disabilities your user base might include: vision impairment, hearing loss, motor differences, cognitive conditions and temporary or situational limitations. Pair each with the assistive technologies commonly used locally, such as JAWS and NVDA on Windows, VoiceOver on iPhones, and the built-in screen reader on Android devices. Plan representative tasks rather than abstract exercises, so participants complete something close to a real booking, form submission or purchase. Where possible, align test scenarios with the user journey you are documenting. A practical walkthrough of mapping flow from existing research data lives in the article on how to create a user journey map from existing data.

Budget extra time for setup, rest breaks and unfamiliar equipment. Participants may need their own devices, a familiar keyboard layout or a particular chair. Build a flexible schedule and let the participant decide the pace.

Recruiting participants across Australian cities

Aim for a panel that reflects the spread of Australian life: users in capital cities, regional towns and remote communities. Partner with organisations such as Blind Citizens Australia, Deaf Australia or the Australian Federation of Disability Organisations to reach genuine participants rather than proxies. Offer reimbursement for travel, support workers and time, because many people live on fixed incomes and the NDIS does not always cover research participation.

When remote sessions are more practical, choose tools that work across low-bandwidth connections in regional Queensland or Tasmania. Always ask participants which device and operating system they prefer, and check whether they need a particular browser or version. A reliable, mainstream handset such as the Moto E is often a fair testbed because it ships with a near-stock Android build that mirrors what many Australians actually own.

Conducting the test with accessibility in mind

Open the session with a clear, plain-English explanation of what will happen and how the data will be used. Ask permission before recording and offer to stop at any time. Allow the participant to use their own equipment, settings and input methods rather than a lab machine, because switching environments can mask real usability issues.

Think-aloud protocols work well, but be patient with verbal fatigue, speech differences or communication aids. Provide captions for remote sessions and confirm they are accurate before the test begins. Where a participant uses a support worker or interpreter, address the user directly and let the helper step in only when invited. Take notes on both task completion and emotional response, since frustration is often the clearest signal of an interface problem.

Analysing findings and documenting them

After each session, transcribe observations while the memory is fresh and tag findings against the relevant success criterion. Group issues by severity and by the disability profile they affect, then cross-reference with any existing heuristic evaluation notes the team has produced. Overlap between expert review and lived experience usually pinpoints the most urgent fixes.

Store everything in a shared, searchable workspace so designers, developers and policy stakeholders can find the evidence later. Summarise patterns rather than isolated quotes, and always protect the participant's identity in published reports. A short video clip, with consent, is often more persuasive than a written summary for busy decision-makers in organisations unfamiliar with accessibility work.

Turning insights into design changes

Translate the prioritised findings into concrete backlog items, each tied to a specific user story and acceptance criterion. Where the data shows a pattern across multiple participants, treat it as a release blocker rather than an optional enhancement. Track changes against accessibility goals over time, and revisit the same test scenarios after redesigns to confirm improvements.

Pair each round of usability testing with a broader audit so that issues uncovered in one project inform the team's standard practice. Build relationships with the participant panel so future research is faster and participants feel valued. The combination of structured testing, thoughtful recruitment and well-kept documentation makes digital products that welcome every Australian, regardless of how they interact with a screen.