> On 16 Dec 2025, at 13:32, Reza Bakhshi <[email protected]> wrote: > > Hi, > > I’d like to ask for feedback on a potential accessibility improvement in Qt. > > On Windows, screen readers rely on UI Automation properties such as > PositionInSet, SizeOfSet, and Level to announce group position information > (e.g. “option 1 of 4”). With our current setup, this information is not > exposed via Qt’s accessibility layer, so screen readers lose this context in > grouped controls (radio button groups, menus, lists, etc.). > > I have a prototype implementation for Qt 5.15.x that provides this > information via Windows UIA. Before turning it into an upstream contribution, > I’d like to ask: > - Is this feature something the Qt project would be interested in supporting? > - If yes, is there a preferred API/design approach for implementing it? > - Should I first file a Jira issue, and if so, under which component? > > Thanks for your time, > Reza
Hi Reza, Thanks for spotting this! Supporting this part of the UI Automation interface would indeed be interesting for our integration in Qt. I assume this can be implemented with the existing hierarchy-traversal APIs, although finding the position of a specific interface within its parent might be a comparatively expensive operation in very large lists (for instance in a tree view). A Jira ticket that documents what the expected outcome should be for different controls would be great; i.e. is “Level” something that we should expect from nested group boxes, or only from nested menus? The component for accessibility issues is “GUI: Accessibility (a11y)”. Given that you have a working implementation for UI Automation, it’s probably best to discuss possible approaches based on the existing patch. One thing to consider is whether this can/should be implemented across platforms, but that depends on whether the native a11y infrastructure on other platforms have that feature in the first place, or whether they use (or fall back to) existing tree-navigation infrastructure to get this information. Best regards, Volker -- Development mailing list [email protected] https://lists.qt-project.org/listinfo/development
