35 ms·
> compared to other desktop or mobile apps, there is literally no difference between rendering on a canvas to rendering on Qt or SwiftUI. Except, you know, acc
by troupo 3y ago
> compared to other desktop or mobile apps, there is literally no difference between rendering on a canvas to rendering on Qt or SwiftUI.
Except, you know, accessibility.
> just get up in arms about the web that does not happen with other technologies.
And for a good reason.
- frabcus 3y agoFlutter has a wild accessibility system that also exports DOM elements just for the aria labels. This all breaks the browser’s in page search function though! Long standing bug with no fix yet.
- satvikpendem 3y agoDo you realize that Flutter has an accessibility system that is often more advanced than most desktop UI frameworks? [0] I notice this often from non-Flutter devs, Flutter has some pretty good a11y. [0] https://docs.flutter.dev/accessibility-and-localization/accessibility https://docs.flutter.dev/accessibility-and-localization/acce...
- troupo 3y agoGood to know! For the longest time ever their export to web was just canvas with no attempt at making it accessible.
- mhoad 3y agoI don’t know if even that was actually true? As far as I know the moment they introduced canvas as a rendering target they also produced a DOM structure along side it to capture the accessibility tree as they were still waiting on a more native solution in the form of AOM (accessibility object model) to be finalised.