RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Have you tried debugging this?

I have no experience with at-spi browser, so I wonder if the issue is just the lack of accessibility roles/labels in those libhandy widgets or there's something more to it. Any idea?

Hello Felipe, no I have not tried debugging the accessibility itself or the widgets used. I have not many experience about how to do that that is why I consulted with you first, the bug was created as a result of our team meeting to keep track of the issue. The roles/labels seem fine actually, I have not encountered much issues there, only the coordinates are wrong in this particular case.

Can still be reproduced on 9.3. But I suppose this should be resolved in upstream first. There is also a fact that this is not an issue of g-c-c but accessibility. Should we close this?