Arnold Loubriat

The Vizia example uses winit and accesskit_winit to install accessibility on the window. There is currently no AccessKit adapter for the baseview crate, so no accessibility tree is exposed. Writing...

To install accessibility on a window using subclassing, you have to first create the window hidden, install AccessKit hooks then show the window. This is fine for regular apps but...

@Timtam baseview is the one responsible for managing the window and accessibility is tied to the window (on Windows and macOS). No matter which UI toolkit you use, if the...

@Timtam opening an issue towards the baseview repository would indeed be a good way to start the discussion. Feel free to mention me over there so I can add the...

Hello @lukexor, thanks for trying out AccessKit. The issue you describe here might be linked to the fact that the version of accesskit_unix used by egui doesn't implement lazy initialization,...

This was probably a Rust bug, see https://github.com/bevyengine/bevy/issues/14956.

Would it make sense to set `indent_string` to a tab so that toml files are indented like the rest of the code base?

I'm not even sure exposing features to pick your async runtime is needed here. I can't find any code path specifically for one runtime or the other therefore the atspi...

Thanks @RastislavKish for your continued support on my accessibility endeavors. The last improvement related to text input probably was my pull request to add support for placeholder text. I don't...

Two points @tronical: - For AccessKit, each span of text must be a node with `Role::TextRun` and these nodes must be direct children of the text input node. Since the...