Mobile accessibility: testing mobile sites and native apps for accessibility

Unfortunately, when developing WCAG2, the 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 Classic). 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 touchscreen user โ€“ which is essential on a mobile device. WCAG2.1 does include some mobile accessibility requirements, but doesnโ€™t go far enough. Gian Wild chaired the Mobile Site Sub-Committee to develop a set of Mobile Site Testing Guidelines that are available under Creative Commons. These guidelines are meant to be used in conjunction with WCAG2 (and WCAG2.1) to ensure that sites are accessible to people with disabilities using mobile and tablet devices.


Accessibility is important to all โ€“ not everyone using your mobile app, device or wearable will be fully functioning: either because they have a disability or they are simply engaged elsewhere. Gian Wild talks about the things that are essential to avoid when designing mobile apps, devices and wearables to ensure that everyone can use them. She talks about specific mobile accessibility features: pinch zoom, native screen readers, haptic keyboard etc, and system accessibility settings: font size, screen rotation, high contrast etc


๐ŸŽค Presenter: gianwild
๐Ÿ”— Session Details: https://www.drupalgovcon.org/2020/program/sessions/mobile-accessibility-testing-mobile-sites-and-native-apps-accessibility

Drupal is a registered trademark of Dries Buytaert.