Mobile testing
Mobile accessibility testing can come in two forms. It can test how responsive a web application is in a mobile phone or tablet viewport, or it can test native applications developed specifically for phones or tablets. Responsive web testing can be done using a desktop or appropriate mobile or tablet hardware. Native mobile testing requires the actual mobile or tablet hardware, as they come with assistive technology to allow users with disabilities to access all forms of digital content. Specific knowledge of gestures and commands are also required for native mobile testing purposes. This has become an important part of comprehensive accessibility testing, as more and more people rely on their phones and tablets for their digital needs.
Need help?
Please contact Nationwide's Digital Accessibility Team if you need help with mobile testing or training.
Contact Us »Mobile screen readers
About Rotor
You can use the VoiceOver rotor to change how VoiceOver works. You can change the VoiceOver volume or speaking rate, move from one item to the next on the screen, and more.
Learn more about VoiceOver RotorTask | Gesture |
---|---|
Start (or stop) VoiceOver | (When setting is enabled) Triple-press home button or side button (for full screen devices without home button) |
Pause/restart reading | Two-finger tap |
Start reading continuously from this point on | Two-finger swipe down |
Read entire page | Two-finger swipe up |
Read next item | Swipe right |
Activate link or button | Double-tap |
Close popup, cancel last action | Two-finger scrub |
Go to next heading, landmark, list, link | Rotor, swipe down |
Choose from a complete list of items on page | Two-finger triple-tap |
Navigate table cells | Swipe up, down, left or right |
Go to next list item | Swipe right |
Go to next image | Rotor, swipe right |
Go to first/last item on page | 4 finger tap upper/lower half of screen |
Scrolling | 3 finger swipe up, down, left, or right |
Go to previous heading, landmark, list, link | Swipe up |
- The local context menu (LCM): contains navigation options relevant to the current page. Options appear in a circle by default. Open the local context menu by swiping up, then right.
- The global context menu (GCM): contains options relevant anywhere on your device. Options appear in a circle and in the corners of the screen, by default. Open the global context menu by swiping down, then right.
- Firefox Browser Navigation (FBN): The Firefox browser adds navigation features using three-finger swipes. Swiping up or down with three fingers chooses an element type, and swiping left or right with three fingers moves to the next or previous element of that type.
Task | Gesture |
---|---|
Turn TalkBack on | Power button, then hold two fingers on screen |
Turn TalkBack off | Must be turned off in the device accessibility settings |
Open the Global Context Menu (GCM) | Swipe down, then right |
Open the Local Context Menu (LCM) | Swipe up, then right |
Stop reading | Single tap |
Read from this point on | GCM, Read from next item |
Read next item | Swipe right |
Repeat last | GCM: Repeat last utterance |
Activate link or button | Double tap |
Go to next heading | LCM or FBN: headings |
Go to next landmark/region | LCM: Landmarks |
Go to main content region | Use the “Skip to Main Content” link if present, explore by touch, or use GCM Quick Nav to search for the desired section |
Show list of all elements onscreen | GCM: Quick navigation |
Navigate table cells | Swipe left or right. TalkBack reads table cells in order left to right; or explore by touch. |
Go to next list | LCM: List navigation |
Go to next list item | FBN: List items |
Go to next link | FBN: Links |
List all elements | GCM Quick Navigation |
Go to first item on page | Swipe up, then down |
Go to last item on page | Swipe down, then up |
Go to home screen | Swipe up, then left |
Go back | Swipe down, then left |
Recent apps | Swipe left, then up |
Notifications | Swipe right, then down |
To previous heading, landmark, table, focusable item, etc. | Swipe up or left |