From 32144d3cb9e236a0cb3d4980c9617b24504d891f Mon Sep 17 00:00:00 2001 From: Matt Campbell Date: Mon, 5 Dec 2022 13:40:01 -0600 Subject: [PATCH] Update README section on accessibility (#2392) --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index ac43a9ed..87d8b1de 100644 --- a/README.md +++ b/README.md @@ -322,9 +322,9 @@ If you call `.await` in your GUI code, the UI will freeze, which is very bad UX. * [`tokio::sync::watch::channel`](https://docs.rs/tokio/latest/tokio/sync/watch/fn.channel.html) ### What about accessibility, such as screen readers? -There is experimental support for a screen reader. In [the web demo](https://www.egui.rs/#demo) you can enable it in the "Backend" tab. +egui includes optional support for [AccessKit](https://accesskit.dev/), which currently implements the native accessibility APIs on Windows and macOS. This feature is enabled by default in eframe. For platforms that AccessKit doesn't yet support, including web, there is an experimental built-in screen reader; in [the web demo](https://www.egui.rs/#demo) you can enable it in the "Backend" tab. -Read more at . +The original discussion of accessibility in egui is at . Now that AccessKit support is merged, providing a strong foundation for future accessibility work, please open new issues on specific accessibility problems. ### What is the difference between [egui](https://docs.rs/egui) and [eframe](https://github.com/emilk/egui/tree/master/crates/eframe)?