Talkback is unable to access combobox dropdown options via swiping left/right [274660397]

Assigned

Bug

[AOSP] assigned

Status Update

No update yet.

Description

dl...@gmail.com

created issue #1

Mar 21, 2023 10:59PM

Background:
Previously our implementation of a ComboBox:

https://react-spectrum.adobe.com/react-spectrum/ComboBox.html was accessible in Talkback. Users could open the combobox and swipe left/right to enter and focus the dropdown options. Now, Talkback seems to be unable to access the items with the combobox dropdown list, reproduced this bug as well in the official WAI-ARIA combobox examples as well:

https://www.w3.org/WAI/ARIA/apg/patterns/combobox/examples/combobox-autocomplete-list/

Steps to reproduce:
1. Navigate to

https://codepen.io/lfdanlu/pen/gOdBzgW
2. Using Talkback, focus the dropdown arrow in the "State" combobox
3. Double tap to open the combobox's dropdown.
4. Attempt to focus any of the items inside the dropdown via swiping left/right. Note that the TalkBack cursor can focus the list itself but not the items within.

- What happened.
You can focus the combobox's dropdown list but not any of the items via swiping left/right in Talkback.

- What you think the correct behavior should be.
All items in the dropdown list should be reachable via swipes in Talkback

- Is this a security related issue? Yes/No
No

- Don't forget to mention which version of Android you're using, and/or which
device the problem appears on (model and Android version).
Android 13, Samsung Galaxy 22+, Chrome 111.0.5563.58, Talkback 13.5

deleted

0 B

Comments

dl...@gmail.com <dl...@gmail.com> #2Mar 21, 2023 11:09PM

Reporting as a developer,

https://drive.google.com/drive/folders/1HZ2WxsZBS2LD5Dc50ubnZMD4djNsDUWs?usp=sharing is the link to the generated bug report

vi...@google.com <vi...@google.com> #3Mar 22, 2023 10:17AM

Assigned to vi...@google.com.

Thank you for reporting this issue. For us to further investigate this issue, please provide the following additional information:

Can you confirm if this issue is reproducible on a Pixel/Nexus device?

Screen Record of the Issue
Please capture screen record or video of the issue using following steps:

adb shell screenrecord /sdcard/video.mp4
Subsequently use following command to pull the recorded file:
adb pull /sdcard/video.mp4
Attach the file to this issue.

dl...@gmail.com <dl...@gmail.com> #4Mar 22, 2023 10:12PM

Unfortunately I don't have a Pixel/Nexus device to test on, I'll ask my coworkers if they do. Attached the screen recording below.

Screen_Recording_20230322_150935_Chrome.mp4

Restricted

5.2 MB

Download

vi...@google.com <vi...@google.com> #5Mar 23, 2023 03:05PM

We have shared this with our product and engineering team and will update this issue with more information as it becomes available.

dl...@gmail.com <dl...@gmail.com> #6Mar 23, 2023 08:50PM

Thanks! A coworker of mine tested on their Pixel phone and ran into the same issue.
Device specs:
phone: pixel 5a
android: 13
chrome: 111.0.5563.58
talkback version 13.1

dl...@gmail.com <dl...@gmail.com> #7Mar 25, 2023 08:33PM

By the way, are there any emails that I should be sharing the debug info with? Got several access requests but just wanna make sure.

vi...@google.com <vi...@google.com> #8Mar 27, 2023 11:29AM

Yes, Please share the access. Thanks!

dl...@gmail.com <dl...@gmail.com> #9Mar 27, 2023 05:01PM

Folder is now shared, lemme know if there is anyone else to share it with.

na...@gmail.com <na...@gmail.com> #10May 5, 2023 03:11PM

I have a Pixel 7, running Android 13 and talkback v13.1
I was able to reproduce this issue. Has the Talkback product team acknowledged this issue yet? Looking forward to a quick solution for our Accessibility customers.

sk...@gmail.com <sk...@gmail.com> #11May 22, 2023 03:06PM

I've been experiencing this same issue on my Samsung Galaxy Note 9 (Android 10) and Pixel 5 (Android 13) since at least Chrome version 110.0.5481.65. Persists on Chrome 113.0.5672.132, Talkback version 13.1 as of this writing.
Any updates related this issue?

na...@gmail.com <na...@gmail.com> #12May 30, 2024 04:43PM

It's been over a year and this issue still exists. What's the ETA for the fix?