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.