Stop Treating Accessibility as an Afterthought: Concrete Steps to Build Inclusive Apps
summary
Argues that apps must meet WCAG 2.1 AA by June 28, 2025 and cites 1.3 billion people affected and a Domino’s settlement of $25,000 as concrete risk. Shows Flutter specifics: the semantics tree (not built by default on web), Semantics/Merge/Block/Exclude widgets, debugDumpSemanticsTree and visualizeSemantics, and the AccessibilityGuideline testing APIs. Recommends fixes like MediaQuery.textScaleFactor or text.rich for scaled fonts, dynamic sizing or scrollable boxes, 48×48 (Material) / 44×44 (Cupertino) tap targets, and tools Rebel App Studios and Google Accessibility Scanner. Semantics widget 25% scale fonts
AI-written summary · about
chapters (14)
- 0:00Introduction and personal story
- 2:35What is accessibility and why it matters
- 4:42WCAG 2.1 level double A compliance
- 6:09Flutter’s accessibility features
- 9:02How to identify accessibility issues
- 11:59Large fonts and text scaling
- 14:55Colors and contrast for vision impairments
- 17:23Screen reader experience and semantics
- 23:06Gestures and tap target areas
- 25:16Cognitive accessibility and content design
- 26:23Testing for accessibility in Flutter
- 29:57Adding accessibility to existing projects
- 31:45Voices of affected users and real-world examples
- 36:26Summary and call to action
related talks
19mAccessibility isn't hard; getting people to see it's easy can be with Sarrah Vesselov
12mAccessibility-First Development: Making Applications Inclusive from Day One
31mAfterthought: Concrete Steps to Build Inclusive Apps
33mEmbedding Accessibility
26mAccessibility Is a Marathon, not a Sprint
52mShop Accessible: Concrete Strategies for Procuring Accessible/Inaccessible Solutions
47mLessons learnt from building accessible complex web apps
16mMobile App Accessibility & Why It Is Important