Arnold Loubriat

> I think we will have to update the widgets so that all accessible properties are set on the built-in element itself rather than the enclosing one This introduces a...

I'm trying to go with the approach described above to expose more kinds of widgets by checking the `TextInput::single_line` and `TextInput::input_type` properties in the AccessKit backend. This require updating some...

@tronical This idea also crossed my mind, but there is one point that I cannot solve. Ideally we'd want this new property to be replaced by appropriate property bindings at...

Nevermind, figured this out by myself: for each element referenced by this new property, the compiler will have to set all accessible properties on the referenced element that are set...

So I gave this a try but quickly ran into issues. What makes this more complicated is that `Element::is_binding_set` only considers bindings that are defined inside the element itself. To...

Your only option @sphw at the moment is to use window subclassing. We use it in AccessKit to return handles to COM interfaces in response to the `WM_GETOBJECT` message. You...

The core of AccessKit (that is, the accesskit crate) is no-std compatible since 0.17.0.

@bushrat011899 You might also want to update the section on bevy_window, since a feature is probably not needed anymore here? Having bevy_a11y run on as much devices as possible is...

Hello @bircni, I've updated the AccessKit crates here https://github.com/bircni/egui/pull/1. Could you merge please? Thanks.

If your comment at the top of `_update_root_window_focus` is true, then this might explain why. > This is not called the first time the window gets focused, but it really...