> Applications, especially desktop applications, are nothing like that. Seperations of concerns gains you very little there. I think you are making critical mi

> Applications, especially desktop applications, are nothing like that. Seperations of concerns gains you very little there. I think you are making critical mistake here. IAccessible & Co. (https://docs.microsoft.com/en-us/windows/win32/api/oleacc/nn-oleacc-iaccessible https://docs.microsoft.com/en-us/windows/win32/api/oleacc/nn...) maps nearly directly onto HTML DOM tree. So no matter what CSS you have there your UI will accessible. The thing is that accessibility works acceptable only on semantic DOM trees. HTML and its DOM was designed with that in mind. Flutter's DOM is not, it is not semantic - it is a Dart code that defines visual structure for particular screen layout. Mobile applications are significantly less demanding (more simple in UI terms) - they have very reduced set of components and layouts. Essentially all mobile UIs are built with <radio>,<checkbox>,<button> and <list> vocabulary. The reason is simple: most of the time mobile apps are serving "reading user" role. While desktop is the place for "writing user"s (a.k.a "content generation" role). Desktop is the place where you must support different editing, object manipulation paradigms - UI on desktop is more rich. Just check apps on your mobile - 90% of them are very close UI-wise.