Are screen readers capable of reading interfaces generated with QT or other desktop UI toolkits?
A cursory look at QT's documentation seems to indicate that they are aware of screen readers, but I didn't dig deeply enough to find out if they were compatible by default.
I know VoiceOver on OSX can at least read out the interfaces on the included apps, but I also don't know if that's true for every app---or if it actually extends to the browser and canvas/plugin rendered (flash, java, etc.) interfaces.
As an addendum, I'm pretty hopeful that in this decade we'll get AI vision enabled screen readers so anything that's displayable to a sighted person can also be immediately used with some caveats by someone reliant on screen reader.
> Are screen readers capable of reading interfaces generated with QT or other desktop UI toolkits?
Qt is one of the very few UI toolkits that is more or less accessible. And even Qt's accessibility implementation isn't great. My advice for someone implementing a cross-platform desktop app would be to go with something based on the web platform. That doesn't have to be Electron; Tauri [1] looks promising, though I haven't tested it lately.
> As an addendum, I'm pretty hopeful that in this decade we'll get AI vision enabled screen readers so anything that's displayable to a sighted person can also be immediately used with some caveats by someone reliant on screen reader.
Sadly, that might be what it takes to get access to applications using the long tail of UI toolkits.
This is a major challenge in the Move Fast and Break Things javascript world of half baked UI frameworka that arent accessible.
The problem with AI screen readers (Android already has one) is that they provide a "good enough" solution that drains the interest in building server frameworms that really work.
The pre-announcement [1] lays out at least some of those alternatives. I understand why they chose the approach they did, but they needed to do the work to make it accessible, as I advised them when that post came out.
