Use scrollPhysics.allowImplicitScrolling to configure scrollable semantics #20210
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jonahwilliams
changed the title
Contributor
|
How does one get to the end of a tab bar that has too many items to fit on screen? This sounds like once it gets to the last visible tab, it jumps to the tab body, but what if the tab bar has a bunch of tabs that are offscreen, but scrollable into view? How would I know that as an accessible interface user? |
gspencergoog
approved these changes
Aug 7, 2018
Contributor
|
|
Contributor
Author
|
@gspencergoog you need to explicitly scroll with two fingers on either the tab body or the page |
Contributor
Author
|
The tab bar labels also describe 3 of N, 4 of N |
Contributor
|
Got it. Cool. Sounds like a good change. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When a user navigates to the end of a visible viewport, there are two behaviors that Talkback supports: 1) it can attempt to scroll the next element from the current viewport into view, like in a List or 2) it can continue the a11y traversal as if the offscreen elements aren't there.
The latter behavior isn't exposed by us, but is necessary for a widget such as a TabBar - with implicit scrolling enabled a user would have to navigate to the end of the scrollable tabs before they can navigate into the tab body. With this change, we can configure it such that reaching the end of the visible tabs will immediately move to the tab body instead.
We already have this information on the framework side with https://master-docs-flutter-io.firebaseapp.com/flutter/widgets/ScrollPhysics/allowImplicitScrolling.html
Fixes #19917