Chrome doesn't always show buttons in the accessibility API (there is some weird parameter to make it do it). But presuming it does, you could use the new facility in the Keyboard Maestro editor to list all the buttons and select it.
I did have someone else who reported it couldn't find a button with just a title, but had no trouble once the button was fully specified.
I'm confused at the example you show because that would not produce a button so I can't see how Keyboard Maestro 10 would have been able to click it with the Press a Button action.
But maybe something is happening on the web site that is changing it in to a button.