Bug 2129290
Summary: | Accessibility problem in gnome-control-center, widgets report wrong coordinates. | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 9 | Reporter: | Michal Odehnal <modehnal> |
Component: | gnome-control-center | Assignee: | Felipe Borges <feborges> |
gnome-control-center sub component: | Other | QA Contact: | Michal Odehnal <modehnal> |
Status: | CLOSED MIGRATED | Docs Contact: | |
Severity: | unspecified | ||
Priority: | unspecified | CC: | cgarnach, tpopela |
Version: | 9.2 | Keywords: | MigratedToJIRA, TestBlocker |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2023-10-06 07:00:35 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
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? 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. 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. |
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.