Afterthought: Concrete Steps to Build Inclusive Apps
summary
Covers concrete checks and fixes: EU Accessibility Act forces new apps from 2025, target WCAG 2.2 AA, and about 25% of users scale fonts. Shows tools and code: Accessibility Tools (Rebel App Studios), Google Accessibility Scanner, how to enable Flutter web semantics in main, and using debugDumpSemanticsTree and showSemanticsDebugger. Demonstrates widgets to use—Semantics widget, SortKey, MergeSemantics, ExcludeSemantics, BlockSemantics—testing tips (set textScaleFactor, contrast 4.5:1 or 3:1 for large text, 44–48px tap targets) and real failures like Instagram story and Snapchat dead‑end examples.
AI-written summary · about
chapters (18)
- 0:00Introduction
- 1:47Personal story on inclusion
- 3:35What accessibility means
- 5:44Flutter’s accessibility features
- 8:56Enabling accessibility in Flutter web
- 10:00Performing an accessibility audit
- 12:25Testing large fonts
- 14:11Color vision impairments and contrast
- 15:40Screen reader experience
- 17:08Customizing screen reader order
- 18:35Semantics widgets for UX
- 20:25Gestures and tap accessibility
- 21:28Cognitive accessibility
- 22:57Automated accessibility testing
- 25:07Testing process
- 25:50Team communication and checklists
- 27:35User testing real issues
- 30:29Call to action
related talks
17mStop Treating Accessibility as an Afterthought: Concrete Steps to Build Inclusive Apps
27mFrom Widget to World Making Flutter Apps Truly Inclusive
15mTesting that your app is accessible to all
40mGetting started with mobile accessibility: iOS, Android, and Flutter
36mNavigating the Roadblocks to European Accessibility Act
44mCrafting Great Accessible Experiences
46mMobile accessibility - challenges and best practices
42mArchitecting for Accessibility