INTRODUCTION
Unfortunately, when developing WCAG2, the W3C WCAG Working Group did not envision the current world where mobile is almost ubiquitous. For example, on a mobile device there is no continual access to a keyboard (unless someone is using it as an add-on to the device – or using a Blackberry Clas- sic!). WCAG2 requires that all content be accessible to the keyboard interface, but it does not require that all content be accessible to a mouse or to a tou- chscreen user, which is essential on a mobile device. WCAG2.1 does include some mobile accessibility requirements but does not go far enough (Wild, 2015) (Alajarmeh, 2022). The ICT Accessibility Testing Symposium has developed a methodology for evaluating the accessibility of mobile websites. This methodology is an amalgamation of accepted mobile site accessibility testing standards from around the world, including additional developments from the ICT Acces- sibility Testing Symposium’s Mobile Site and Native App Sub-Committee.
WCAG2 success criteria are applicable to mobile sites; however, not all aspects of mobile site accessibility are specifically covered by WCAG2. It was the opinion of the committee that merely conforming WCAG2 (or WCAG 2.1) would not provide for a fully accessible experience for users with disabilities.
© 2023. Published by AHFE Open Access. All rights reserved. 11
12 Wild
ABOUT THE DOCUMENTS Please note that this methodology does not include those issues already inclu- ded in WCAG2; however, it does include issues identified in WCAG2.1. This guide was written with the intent to clarify the unique needs of users with disabilities who use mobile websites and to raise the bar for the web deve- lopment community. This is a work-in-progress, and, as such, the committee does not make a claim that conforming to these requirements will ensure that your mobile site is fully accessible to all users.
Gian Wild chaired the Mobile Site Sub-Committee to develop a set of Mobile Site and Native App Accessibility Testing Guidelines that are avai- lable under Creative Commons. These guidelines are meant to be used in conjunction with WCAG2 (and WCAG2.1) to ensure that sites are accessi- ble to people with disabilities using mobile and tablet devices. There are two sets of documents: one for Mobile Sites and one for Native Apps. These are available on the AccessibilityOz website (ICT Mobile Site and Native App Sub-Committee, 2023).
OVERVIEW OF THE MOBILE SITE METHODOLOGY There are two overview documents:
- Mobile Site Accessibility Testing Methodology (Word, 5.48 MB)
- About Mobile Site Testing – Devices, assistive technologies, site types, variations of a page and capturing errors (Word, 23.4 MB) The steps for Mobile Site accessibility are:
1. Identify devices: the committee recommends testing with iPhone (Safari), iPad (Safari) and Android (Chrome), but also consider alternative devices such as an Android tablet, especially if this is indicated in analytics or expected usage. 2. Identify site type and variations: identify whether the site is a desktop site (one view whether on a desktop or mobile device), responsive site (resize as the screen size changes) or m.dot site (a completely separate site for mobile devices). Where the site is a responsive site, identify all the different variations of the page. 3. Test critical issues: test for any traps on the website (exit trap, swipe/scroll trap and layer trap). 4. Test mobile issues: test cases are broken into the following categories: Alternatives, Display, Actionable items, Navigational aids, Audio and video, Forms and Mobile/desktop interaction. 5. Test mobile assistive technology and feature support.
MOBILE SITE METHODOLOGY There are three sets of test case documents, which detail how to test a particu- lar requirement in the methodology, why it is important and example passes of the requirement:
Mobile Site and Native App Accessibility Testing Methodology 13
- Mobile Site Accessibility Testing Methodology – Critical test cases (Word, 22.3 MB)
- Mobile Site Accessibility Testing Methodology – Test cases (Word, 90.77 MB)
- Mobile Site Accessibility Testing Methodology – Test cases for assistive technologies and mobile features (Word, 48.14 MB) The following are the test cases for Mobile Site Methodology:
- Critical
- Exit trap
- Swipe/scroll trap
- Layer trap
- Alternatives
- Motion, interaction and gesture
- Touch gestures
- Geolocation
- Change of state
- Audio cues
- Status messages
- Abbreviations
- Summary of content
- Ambiguous text
- Display
- Three flashes
- Change on request
- Target size
- Inactive space
- Fixed size containers
- Justified text
- Color contrast
- Orientation
- Animation
- Pinch zoom
- Reflow
- Actionable items
- Content on hover, focus or input
- Native UI
- Descriptive text links
- Non-keyboard options
- Infinite scrolling
- Color alone
- Removal of touch
14 Wild
- Navigational aids
- Visual indicators
- Character key shortcuts
- Descriptive headings
- Inactivity timeout
- Navigation features
- ARIA
- Audio and video
- Transcript
- Closed captions
- Live audio and video
- Forms
- CAPTCHA
- Context-sensitive help
- Error prevention
- Positioned field labels
- Visible field labels
- Accessible name
- Form and keyboard interaction
- HTML5
- Mobile/desktop interaction
- Consistency
- Linking between types of a site
- Assistive technology testing: iOS
- VoiceOver
- Keyboard
- Switch
- Zoom
- Reduce Motion
- Invert Colors
- Grayscale
- Reader View and increase text size
- Assistive technology testing: Android
- TalkBack
- Keyboard
- Switch
- Magnification
- Remove Animations
- Color Inversion
- Grayscale
- Color correction
- Increase display size
Mobile Site and Native App Accessibility Testing Methodology 15
- Increase text size with Android Chrome
- Simplified view
OVERVIEW OF NATIVE APP METHODOLOGY The steps for Native App accessibility are:
1. Identify devices: as per mobile site accessibility. 2. Define application functionality: identify the purpose of the native app and detail the required user journeys and test for common elements such as:
- Navigation – menus, header, footer
- Landing screen(s)
- Emergency sections and content
- Login flows
- Settings
- Account and profile
- Contact Us
- Real-time updates (eBay, Uber)
- Privacy policy, Terms and Conditions
- Interactional functionality (adding items to a shopping cart, payment details, live chat, selections for a product in a catalogue, scanning a barcode, VR, QR code)
- Help section
- Widgets (calendars, date pickers)
- Third-party integrations (geo-locational maps)
- High-traffic areas
3. Test critical issues: test for any traps in the native app (exit trap, swipe/scroll trap and layer trap, text-to-speech trap, headset trap). 4. Test mobile issues: test cases are broken into the following categories: Alternatives, Display, Actionable items, Navigational aids, Audio and video and Forms. 5. Test mobile assistive technology and feature support.
There are two overview documents:
- Native App Accessibility Testing Methodology (Word, 2.05 MB)
- About Native App Testing – Devices, assistive technologies and capturing errors (Word, 2.06 MB)
NATIVE APP METHODOLOGY There are three sets of test cases documents, which detail how to test a par- ticular requirement in the methodology, why it is important and example passes of the requirement:
- Native App Accessibility Testing Methodology – Critical test cases (Word, 37.13 MB)
16 Wild
- Native App Accessibility Testing Methodology – Test cases (Word, 101.94 MB)
- Native App Accessibility Testing Methodology – Test cases for assistive technologies and mobile features (Word, 77.9 MB) The following are the test cases for Mobile Site Methodology:
- Critical
- Exit trap
- Swipe/scroll trap
- Layer trap
- Text-to-speech trap
- Headset trap
- Alternatives
- Motion, interaction and gesture
- Touch gestures
- Geolocation
- Change of state
- Audio cues
- Status messages
- Abbreviations
- Summary of content
- Ambiguous text
- Display
- Three flashes
- Change on request
- Target size
- Inactive space
- Fixed size containers
- Justified text
- Color contrast
- Orientation
- Animation
- Actionable items
- Content on hover, focus or input
- Native UI
- Descriptive text links
- Non-keyboard options
- Infinite scrolling
- Color alone
- Removal of touch
- Navigational aids
- Visual indicators
- Character key shortcuts
Mobile Site and Native App Accessibility Testing Methodology 17
- Descriptive headings
- Inactivity timeout
- Navigation features
- Audio and video
- Transcript
- Closed captions
- Live audio and video
- Forms – CAPTCHA
- Context-sensitive help
- Error prevention
- Positioned field labels
- Visible field labels
- Accessible name
- Form and keyboard interaction
- Assistive technology testing: iOS
- VoiceOver
- Keyboard
- Switch
- Zoom
- Reduce Motion
- Invert Colors
- Grayscale
- Assistive technology testing: Android
- TalkBack
- Keyboard
- Switch
- Magnification
- Remove Animations
- Color Inversion
- Grayscale
- Color correction
- Increase display size
- Increase font size
ACKNOWLEDGMENT
The author would like to acknowledge the following people.
The Mobile Site Testing Methodology was developed by the ICT Acces- sibility Testing Symposium Mobile Sub-Committee. Members include: Gian Wild (Co-Chair), Peter McNally (Co-Chair), Brent Davis, Corbb O’Connor, Karen Herr, Kathryn Weber-Hottleman, Kathy Eng, Laura Renfro, Megha Rajopadhye, Mona Rekhi, Morgan Lee Kestner, Rafal Charlampowicz, Ryan Pugh, Steve Sawczyn, Sunish Gupta, Tom Lawton and Chris Law.
18 Wild
The Native App Testing Methodology was developed by the ICT Acces- sibility Testing Symposium Native App Sub-Committee. Members include: Gian Wild (Co-Chair), Jennifer Chadwick (Co-Chair), Kathy Eng, Ryan Pugh, Kathryn Weber-Hottleman, Brent Davis, Laura Renfro, Peter McNally, Karen Herr, Steve Sawczyn, Sunish Gupta, Tom Lawton, Sam Bouchat, Rafal Charlampowicz, Damon Wandke, Morgan Lee Kester, Mona Rekhi, Corbb O’Connor and Chris Law.
REFERENCES
Alajarmeh, N. (June 1, 2022) “The Extent of Mobile Accessibility Coverage in WCAG2.1: Sufficiency of Success Criteria and Appropriateness of Relevant Con- formance Levels Pertaining to Accessibility Problems Encountered By Users Who Are Visually Impaired”, in: Universal Access in the Information Society, Volume 21 Issue 2. pp 507-538 ICT Mobile Site and Native App Sub-Committee. (February 1, 2023) Mobile
Testing. AccessibilityOz website: https://www.accessibilityoz.com/resources/mobi le-testing/ Wild, G. (October 20, 2015) Mobile Accessibility Fails: Do We Need a WCAG3?
SitePoint website: https://www.sitepoint.com/mobile-accessibility-fails-need-wc ag3/