This isnt a bug, though. It’s the nature of the click command, whicb, as you’ve noted, is an accessibility hook rather than an event tap.
No. For whatever reason, it so happened that click was previously able to interface with HTML DOM elements in Google Chrome, which was fortuitous for @Salazarian’s purposes but not typical behaviour one ought to expect (notwithstanding the same behaviour exhibited in Safari).
And the reason this behaviour is exhibited will be because of the conscientiousness of the developers who would have taken the time to expose the DOM content for accessibility. That Google Chrome apparently no longer does this, however, doesn’t infer any shortcomings of either click or the web browser.
Interfacing with the DOM using accessibility is not a particularly appropriate technique, as there’s already a specific way to interact with a webpage programmatically, which is by way of JavaScript injection. This, of course, would negate the need to rely on screen coordinates and the careful positioning of the browser window. Even cliclick—which I assume posts an event tap—is not going to be a robust approach here.