It legitimately angers me that Google claim any sort of robust #accessibility support in their half-baked #Flutter UI toolkit. From the need for users to manually enable an accessible mode in web apps, to the use of accessible names to convey role information on mobile, to a borderline unusable keyboard experience on Windows, it is a rotten mess throughout.
James Scholes
in reply to James Scholes • • •Just had a session with an app team who've developed with Flutter. On Windows they have a pretty basic landing screen: a language selector button, two columns of text, an input field and a submit button, and a link.
We spent 30 minutes just breaking down all the ways it is unusable with NVDA, and I do mean that in the truest sense of the word. Without object navigation, you can't reach most of the context and controls. Even when you manage to reach e.g. the submit button, pressing Space or Enter on it does nothing.
I feel bad for the team, but Google should feel worse. #accessibility
reshared this
André Polykanine and Federico Mena Quintero reshared this.
aaron
in reply to James Scholes • • •