How to Use WCAG for Mobile Accessibility
summary
Mobile Accessibility Task Force publishes a draft of mobile best practices and a GitHub repo with weekly updates and a research wiki. It proposes WCAG 2.1 additions: touch and pointer rules (all touch functions must remain usable when platform assistive tech remaps gestures; failures include infinite-scroll that cannot be closed), a 44×44 CSS-pixel target recommendation (20×20 for precise pointers under discussion), activation-on-up or undo/confirm alternatives, device-manipulation fallbacks, speech-input and orientation rules, and honoring platform accessibility settings.
AI-written summary · about
chapters (28)
- 0:00Intro
- 0:45Welcome
- 2:15What is mobile
- 2:55What is mobile technology
- 4:48Mobile landscape
- 7:43What is mobile accessibility
- 10:09Mobile accessibility isnt just mobile
- 11:38What WCAG does apply for mobile
- 12:30Mobile Accessibility Task Force
- 15:01Mobile Accessibility Techniques
- 16:10Mobile Accessibility Best Practices
- 18:37Structure
- 19:04Table of Contents
- 19:34New Guidelines
- 20:25Touch and Pointer
- 21:30All About Touch
- 24:02No Touch
- 25:29Accidental Activation
- 27:43Button Size
- 29:50Device Manipulation
- 32:05Speech Input
- 33:56Device Orientation
- 36:11Interactive Elements
- 37:33Assistive Technology
- 39:02Mobile Accessibility Extension
- 41:46Next Steps
- 42:27Feedback
- 42:59Questions
related talks
19mThe future of Mobile Accessibility!
46mWCAG 2.1 What's new and what to do with it
01h 09mBuilding Accessible Mobile Games and Native App Games for Accessibility
54mWhat’s new in WCAG 2.1?
46mWhat WCAG 2.2 Means for Native Mobile Accessibility
17mAccessibility in Mobile Apps
34mIncrease Your Product Quality Through Accessibility
46mMobile accessibility - challenges and best practices