One thing that we found when researching was that although there were tons of guidelines for web accessibility, there were hardly any for mobile – the ones that did exist weren’t very easy to find. Which is so surprising when you think about it, apps have been mainstream for well over a decade, yet there are no black and white guidelines which people implemented years ago to ensure accessibility!
This led us to draft our own internal accessibility testing standard, including detail on regression testing for accessibility, the level at which we’ll test using screen readers and scaling, as well as known limitations of accessibility across iOS and Android
The following contains the standard for testers at Cube to adhere to when testing accessibility. As there are very few set guidelines for mobile development in terms of accessibility testing, to prevent discrepancy across projects we have defined an in-house standard. This has been compared to existing web standards, as well as the accessibility functionality of leading apps across both iOS and Android.
Accessibility Regression Testing
Testers to compile a standardised accessibility test script that can be applied to all 3SC projects. This will contain runs that meet AA and AAA standard, as well as meeting the standard defined within this document that has been agreed as 3SC’s internal accessibility development and testing standard.
When testing a screen reader, we would need to define priority of content to be read out – screen reader to then follow this priority. Default would be reading content from top to bottom of screen.
Images that provide no extra value/information to user to be hidden from screen reader, e.g. a decorative image would not be announced by a screen reader, but an image containing information such as COVID-19 regulations would need to be announced, therefore content would need to be added to the alt text
To be tested on font size up to 200% – this is the standard largest size recommended for web testing so remains consistent with existing accessibility standards. If no percentage visible on device, tester should use largest available font size.
To be tested primarily by creative team within the creative review of each ticket – this means that any necessary changes can be actioned before the app reaches UAT, meaning that the product handed over meets the required standard
Testers to complete a spot check of colour contrast as part of the accessibility regression. iOS to be tested using TPGI Colour Contrast Checker. Android Colour Contrast can be tested using Android Accessibility Scanner
Testers to compile dictionaries of common device gestures that can be used when testing accessibility