Most Flutter developers have touched the Semantics widget at some point - usually to set a label on a custom button, or to mute a decorative image. The moment you hand your app to a real screen reader user, the gap between technically accessible and actually usable becomes clear: everything is read, nothing is broken, and yet some flows are, in practice, painful to get through.

This is ~1 year a11y work on prod banking app - the kind of app where a visually impaired user has to move money, confirm a transfer, and recover from a validation error with confidence.

We'll show the perspective of the people we’re actually building for: we’ve spoken with long-time screen reader users how they really use mobile apps, and we’ll bring their conclusions into the room - what is okay and what is a painpoint.

We'll also show a set of concrete production cases - form errors and focus, reading order, status announcements, the `GestureDetector` trap, and a few more - each tied to the WCAG rule.