4 ms·
Call me back when Flutter can have an always-on accessibility system that doesn’t tank performance[1] (self-admitted!) and we can talk about potentially being r
by robin_reala 2y ago
Call me back when Flutter can have an always-on accessibility system that doesn’t tank performance[1] (self-admitted!) and we can talk about potentially being ready for use in a production system.
[1] https://medium.com/flutter/accessibility-in-flutter-on-the-web-51bfc558b7d3 https://medium.com/flutter/accessibility-in-flutter-on-the-w...
- satvikpendem 2y agoI wonder how native iOS and Android solve it, wouldn't they also have a similar performance problem? I haven't delved too deep into the problem however so not sure myself.
- xster 2y agoMay I ask what the use case is? What would you do with it besides using it for a screen reader (which turns it on)
- robin_reala 2y agoA screen-reader user (or Braille display, any assistive tech that engages with the accessibility tree) deserves access to both an automatic system that doesn’t require them to engage a specific mode, and to a system that is as fast as any other. If your production system can’t do that because of your tech decisions then you’ve made the wrong decisions, given the plethora of other choices you could have made that don’t make that sacrifice.