Stop Treating Accessibility as an Afterthought: Concrete Steps to Build Inclusive Apps
summary
Accessibility is framed as concrete Flutter practice: target WCAG 2.1 AA (legal risk in EU/US/UK), test with Flutter’s AccessibilityGuideline class and the non‑fuzzy matchSemantics matcher, simulate traversal to verify sortKey ordering, and use MediaQuery textScaleFactor checks for large fonts. Use Semantics widget, MergeSemantics, BlockSemantics and ExcludeSemantics to control what screen readers see, enable showSemanticsDebugger to visualize nodes, and note Flutter web requires an invisible button to build the semantics tree for screen readers.
AI-written summary · about
chapters (8)
- 0:00Introduction to accessibility
- 1:12Why accessibility matters
- 2:45Flutter’s accessibility support
- 4:11Semantics in Flutter apps
- 7:06Semantics widget properties
- 10:37Testing for accessibility
- 13:26Adding accessibility to projects
- 14:53Call to action and resources
related talks
31mAfterthought: Concrete Steps to Build Inclusive Apps
27mFrom Widget to World Making Flutter Apps Truly Inclusive
32mLessons Learned from Adding Accessibility to a Flutter Web App
33mAccessibility in Flutter
40mGetting started with mobile accessibility: iOS, Android, and Flutter
15mTesting that your app is accessible to all
49mAccessibility of Flutter Apps, or How to Increase Traffic by 20%
52mCommon Accessibility Pitfalls