Mobile Site and Native App Accessibility Testing workshop (Part 2)

This is part 2 of a 2-part workshop. Part 1 is a prerequisite for participation in this part of the workshop.

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.

In this 3-hour Mobile Site and Native App Accessibility Testing Workshop, digital accessibility expert Gian Wild talks about the unique accessibility issues on mobile sites and mobile apps, including hover traps, VoiceOver swipe traps and zoom traps.

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 discusses the things that are essential to avoid when designing mobile apps, devices and wearables to ensure that everyone can use them.

This second 3-hour workshop will include a detailed review of the Mobile Site and Native App Accessibility Testing methodologies, including:

• Critical issues, such as keyboard traps, swipe traps, exit traps etc
• Mobile-specific issues, such as alternatives, display, actionable items, navigational aids, video and forms
• Mobile assistive technology and feature support, such as VoiceOver, TalkBack, Zoom, Invert Colors and Reader View
• Mobile and desktop relationship issues, such as providing links between desktop and m.dot sites and not restricting users to a particular version of the site

Each attendee will be provided with:

• The PowerPoint slides;
• The Mobile Site Accessibility Guidelines, along with test cases an example passes and fails;
• The Native App Accessibility Guidelines, along with test cases an example passes and fails;
• Links to articles; and
• Six months’ access to OzWiki, AccessibilityOz's database of accessibility errors, solutions, examples and code.

What attendees should bring:

• A mobile or tablet device
• Headphones
• Laptop
  

What participants will learn by attending Part 1 and Part 2 of this full-day workshop

• The importance of mobile accessibility
• How mobile accessibility differs from desktop accessibility
• What an inaccessible mobile site or native app looks like
• How to use assistive technologies, such as screen readers, grayscale and increase text on mobile devices
• How to test a mobile site or native app for accessibility compliance