Change theme
Help
Press space for more information.
Show links for this issue (Shortcut: i, l)
Copy issue ID
Previous Issue (Shortcut: k)
Next Issue (Shortcut: j)
Sign in to use full features.
Vote: I am impacted
Notification menu
Refresh (Shortcut: Shift+r)
Go home (Shortcut: u)
Pending code changes (auto-populated)
View issue level access limits(Press Alt + Right arrow for more information)
Unintended behavior
View staffing
Description
Then I found that Carousel Role was added
So what this does is when swiping with talkback it reads the next carousel item and scroll horizontally.
So without the Role of carousel it does not read the next item on scroll horizontally. I am overall kind of confused on when you use a carousel or not. Currently I have a quite a few HorizontalPagers some that are full screen, some that are partial screen, and some used with tabs. I am not clear on when we should be using carousel and when not.
This is my best guess. So every horizontalpager should be using Carousel except when there is other ways to navigate the carousel like tabs? Like if you do not add the role of carousel for things it will make certain content inaccessible which is not good.
So some things that add confusion
Seems to indicate there is a direct relationship on if its full screen or not whether you use it. "Introduce a new semantics Role that can be used to indicate that a Pager should behave like a Carousel and not a regular full-screen Pager.
"
Like I wonder if this is what broke it but there is not alot of detail on pager semantics
Maybe that is the missing piece I need to understand.
Thanks for your time