355
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 04 Nov 2026
355 points (95.9% liked)
Linux Gaming
28298 readers
1436 users here now
Discussions and news about gaming on the GNU/Linux family of operating systems (including the Steam Deck). Potentially a $HOME away from home for disgruntled /r/linux_gaming denizens of the redditarian demesne.
This page can be subscribed to via RSS.
Original /r/linux_gaming pengwing by uoou.
No memes/shitposts/low-effort posts, please.
That includes posts generated by LLMs. It doesn’t matter if you “don’t have the time” or “would’ve written the same anyway”, or if “everyone’s doing it geez get with the times”.
For now it’ll also include “AI”-assisted projects that haven't had at least two months of (public, verifiable) dev time behind them.
Resources
Help:
- ProtonDB
- Are We Anticheat Yet?
- r/linux_gaming FAQ
- Fork of an earlier version of the above
- PCGamingWiki
- LibreGameWiki
Launchers/Game Library Managers:
General:
Discord:
IRC:
Matrix:
Telegram:
founded 3 years ago
MODERATORS
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.
Without knowing what framework is in use its hard to say. Hell electron had accessibilty issues for a while