Tell users that bottom toolbar is swipeable |
||||||
Issue descriptionIssue Steps: + Select omnibox/overflow menu + Have no idea that bottom toolbar is swipeable open Proposed Solution: When you focus on omnibox/overflow menu, say what the standard text and append “Swipe up to access navigation panel”.
,
May 22 2017
A quick correction on the strings - the "Double tap activate" and similar strings are appended automatically by Android, so the strings would read more like "More options button. Swipe up to access navigation panel. Double tap to activate."
,
May 23 2017
I came up with a good compromise. When the expand button is not visible, I made the bottom toolbar focusable via touch exploration and set the content description to "Address bar. Pull up to see bookmarks, downloads, and history." That way if users are swiping between items when talk back is on, the entire toolbar can gain focus and will read the description.
,
May 23 2017
Perfect - yes that sounds great. Thanks!
,
May 23 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/44dd1fe909c433cf0b8297be8825e372fc2d57a8 commit 44dd1fe909c433cf0b8297be8825e372fc2d57a8 Author: twellington <twellington@chromium.org> Date: Tue May 23 18:36:17 2017 [Home] Add some accessibility support * Announce when the panel is opened and closed. * Prevent focus from going to the tab content when the bottom sheet is open. * Change the in-product help bubble when the expand button is enabled and use different strings for non-accessibility mode and accessibility mode. * Announce when a different bottom sheet tab is selected. * When the expand button isn't visible, make the entire toolbar focusable for accessibility and add a content description. BUG= 724694 , 724696 , 724693 , 724695 Review-Url: https://codereview.chromium.org/2895223003 Cr-Commit-Position: refs/heads/master@{#473995} [modify] https://crrev.com/44dd1fe909c433cf0b8297be8825e372fc2d57a8/chrome/android/java/src/org/chromium/chrome/browser/ChromeActivity.java [modify] https://crrev.com/44dd1fe909c433cf0b8297be8825e372fc2d57a8/chrome/android/java/src/org/chromium/chrome/browser/toolbar/BottomToolbarPhone.java [modify] https://crrev.com/44dd1fe909c433cf0b8297be8825e372fc2d57a8/chrome/android/java/src/org/chromium/chrome/browser/widget/bottomsheet/BottomSheet.java [modify] https://crrev.com/44dd1fe909c433cf0b8297be8825e372fc2d57a8/chrome/android/java/src/org/chromium/chrome/browser/widget/bottomsheet/BottomSheetContentController.java [modify] https://crrev.com/44dd1fe909c433cf0b8297be8825e372fc2d57a8/chrome/android/java/strings/android_chrome_strings.grd
,
May 23 2017
,
Jun 1 2017
Verified in M60-60.0.3112.10 build. It is reading as "Navigation Panel Opened and Closed
,
Jun 12 2017
I'm going to re-open to track an add on piece for accessibility. We should change the toolbar content description to "pull down to close navigation panel" or something like that when the sheet is opened.
,
Jun 12 2017
Sounds reasonable to me. +Laura any thoughts here? Otherwise, I think calling "Swipe down to close navigation panel" seems fine to me.
,
Jun 12 2017
If we do "Swipe down to close..." should we change the existing accessibility to "Swipe up to see..." (it's currently "Pull up to see...")?
,
Jun 12 2017
Sure - let's keep to pull down since that's already been reviewed.
,
Jul 1 2017
,
Jul 6 2017
Laura, changing the content description of the toolbar while it's focused causes TalkBack to read the new content description. For example, if the user focuses the toolbar, TalkBack will currently read "Address bar. Swipe up to see bookmarks, downloads, and history." If the user then pulls up on the address bar to open the navigation panel, TalkBack will read "Address bar. Swipe down to close navigation panel. Navigation panel opened." I think it's a bit odd that it reads the new content description. I can prevent it by temporarily marking the view and not important for accessibility, but that causes the toolbar to lose accessibility focus. From your perspective, what is the correct behavior?
,
Jul 11 2017
post holiday bump - lpalmaro@, will you pleas comment on #13 when you have a few minutes?
,
Jul 13 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/b8d100d9581474a2f45bc03c2ed7b45bfa6b9b1d commit b8d100d9581474a2f45bc03c2ed7b45bfa6b9b1d Author: Theresa Wellington <twellington@google.com> Date: Thu Jul 13 22:50:39 2017 [Home] Update toolbar content description based on sheet state BUG= 724695 Change-Id: Ibb733a5ac20664aa4bac20fe41e13ffe1523ffef Reviewed-on: https://chromium-review.googlesource.com/570665 Reviewed-by: Ted Choc <tedchoc@chromium.org> Commit-Queue: Theresa <twellington@chromium.org> Cr-Commit-Position: refs/heads/master@{#486505} [modify] https://crrev.com/b8d100d9581474a2f45bc03c2ed7b45bfa6b9b1d/chrome/android/java/src/org/chromium/chrome/browser/toolbar/BottomToolbarPhone.java [modify] https://crrev.com/b8d100d9581474a2f45bc03c2ed7b45bfa6b9b1d/chrome/android/java/strings/android_chrome_strings.grd
,
Jul 13 2017
,
Jul 14 2017
To circle back, when the sheet is opened I give focus to the bottom sheet. When the sheet is closed, focus stays on the toolbar (if it has focus) so the content descriptions may be read back to back. The experience seems pretty good to me, but we can polish after accessibility review if needed.
,
Jul 17 2017
Hey! Sorry for the delay as I was traveling for 2 back to back a11y conferences. I think it's fine to have the description read, actually, as it gives the user confirmation of what happened. The only thing I'd say is that if we could reorder what is spoken, that might be best -- for example, if we could say "Address bar. Navigation panel opened. Swipe down to close navigation panel." that might be more intuitive. What do you think?
,
Jul 17 2017
No problem, thanks for the feedback! "Address bar" and "Swipe down to close navigation panel" are part of the same content description, so they can't be broken up. I could try to swap the order -- "Navigation panel opened. Address bar. Swipe down to close navigation panel." ? |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by twelling...@chromium.org
, May 22 2017