The future of Mobile Accessibility!
summary
WCAG 2.1 arrives June 2018 and adds concrete mobile rules: require portrait and landscape support, allow 400% zoom without horizontal scrolling, enforce text spacing and minimum touch targets of four to five by four to five pixels, and demand alternatives for motion-based controls. Visible text must lead the accessible name so voice control works, form fields must use autocomplete="given-name" / family-name and sites should adopt the Payment Request API for safer autofill.
AI-written summary · about
chapters (12)
- 0:00Introduction and speaker background
- 1:56WCAG evolution and mobile impact
- 4:04Mobile design requirements overview
- 7:02Target size and clickable areas
- 8:07Motion and alternative input methods
- 9:12Keyboard support and assumptions
- 10:20Labeling and accessible names
- 12:17Input purpose and autocomplete
- 14:54Web Payment API benefits
- 16:45Content customization and focus
- 17:31Accessible authentication methods
- 18:15Conclusion and Q&A
related talks
46mWCAG 2.1 What's new and what to do with it
44mHow to Use WCAG for Mobile Accessibility
54mWhat’s new in WCAG 2.1?
01h 09mBuilding Accessible Mobile Games and Native App Games for Accessibility
46mWhat WCAG 2.2 Means for Native Mobile Accessibility
34mIncrease Your Product Quality Through Accessibility
46mMobile accessibility - challenges and best practices
06mWeb Accessibility by 2025