[jamesgeck0]

Under project scope, there's this statement:

> To name just a few things you usually don't need: ... flawless i18n & accessibility

Lack of basic accessibility support is (or should be) a complete nonstarter for any serious project.

[DonHopkins]

I'd demand better than basic accessibility support!

https://www.youtube.com/watch?v=GwSh0dAaqIA

[cztomsik]

you can join the effort and help me, the scope is limited to something I can do myself in reasonable time :-)

[Macha]

This is ultimately why I went with gtk in a recent Rust project. Qt bindings are a pain, and the license stuff was coming out. But most of the native Rust GUI libraries don't even try. Maybe its a maturity thing and they'll get there but I picked GTK for now

[mwcampbell]

Note though that GTK has no accessibility support on Windows and Mac. If you're only targeting GNOME, then that's fine. For something that's more or less accessible cross-platform, I'd go with wxWidgets or something Web-based.

[gmueckl]

Also, what is "flawless" i18n support?

[cztomsik]

To have what browsers do. And getting there would take few months on its own so it's not a priority right now.