accessibility getting some resources
accessibility getting some resources
Posted Jun 20, 2025 17:49 UTC (Fri) by ebassi (subscriber, #54855)In reply to: accessibility getting some resources by linuxrocks123
Parent article: Enhancing screen-reader functionality in modern GNOME
The toolkit is involved, of course, and can fill in the basics for you; but GTK, or Qt, or any other toolkit cannot come up with a textual description for your own application's UI components. Or the relations between those components, especially once you write your own custom UI elements to group things, for instance. A toolkit cannot read your mind, or read the mind of the people using your application. We can have educated guesses about it, and encode them into the API, but failing an educated guess is worse than not putting anything in: the latter is, at least, invisible, while the former can lead to data loss.
Just like the web, GTK has authoring practices that application developers have to follow: https://docs.gtk.org/gtk4/section-accessibility.html#auth...
Posted Jun 21, 2025 2:56 UTC (Sat)
by linuxrocks123 (subscriber, #34648)
[Link]
No, just like the W3C, GTK has written some words that almost nobody actually pays any attention to.
accessibility getting some resources