Navigating the Roadblocks to European Accessibility Act
summary
Explains how a legacy Android app is brought toward EAA compliance with concrete results: EU deadline 28 June 2025 and 5‑year transition; audited against WCAG A/AA, 23.9% EU activity limitation cited, and apps must allow 200% text resize and rotation. Demonstrates building a fake malicious accessibility service to prove attack vectors, then protecting inputs using Android 14’s sensitive view flag and Compose semantics. Shows fixes for focus order, keyboard/switch support, minimum touch targets, and a pragmatic ellipsize+expand Top App Bar pattern that keeps TalkBack and keyboard behavior correct.
AI-written summary · about
chapters (19)
- 0:00Introduction
- 1:04Why accessibility matters
- 3:13Business case for inclusion
- 7:26European Accessibility Act
- 10:37Key documents and standards
- 12:23WCAG levels A, AA, AAA
- 13:08Text alternatives and descriptions
- 16:19Alternative input and keyboard
- 18:04Name, role, value for UI
- 20:32Orientation flexibility
- 22:39Resizing text without loss
- 24:44Meaningful sequence and focus
- 27:47Testing with assistive tech
- 28:08Target size and touch
- 30:17Security risks and accessibility
- 31:42Protecting data with Android 14
- 32:45Top app bars challenges
- 35:34Creative accessibility solutions
- 35:56Q&A
related talks
48mNavigating the Roadblocks to EAA Compliance
15mAccess-what? why and how. A11Y for all
19mAre you ready for the European Accessibility Act Enforcement in 2025?
36mRaise accessibility awareness at work as an Android developer
31mAfterthought: Concrete Steps to Build Inclusive Apps
43mAccessibility Made Simple
48mAccessibility is not rocket science!
32mMaking Android accessibility easy