Tested the issue in Android and unable to reproduce the issue.

Steps Followed:
1. Enabled Talkback.
2. Launched the Chrome Browser.
3. Navigate to https://movil.bbva.es/ 
4. Tap on the back button displayed on left top of the screen or the Help button on right top of the screen.
5. Observed that Screen is navigated only once to the respective page. Behavior is same with or without enabling talkback. 

Chrome versions tested:
62.0.3202.84 (Stable)

OS:
Android 8.1.0

Android Devices:
Nexus 6P Build/OPM1.171019.010

@andres.rondan -- Thanks for reporting this issue. Could you please provide screencast reproducing the issue and let us know if we have missed anything. That would help us in further triaging the issue.

Thanks in advance.

Hello,

the "good interaction" has been recorded in chrome 61.0.3163.98 with TalkBack, and "wrong interaction" with 62.0.3202.84.

1. Enabled Talkback.
2. Launched the Chrome Browser.
3. Navigate to https://movil.bbva.es/ 
4. Swipe over elements with icons.
5. When you set focus on the "help" button or the "back" button and swipe to set the focus on the next elements, it turns out that the focus appears inside the button and not on the next element.
6. Note that in "good interaction.mp4" the focus goes to the next element immediately, and it is not placed inside the button.

Thanks

Deleted: good interaction.mp4 4.6 MB

	good interaction.mp4 4.6 MB View Download

Deleted: wrong interaction.mp4 1017 KB

	wrong interaction.mp4 1017 KB View Download

Thank you for providing more feedback. Adding requester "pnangunoori@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

I can't reproduce in the latest version. Is it possible it regressed in 62 and was fixed again?

I was able to reproduce it all the Play Store versions of Chrome.
Chrome (62.0.3202.84), Chrome Beta (63.0.3239.41), Chrome Dev (64.0.3261.0) and Chrome Canary (64.0.3268.2)

The accessibility tree created itself is different in case of correct and incorrect behavior which causing the focus to land differently.

Deleted: incorrect 11.3 KB

incorrect 11.3 KB View Download

Deleted: correct 10.0 KB

correct 10.0 KB View Download

This behavior is repeated for almost all elements with role = "button".
We have put tabindex = "0" in the affected elements and the behavior is correct. At the moment we are going to place this tabindex because it is correct that the buttons are accompanied by this attribute.

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/9684de17594ab4a8fb00318dc588842f42bd8bca

commit 9684de17594ab4a8fb00318dc588842f42bd8bca
Author: Isha Bobra <ibobra@google.com>
Date: Thu Dec 07 20:30:45 2017

Android accessibility: Making non focusable children of a control not interesting

For Android, the a11y focus was landing on non focusable children of a control.
This CL makes them non interesting and always places the a11y focus on the
control as a whole.

Bug:  784321 
Change-Id: Ib8ebb6f19bb0fc404872570f8998c8eaa0e65100
Reviewed-on: https://chromium-review.googlesource.com/809934
Reviewed-by: Dominic Mazzoni <dmazzoni@chromium.org>
Commit-Queue: Isha Bobra <ibobra@google.com>
Cr-Commit-Position: refs/heads/master@{#522534}
[modify] https://crrev.com/9684de17594ab4a8fb00318dc588842f42bd8bca/content/browser/accessibility/accessibility_tree_formatter_android.cc
[modify] https://crrev.com/9684de17594ab4a8fb00318dc588842f42bd8bca/content/browser/accessibility/browser_accessibility_android.cc
[modify] https://crrev.com/9684de17594ab4a8fb00318dc588842f42bd8bca/content/browser/accessibility/dump_accessibility_tree_browsertest.cc
[add] https://crrev.com/9684de17594ab4a8fb00318dc588842f42bd8bca/content/test/data/accessibility/html/isInteresting-expected-android.txt
[add] https://crrev.com/9684de17594ab4a8fb00318dc588842f42bd8bca/content/test/data/accessibility/html/isInteresting.html