Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Android and iOS Accessibility Testing

Android and iOS Accessibility Testing

With the exponential increase of mobile devices it’s critical for developers, testers and designers to understand how accessible and usable their native and web applications are for people of different abilities. This talk goes over best practices, techniques and some of tools of testing native and mobile web applications on Android and iOS devices.

Crystal Preston-Watson

August 28, 2019
Tweet

More Decks by Crystal Preston-Watson

Other Decks in Technology

Transcript

  1. AGENDA • Accessibility 101 • iOS • Features • Tools

    • Things to Note • Android • Features • Tools • Things to Note • Best Practices
  2. Websites, applications and technologies that are designed and developed so

    that people regardless of their situation, circumstances or ability can use them. w3c.org
  3. • About 1 billion of the world's population lives with

    some form of disability (World Health Organization) • 56 million live in the United States. (U.S Census) • 28 million use the Internet on a daily basis (Pew Research Center)
  4. BENEFITS FOR THOSE WITHOUT DISABILITIES Holding a Phone with one

    hand Watching a video in a coffeeshop A person who is inebriated A person who doesn’t want to put in their contact
  5. Web Content Accessibility Guidelines (WCAG) are a series of internationally

    recognized guidelines for improving web accessibility created by World Wide Web Consortium (W3C)
  6. FOUR PRINCIPLES OF WCAG • Perceivable: Users must be able

    to perceive the information being presented • Operable: Users must be able to operate the interface • Understandable: Users must be able to understand the information as well as the operation of the user interface • Robust: Users must be able to access the content as technologies advance WCAG 2.1 Guidelines
  7. WCAG LEVELS OF CONFORMANCE • Level A: The most basic

    web accessibility features • Level AA: Deals with the biggest and most common barriers for disabled users • Level AAA: The highest (and most complex) level of web accessibility
  8. WCAG 2.1 MOBILE SUCCESS CRITERIA • Orientation (AA) • Pointer

    Gestures (A) • Motion Actuation (A) • Pointer Cancellation (A) • Concurrent Input Mechanisms (AAA) • Target Size (AAA) • Label in Name (A) • Status Messages (AA)
  9. ANDROID A11Y FEATURES • TalkBack • Magnifier • High Contrast

    Text • Larger Text • Switch Control Android Accessibility Overview
  10. IOS

  11. IOS A11Y FEATURES • VoiceOver • Zoom • Magnifier •

    Invert Colors • Larger Text • Switch Control Accessibility on iOS
  12. MOBILE QA TEST CHECKLIST • Navigate page by semantic elements,

    i.e., using the VoiceOver Rotor, keyboard navigation, or explore-by-touch to select elements and hear their accessibility properties. • Tab, swipe, or arrow key through all elements. Make sure that you can access all elements in a logical way. • Set focus to each element to verify proper accessible name, role, value, and state is spoken by the screen reader. • Activate all dynamic controls using the screen reader only. • Activate all dynamic controls by using just a keyboard alone. • Check for proper keyboard focus order and focus visibility (this is different from screen reader focus, so disable the screen reader) • Enter blank and invalid values into forms to test error validation for accessibility. Are errors spoken aloud? Sanjay S. Nasta and Paul J. Adam