wxStyledTextCtrl isn't accessible with MacOS voiceover screenreader (Issue #26652)
Daniil-Gusev
Daniil-Gusev created an issue (wxWidgets/wxWidgets#26652)See #16863.
The issue seems to be present on MacOS as well: wxStyledTextCtrl isn't detected by voiceover.
I'm using wxWidgets v3.3.2, a port of wx cocoa.
Any ideas?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS and Android. Download it today!
You are receiving this because you are subscribed to this thread.
VZ
vadz left a comment (wxWidgets/wxWidgets#26652)Unfortunately I don't know much about accessibility under macOS so we would need help with fixing this.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS and Android. Download it today!
You are receiving this because you are subscribed to this thread.
Maarten
MaartenBent left a comment (wxWidgets/wxWidgets#26652)I suppose the NSAccessibility functions will need to be implemented somewhere, but I have no idea where (PlatWXcocoa.mm?) and how.
Similar to what Scite does (from line 988): https://sourceforge.net/p/scintilla/code/ci/default/tree/cocoa/ScintillaView.mm
—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS and Android. Download it today!
You are receiving this because you are subscribed to this thread.
Joshua Lee Ockert
torstenvl left a comment (wxWidgets/wxWidgets#26652)wxAccessible is unfortunately only implemented on Windows for now. See: https://forums.wxwidgets.org/viewtopic.php?t=4351
I am interested in broadening wxWidgets Accessibility, and I've been looking into it as part of my work on wxRichTextCtrl (for which the existing wxAccessible implementation based on the MSAA/IAccessible API is insufficient even on Windows). But it's a lot of work, with a lot of legacy API and ABI concerns, and I have a very busy full-time job.
I also don't really know enough about macOS ABI to know off the top of my head if the concerns are the same. It's POSSIBLE that the message-passing nature of ObjC means this be handled without breaking ABI the way messing with C++ object vtables can. I would need to research and think about that a lot before giving an intelligent answer.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS and Android. Download it today!
You are receiving this because you are subscribed to this thread.
Daniil-Gusev
Daniil-Gusev left a comment (wxWidgets/wxWidgets#26652)In any case, thank you for any work you do on this. I'm unlikely to be able to help you with the code at this stage, but if needed, please feel free to mention me, and I'll be happy to test patches.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS and Android. Download it today!
You are receiving this because you are subscribed to this thread.
Joshua Lee Ockert
torstenvl left a comment (wxWidgets/wxWidgets#26652)I got a minimal proof of concept for macOS using wxAccessible working last weekend. The NSAccessibility implementation shouldn't break ABI, but wiring it up does.
Currently, there is an ABI break between accessible builds and non-accessible builds, because the very existence of the wxAccessible * on wxWindowBase is gated behind wxUSE_ACCESSIBILITY. As a result, sizeof(wxWindow) changes based on the compile-time options.
@vadz I recommend that for 3.4, the wxAccessible * and related virtuals be ungated, and be part of wxWindowBase regardless of compile-time options. This will maintain ABI of wxWindow; instead, we can use wxUSE_ACCESSIBLE to gate the implementation methods, reducing them to stubs when accessibility is turned off and compiling the accessibility implementation in when it's turned on. This will in turn allow us to make accessibility improvements on Mac and Windows (and maybe GTK?) throughout the 3.4.x lifecycle.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS and Android. Download it today!
You are receiving this because you are subscribed to this thread.