Bug P2
Status Update
Comments
ra...@google.com <ra...@google.com> #2
It looks like you are raising an issue as an Android user, rather than an Android Open Source Developer.
For user support, please see the
For Pixel phone support, please see the
Support for other devices is provided by the device manufacturers or by the carriers selling those devices,
ma...@gmail.com <ma...@gmail.com> #3
Attached is a demonstration of the issue using Talkback 12.1.0.397273305 (60120642), Chrome 100.0.4896.127 (Official Build) (32-bit), Nexus 5, Android 6.0.1 Build number M4B30Z.
dl...@gmail.com <dl...@gmail.com> #4
ra...@google.com <ra...@google.com>
ab...@google.com <ab...@google.com> #5
This seems to be related to clank. Moving to the clank bug queue.
dt...@google.com <dt...@google.com>
so...@gmail.com <so...@gmail.com> #6
Muito ruim
Description
When using a HTC Nexus 9 on Android 7.1.1 + Talkback 12.1 + Chrome 100.0.4896.88, I am unable to trigger a click on a visually hidden element via double tapping with Talkback enabled. However, with a Galaxy S9+ on Android 10 + Talkback 12.1 + Chrome 100.0.4896.88, I am able to trigger a click on the same visually hidden element with Talkback. The context behind this is that we are attempting to create a screenreader specific "dismiss" button that shouldn't be visible to non-screenreader users. Said button would be used as a way for screenreader users to close a dialog or menu since non-screenreader users would be able to tap outside the dialog/menu to close it.
Reproduction steps:
1. Navigate to
2. Using Talkback, focus the visible button and double tap to trigger a click. See
3. Note that an alert should appear indicating that the click was successfully. Close this alert.
4. Refocus the visible button and swipe to the right to focus the visually hidden button.
5. Attempt to click the visually hidden button by double tapping. It may or may not open an alert indicating the click was successful depending on your device.