Matt Campbell

wxWidgets basically dodges the whole accessibility problem by using the native widgets on each platform.

@camlorn Kivy's [pyjnius](https://github.com/kivy/pyjnius) project has already solved the problem of implementing JNI interfaces from Python. So that specific problem is not a barrier to implementing Android accessibility in Kivy. I...

It seems to me that the work of implementing platform accessibility APIs belongs in the main Kivy project, not Plyer, since it needs to be an integral part of the...

I'm a newcomer to Kivy, so anything I say about project structure should be taken with a grain of salt. But there is already a precedent for using pyjnius and...

Thanks @maroider for working on this. I'll settle for having a separate `accesskit_winit` crate rather than having any of my existing crates depend directly on winit. I assume the `*mut...

I like the idea of using `WindowId`. Among other benefits, it's hashable, so my code will be able to look up its own struct associated with the window.

This all sounds good. For what it's worth, AccessKit for Mac will need to override some methods on the `NSView` object. I'm not yet sure which ones.

FWIW, initializing accessibility inside the call to `CreateWindowExW` only seems to be necessary if the window is created with the `WS_VISIBLE` style already set. If the window is created hidden,...

@maroider Have you had a chance to do any work on this lately? I'm starting up work on AccessKit again, and I want to be able to use it in...

The `HWND` can be obtained through the `WM_NCCREATE` and `WM_CREATE` messages, which are sent during the call to `CreateWindowExW`. I'm not sure about the practical differences between those two messages.