It's really unfortunate that a ton of the new GUI libraries out there for newer programming languages like Rust or Zig have left accessibility as a long-term goal instead of something core to the project.
@brainblasted and most likely it'll never happen, if nothing else because their über idiomatic micro-optimised buzzwordy architecture is probably entirely at odds with AT-SPI etc
@brainblasted Actually, people have tried with egui, but it seems the results are not great https://www.reddit.com/r/rust/comments/wippxd/comment/ijdjpu7/?utm_source=share&utm_medium=web2x&context=3
@brainblasted I started documenting the XML interfaces recently and will keep doing that - then I really want to write a "how to make your toolkit accessible" manual.
@brainblasted Aren't a lot of these just wrappers around GTK and suchlike? I'm not super-familiar with their respective ecosystems though, so I could be wrong.
@brainblasted Also a lot of them seem to aim for GPU acceleration and I don't wanna live in a future where I need OpenGL to render everything. Being able to run the software on old/cheap hardware is an accessibility consideration too.
- Making people buy new hardware has emissions costs too.
- A GUI that minimize updates and runs on e-ink screens will always beat animated GUIs that require a high refresh high DPI screen.
@brainblasted that's just one of the many reasons why I stick with Gtk+, even if it is written in C. The Rust bindings are actually quite nice at this point.
I've used Gtk in Zig as well, but it's quite a bit more work.
The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!