Record the operating system, browser or app, screen reader version and product build.
Screen reader testing
To understand how someone uses your product with a screen reader, test the same journey on their platform. Prepare the session, choose a guide and record what happens: commands help you explore; observations help document barriers.
Prepare the session
Choose a task to test and a platform, then prepare the device, screen reader and conditions to record.
- Settings
Configuration used
Record zoom, text size, rotor options or reading controls and command customisations. Do not assume defaults.
Platform guides
Keyboard navigation, reading modes and tests with NVDA, JAWS and VoiceOver.
Touch exploration, gestures, reading order and announcements on Android.
Gestures, rotor, reading order and announcements on iPhone and iPad.
Gestures, keys and voice commands for every platform, with animations and comparisons.
Collect observations
Anyone reading the issue report must be able to reconstruct the test. Record the environment, commands, observed behaviour and expected result, together with the impact on the journey.
- Sequence
Steps and focus
Write down the commands used, the order of reached elements and where focus is before and after each action.
- Outcome
Announcements and barriers
Report announced names, roles, states and messages. If the flow stops, identify the exact point and expected result.