Building Accessible Mobile Games and Native App Games for Accessibility
summary
Argues that WCAG2.1 is insufficient for phones, points to a Creative Commons Mobile Site Testing Guidelines that list concrete tests: TalkBack and VoiceOver, zoom, pinch zoom, reduce motion, grayscale, voice control and haptic keyboards. Defines five real traps (exit, swipe‑scroll, text‑to‑speech, headset, layer) with failing examples: YouTube hides upload at 200% text, New York Times games expose missing accessible names and scrambled keyboard order, and touch target size is still only AAA in WCAG. Recommends testing on real devices.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 5:00Mobile accessibility guidelines
- 13:08Mobile vs desktop accessibility
- 21:37Testing mobile apps
- 26:20Site types for accessibility
- 30:58Common accessibility traps
- 36:24Mobile accessibility issues
- 40:12Testing with assistive tech
- 44:50Future mobile accessibility
- 47:19Q&A
related talks
50mMobile accessibility: testing mobile sites and native apps for accessibility
46mMobile accessibility - challenges and best practices
20mHow to make your mobile games more accessible to people with disabilities
51mAccessible UX: Going beyond WCAG
33mAccessibility needs to be the future of better technology
19mThe future of Mobile Accessibility!
44mHow to Use WCAG for Mobile Accessibility
42mArchitecting for Accessibility