https://bugs.documentfoundation.org/show_bug.cgi?id=155447
Michael Weghorn <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Ever confirmed|0 |1 Status|UNCONFIRMED |NEEDINFO --- Comment #11 from Michael Weghorn <[email protected]> --- (In reply to Michael Weghorn from comment #7) > > It sounds like API specifically for tools/uses that are NOT screen readers. > > I don't think this is set in stone, and the doc for the ATK equivalent is > not restricted to testing either, so I think it makes sense to adjust the > AT-SPI XML documentation as well. Pending MR: > https://gitlab.gnome.org/GNOME/at-spi2-core/-/merge_requests/161 > > From an implementation perspective, using the AccessibleId would IMHO have > the advantage that it wouldn't require introducing new object attributes and > there's already existing API to easily set that for ATK, GTK 3 and Qt at > least. The at-spi2-core MR has been merged and with the commits from comments 8 to 10 in place, accessible IDs are now set for both, gtk3 and qt6. "SpellingDialog" is the accessible ID for the dialog. Orca MR demonstrating how this can be used: https://gitlab.gnome.org/GNOME/orca/-/merge_requests/220 If considered a proper solution, this could be extended to also use the accessible ID for the individual components in the dialog. Then: probably makes sense to agree on proper IDs and ideally add a test case to prevent unnoticed change. GTK 4 issue suggesting to support accessible ID there as well: https://gitlab.gnome.org/GNOME/gtk/-/issues/6870 @joanie: What do you think? -- You are receiving this mail because: You are the assignee for the bug.
