GNOME Bugzilla – Bug 651349
Identify recommended hierarchies for complex(ish) widgets, then document best practice
Last modified: 2021-06-10 11:25:48 UTC
When implementing the accessibility representations for widgets, it is good if all implementations follow some schemes. To make it easier for the client side, we propose a few ways of representing widgets where the structure is not really clear. While we cannot "enforce" its use, hopefully by identifying a complete, useful set of hierarchies which are well-documented, we can convince implementors that it is the right thing to do. :-)
Note: This work began at the ATK hackfest and the current state can be found on https://live.gnome.org/Hackfests/ATK2011/Agenda/widgets-best-practices.
Note: AtkTable already has a dedicated bug (bug 639479).
[Mass-reassigning open atk bug reports for better trackability as requested in https://bugzilla.gnome.org/show_bug.cgi?id=653179 .
If you have watched the previous assignee of this bug report as a workaround for actually getting notified of changes in atk bugs, you yourself will now have to add email@example.com to your watchlist at the bottom of https://bugzilla.gnome.org/userprefs.cgi?tab=email to keep watching atk bug reports in GNOME Bugzilla.
Sorry for the noise: Feel free to filter for this comment in order to mass-delete the triggered bugmail.]
GNOME is going to shut down bugzilla.gnome.org in favor of gitlab.gnome.org.
As part of that, we are mass-closing older open tickets in bugzilla.gnome.org
which have not seen updates for a longer time (resources are unfortunately
quite limited so not every ticket can get handled).
If you can still reproduce the situation described in this ticket in a recent
and supported software version of atk, then please follow
and create a ticket at
Thank you for your understanding and your help.