Perspective

Screen-reader testing as a task, not a tour

Use a screen reader to complete representative work rather than simply listening to every element on a page.

A screen reader is not an accessibility scanner you drive manually.

Name the environment

Record the screen reader, version where useful, browser or app platform, and device. Results from one combination should not be reported as universal screen-reader compatibility.

Learn the interaction model first

If you are new to the screen reader, practise on known accessible content before evaluating a product. Otherwise it is easy to report unfamiliarity with the tool as a product defect.

Attempt a real task

Use the same task you would give another tester. Navigate, make choices, enter information, cause errors and complete the outcome.

Listen for meaning

Pay attention to:

• page/screen structure;
• control names, roles and states;
• instructions and relationships;
• errors and status changes;
• focus after actions;
• unexpected repetition or missing context.

Use multiple navigation strategies

Do not test only by swiping or moving item by item. Where appropriate, navigate by headings, controls, landmarks, links or other screen-reader mechanisms.

What a pass establishes

The tested task was usable with that screen-reader/environment combination at that time.

What it does not establish

It does not prove usability with other screen readers, low-vision access, keyboard-only access, cognitive accessibility or accessibility for all disabled users.