4 ms·
Hi, lead developer of AccessKit here. I appreciate Emil's openness to integrating AccessKit, and to accessibility in general. Before AccessKit, egui had a parti
by mwcampbell 3y ago
Hi, lead developer of AccessKit here. I appreciate Emil's openness to integrating AccessKit, and to accessibility in general. Before AccessKit, egui had a partial accessibility solution based on direct text-to-speech output. Also, support for moving keyboard focus with Tab and Shift+Tab was already there. These things made it easier to implement proper platform accessibility support using AccessKit. IMO it's usable today on Windows and macOS, and we're working on Linux (or more generally, free desktop) support.
Edit to add: At the risk of self-promoting a bit more, I gave a talk about AccessKit at RustConf last September, and I used egui in the first demo. https://www.youtube.com/watch?v=LRBKb6McgqA https://www.youtube.com/watch?v=LRBKb6McgqA
- sbt567 3y agoThanks for creating AccessKit! It is awesome seeing an initiative to create a common library for such a fundamental building block for GUI
- isodev 3y agoHow does AccessKit actually work? For example, I opened https://www.egui.rs/#demo https://www.egui.rs/#demo and no parts of the interface were available via VoiceOver in the browser.
- mwcampbell 3y agoSorry, it's not implemented in the web version of eframe yet, only native. We started working on a web backend for AccessKit, but there are higher priorities. The ability to make a fully canvas-rendered web app practically accessible is limited anyway.
- isodev 3y agoThat's certainly an interesting challenge. But a web app which is not accessible is a show-stopper in general so it will be hard to use this for anything serious. Is it an ongoing effort? I couldn't find a lot of pointers in the repo on how one could try to contribute to move this along.