Chrome 52 is super old. I can't reproduce with Chrome 63 on Android 8.

Please reopen if you can reproduce with the current version of Chrome.

sorry, the correct version is 62.0.3202.84, not 52.x... I don't know if I can edit the issue description. 
I reproduce it in chrome canary 64.0.3282.0.
Is It possible that it is a talkback issue? Then, how can I open them the issue?

Able to reproduce the issue in Android. Observed the application is not responding.

Steps Followed:
1. enable talkback
2. visit https://beeva-andresrondan.github.io/a11y-issues/
3. Tapping on button 1 ot button 2 shows the text "The element is not a buttont"

Observations --
1. When talk back is not enabled, Tapping on button 1 ot button 2 shows the text "button1 or button 2"
2. In Firefox Tapping on button 1 ot button 2 shows the text "button1 or button 2", even when talkback is enabled or not.

Chrome versions tested:
62.0.3202.84, 63.0.3239.71, 64.0.3282.0

OS
Android 78.0.0

Android Devices
Pixel XL (OPR1.170623.027)

This seems to be a Non-Regression issue as same behavior is seen since M59. Untriaged for further inputs on this issue.

Please navigate to below link for log's and video--
go/chrome-androidlogs/791285

Note: Behavior of firefox is also displayed in the video.

Thank You.

OK, I see the issue.

This only happens with Android O and higher (8.0 and higher). On that version, when you double-tap it sends an accessibility click to the object with accessibility focus.

In prior Android versions, it simulated a tap, which led to both click and focus.

It sounds like Chrome should give elements focus if they're clicked via accessibility.

I reproduce it as well. Focus is broken