Nested VerticalGridView (RecyclerView) from Android TV lean back library is keep skipping row elements in TalkBack mode [277822282]

Assigned

Bug

Status Update

No update yet.

Description

an...@gmail.com

created issue #1

Apr 12, 2023 11:33AM

As per my current Android TV app architecture, its using nested VerticalGirdView (recyclerview). The parent element is one VerticalGridView which is used to scroll vertically the whole page and the each row elements inside it is the one VerticalGridView which is used to scroll horizontally thorough list of cards. When I enabled the accessibility mode, the rows are keep skipping and traversing through horizontal elements also skipping.

Affected device: Android TV

As in the video from below drive link, you will notice the if I click down button the talkback focus from "Title 0" is jumping directly to "Title 2" in between skipping "Title 1". Even it is skipping in horizontal rail items as well.

Tried with many possibilities none of them works. Tried with onKeylistener to get the user key pad events for workaround but listener itself is not working in talkback mode.

Video:

https://drive.google.com/file/d/1FCg6tkRVx6-2Dl2Ucy-e_GE2lYxCscJr/view?usp=sharing

Source code:

https://github.com/anas-ahamed/android-talkback-poc

Is it an Android framework issue?

Any help will be much appreciated. Thanks

Comments

vi...@google.com <vi...@google.com> #2Apr 12, 2023 03:29PM

Assigned to vi...@google.com.

IMPORTANT! Please note that if you released your library to stable with these calls, the APIs must maintain binary compatibility moving forward.

That means the restricted APIs need to be made public or @RestrictTo(LIBRARY_GROUP_PREFIX) (e.g. effectively public for the purposes of compatibility).

You CANNOT simply remove the call to the restricted API.

an...@gmail.com <an...@gmail.com> #3Apr 13, 2023 06:55AM

Sorry, additional point of clarification. These bugs have been filed against the call sites, but the issue really applies to both the restricted API and the call site.

For the call site: the call may be safely removed, however if the call went out in a stable release then that release will crash if the restricted API is removed.

If the restricted API should be maintained to ensure binary compatibility with your library, please forward this issue to the component for the restricted API and continue reading.

For the restricted API: this bug was filed because your API was used outside of your library group. The API must now be tracked for binary compatibility. You may make the API public or LIBRARY_GROUP_PREFIX visibility.

vi...@google.com <vi...@google.com> Apr 13, 2023 01:57PM

Status: New

ad...@google.com <ad...@google.com> Apr 13, 2023 02:10PM

Assigned to da...@google.com.

an...@gmail.com <an...@gmail.com> #4Apr 24, 2023 05:44AM

Can we make this to P1 and check on priority. Because our app requires this issue to be fixed for talkback users on android TV since it is blocked for them to be scrolling down in home screen.

an...@gmail.com <an...@gmail.com> #5May 2, 2023 05:29PM

Any update on this issue ?

ru...@joyn.de <ru...@joyn.de> #6May 8, 2023 03:29PM

#5: Did you try this with https://github.com/rubensousa/DpadRecyclerView?

an...@gmail.com <an...@gmail.com> #7May 12, 2023 12:25PM

Basically there is a restriction to use third parity library in our project for our client. Anyway i will try to use this in my POC and let you know. is there any other workaround available to fix this?