How to win at mobile accessibility
summary
Focuses on concrete wins: prioritizes iOS and Android screen‑reader behaviour, shows breakable patterns (CNN hamburger, Huge off‑screen panels, Ionic swipe conflicts) and fixes that work — use HTML button over div, label icons with aria‑labels, and hide background regions with aria-hidden + tabindex="-1". Demonstrates testing workflows: tethered device inspection in Chrome, Firefox WebIDE and the Axe extension; evaluates whether fixes actually remove items from the accessibility tree and restore usable tab order.
AI-written summary · about
chapters (25)
- 0:00Intro
- 2:46Mobile++
- 4:48Why should I bother? Sales potential
- 5:59Develop for future you
- 6:52Mobile Platform Usage in Accessibility
- 7:55Do you use a mobile screen reader more than a desktop screen reader?
- 12:43Text is too small
- 13:29Visual clutter
- 15:40Conflicting gestures
- 19:52Winning?
- 20:35You're competing...
- 21:10BBC Mobile Accessibility Guidelines
- 21:48Use buttons
- 22:45Label buttons and controls
- 23:46Touch targets
- 25:23Crafting mobile tab order
- 28:10Hidden links shouldn't be reachable
- 30:51Disabling interactive elements in HTML
- 31:59Content properly disabled
- 33:10What We Have vs. What We Want
- 33:49iOS Safari with Accessibility Node Inspector
- 34:14Safari Accessibility Audit?
- 35:52Firefox WebIDE: Add-ons?
- 36:46Chrome Accessibility Developer Tools + Android Tethering
- 37:22Let's Recap Accessibility is important
related talks
46mMobile accessibility - challenges and best practices
53mDoing Responsive Right: Accessibility Lessons from the Field
44mCrafting Great Accessible Experiences
26mAccessibility Is a Marathon, not a Sprint
50mMobile accessibility: testing mobile sites and native apps for accessibility
29mAccessibility first is the new Mobile first
26mHow to Catch Low-Hanging Accessibility Fruits while Developing
31mDecoding web accessibility through testing