Possible regression: wx.Accessible causes screen readers to announce generic labels if wx.Control name kwarg is empty
Hi Robin and others,
A few months ago someone asked how one can improve accessibility of wx.Grid for screen reader users, and wx.Accessible wrapper was added as a result. However, it appears that, in real world it has created a severe regression for screen reader users and developers (I’m a screen reader dev myself).
Specifically, as documented in the following issue:
When I run NonVisual Desktop Access (NVDA) with wxPython 4.0.4 installed, NVDA and Narrator announces generic control role labels for controls with empty string for name kwarg argument. This was confirmed by a colleague of mine (another NVDA code contributor), who also used Microsoft’s Inspect tool to check accessibility implementation of wxWidgets 4.0.4 apps. My colleague suggests letting widgets choose whether they wish to use native versus wxPython MSAA server implementation on individual cases.
Also, while we’re at it, if possible, can you ask upstream wxWidgets devs to contact screen reader developers (Microsoft, NV Access, Vispero, etc.) about proper accessibility API server implementations, and for benefit of all screen readers that supports it, a wxUIA (UI Automation) server implementation in the future? If wxUIA is implemented, this would benefit Narrator in particular, because in Windows 10, Narrator (from Microsoft) prefers UI Automation.
You received this message because you are subscribed to the Google Groups "wxPython-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/d/optout.