Iced itself appears to be largely an API definition (and project to implement that API), there's currently two largely independent backends - iced_winit and ice

Iced itself appears to be largely an API definition (and project to implement that API), there's currently two largely independent backends - iced_winit and iced_web. They provide their own widget structs, event loops, and so on. There's therefore enough of an abstraction which could be used to get Iced to create Windows/Cocoa/GTK/Qt native widgets (in much the same way it currently creates VDOM elements for the web, thus getting some level of accessibility by default). Then Iced could provide additional a11y information to the backend by means of properties on the virtual objects.