I haven’t messed with Tauri, but I’m not very hopeful. My best case scenario right now is for Discord to continue upstream accessibility work. To be clear, there is an edit for GPUI, but it still seems to be in early stages.
Speaking of framework maturity, last I looked at OBS on Qt6 it still had significant issues. You need the OS accessibility API, the framework to hook into it and the developer knowledge on how to leverage that. It’s a lot of ifs that can fail early.
Thanks for answering. Trying to keep my software as accessible as possible with regards to colors and structure, but screen readers are a bit beyond my competency.
The first step is to make sure it’s keyboard accessible, since that’s how blind people will use your software. Tab, arrows, space, enter should get you to most things and trigger controls. Ctrl + tab for some things, F6 typically moves focus between panes.
Apart from that, you can always turn on your own screen reader. Windows comes with Narrator, macOS with VoiceOver and most Linux distros will come with Orca. Mind you, you’ll have to learn a lot and the fact you can’t do something doesn’t mean an experienced screen reader user can’t, but you’ll get some feedback pretty quickly.
That’s actually an excellent point. I can just use the text-to-speech screen reader, and the same content will go to a physical screen reader. I’ll try that!
Well that sucks. Do you know if Tauri is any better in that regard?
Unrelated to Rust, I assume Qt6 has the expected accessibility features wired?
I haven’t messed with Tauri, but I’m not very hopeful. My best case scenario right now is for Discord to continue upstream accessibility work. To be clear, there is an edit for GPUI, but it still seems to be in early stages.
Speaking of framework maturity, last I looked at OBS on Qt6 it still had significant issues. You need the OS accessibility API, the framework to hook into it and the developer knowledge on how to leverage that. It’s a lot of ifs that can fail early.
Thanks for answering. Trying to keep my software as accessible as possible with regards to colors and structure, but screen readers are a bit beyond my competency.
The first step is to make sure it’s keyboard accessible, since that’s how blind people will use your software. Tab, arrows, space, enter should get you to most things and trigger controls. Ctrl + tab for some things, F6 typically moves focus between panes.
Apart from that, you can always turn on your own screen reader. Windows comes with Narrator, macOS with VoiceOver and most Linux distros will come with Orca. Mind you, you’ll have to learn a lot and the fact you can’t do something doesn’t mean an experienced screen reader user can’t, but you’ll get some feedback pretty quickly.
That’s actually an excellent point. I can just use the text-to-speech screen reader, and the same content will go to a physical screen reader. I’ll try that!