Fun! I’ll get to moderate a Discord server for blind people that blind people can’t use on desktop!
How would a rewrite cause this to happen? Is there something about Rust frameworks for the desktop that exclude accessibility features?
I’ve been working primarily with C#, but none of their frameworks exclude accessibility features… would be shocked AF if Rust frameworks just left that all out.
Yeah, but this is Rust, not some single-dev pet project. You would expect a fully fleshed out framework to have accessibility features built in as first-class features, not some randomly bolted-on afterthought.
Fun! I’ll get to moderate a Discord server for blind people that blind people can’t use on desktop!
Seriously, anything on GPUI reads as “empty window” to screen readers.
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?
How would a rewrite cause this to happen? Is there something about Rust frameworks for the desktop that exclude accessibility features?
I’ve been working primarily with C#, but none of their frameworks exclude accessibility features… would be shocked AF if Rust frameworks just left that all out.
I checked the gpui crate and it has an accessibility module that uses AccessKit, but I can’t say if it actually works.
Yeah, but this is Rust, not some single-dev pet project. You would expect a fully fleshed out framework to have accessibility features built in as first-class features, not some randomly bolted-on afterthought.
Without knowing what framework is in use its hard to say. Hell electron had accessibilty issues for a while
they literally explained the problem in the second sentence of their comment: