After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 651349 - Identify recommended hierarchies for complex(ish) widgets, then document best practice
Identify recommended hierarchies for complex(ish) widgets, then document best...
Product: atk
Classification: Platform
Component: atk
Other All
: Normal enhancement
: ---
Assigned To: ATK maintainer(s)
ATK maintainer(s)
Depends on:
Blocks: 638537
Reported: 2011-05-28 20:37 UTC by Joanmarie Diggs (IRC: joanie)
Modified: 2021-06-10 11:25 UTC
See Also:
GNOME target: ---
GNOME version: ---

Description Joanmarie Diggs (IRC: joanie) 2011-05-28 20:37:36 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

Note: AtkTable already has a dedicated bug (bug 639479).
Comment 1 André Klapper 2011-06-23 22:06:22 UTC
[Mass-reassigning open atk bug reports for better trackability as requested in .
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 atk-maint@gnome.bugs to your watchlist at the bottom of 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.]
Comment 2 André Klapper 2021-06-10 11:25:48 UTC
GNOME is going to shut down in favor of
As part of that, we are mass-closing older open tickets in
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.