This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
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.
Bug 2129290 - Accessibility problem in gnome-control-center, widgets report wrong coordinates.
Summary: Accessibility problem in gnome-control-center, widgets report wrong coordinates.
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: gnome-control-center
Version: 9.2
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Felipe Borges
QA Contact: Michal Odehnal
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-09-23 08:38 UTC by Michal Odehnal
Modified: 2023-10-06 07:00 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-10-06 07:00:35 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker   RHEL-11907 0 None Migrated None 2023-10-06 07:00:29 UTC
Red Hat Issue Tracker RHELPLAN-134772 0 None None None 2022-09-23 09:20:41 UTC

Description Michal Odehnal 2022-09-23 08:38:23 UTC 
Created attachment 1913667 [details]
wrong reported coordinates

Description of problem:
Automation for RHEL requires working accessibility with various features that we are using to verify all features of desktop applications. As the time goes things break and we need to make a workaround to make the test work and be able to provide data about component state. Now it seems like things only break on a11y side and never get fixes, but we need this working because we lose ability to make clicks on desired targets and we lose the test. Our automation does not have eyes, it relies on a11y providing the coordinates based on the name/rolename of the buttons/panels. It is also not viable to only workaround those issues which seems to only increase with time.

Version-Release number of selected component (if applicable):
gnome-control-center-40.0-24.el9.x86_64

How reproducible:
100%

Steps to Reproduce:
1. Find the coordinates to some settings, as the video shows.
2.
3.

Actual results:
wrong coordinates

Expected results:
correct coordinates

Additional info:
I have in past gave up on filing bugs on a11y since they only get closed and never get worked on.

The bugs in the past got closed because there was no business justification. Well the justification is that the customer files bugs and we try to automate the reproducer so it will not happen again. I believe the justification for this to get fixed is there.
Comment 2 Felipe Borges 2022-09-23 09:31:41 UTC 
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?
Comment 4 Michal Odehnal 2022-09-23 09:35:57 UTC 
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.
Comment 6 Michal Odehnal 2023-08-23 13:49:59 UTC 
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?
Comment 7 RHEL Program Management 2023-10-06 07:00:12 UTC 
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.
Comment 8 RHEL Program Management 2023-10-06 07:00:35 UTC 
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.
Note You need to log in before you can comment on or make changes to this bug.