What WCAG 2.2 Means for Native Mobile Accessibility
summary
WCAG 2.2 adds 9 new success criteria and the session translates them to native apps with concrete guidance: focus must remain visible (2.4.11/12) and meet size and contrast rules, drag‑and‑drop needs an alternative because dragging movement not scrolling (2.5.7), and touch targets must be at least 24px minimum / 44px recommended with listed exceptions. Android and iOS accessibility APIs already handle many focus issues and Deque’s mobile tooling already flags touch target violations.
AI-written summary · about
chapters (11)
- 0:00Introductions and agenda
- 3:18History of WCAG
- 7:11WCAG in native mobile apps
- 15:24Overview of WCAG 2.2
- 16:22Focus appearance criteria
- 22:04Focus appearance standards
- 24:28Dragging movements
- 28:52Dragging movement details
- 31:04Touch target size
- 38:14Consistent help
- 40:17Q&A session
related talks
46mWCAG 2.1 What's new and what to do with it
54mWhat’s new in WCAG 2.1?
44mHow to Use WCAG for Mobile Accessibility
19mThe future of Mobile Accessibility!
17mAccessibility in Mobile Apps
01h 09mBuilding Accessible Mobile Games and Native App Games for Accessibility
50mWCAG 2.2 and 3.0 Update
34mIncrease Your Product Quality Through Accessibility