Issue metadata
Sign in to add a comment
|
Download manager accessibility announcements are not functional |
||||||||||||||||||||||
Issue descriptionApp Version: 68.0.3398.0 Canary iOS Version: 10.3.3, 11.3 Device: iPhone and iPad Steps to reproduce: 1. Launch chrome 2. Enable Voice Over in device Settings 3. Load https://www.barebones.com/products/bbedit/download.html 4. Tap Download Observed result: Partial text is read for file available and download complete in iPhone. In iPad only download complete text is not completely read Expected result: The app should speak the following text: - "File download is available" (when UI shows up) - "Download successfully finished" (when download is successfully finished) - "Download failed" when download failed Number of times you were able to reproduce: 5/5 Bug reproducible after clean install: Yes Bug reproducible after clearing cache and cookies: Yes Bug reproducible on Chrome Mobile on Android: Not tested Bug reproducible on Safari/Firefox: Firefox: NA, Safari: NA Bug reproducible on current stable build (App Version, iOS Version): No on M65 or M65 (Feature is available from M67) Bug reproducible on the current beta channel build (App Version, iOS Version): Yes on M67 Beta Link to the video: https://drive.google.com/file/d/1P0A9as-4mK4nlIS3Eq9qTek79VyMelOU/view?usp=sharing
,
Apr 19 2018
I tested on iPhone SE and iPad Air 2 and accessibility announcements work as expected. The app reads the text when UI is presented or download is completed. Interacting with the app cause accessibility system to describe the label, which can interrupt previously spoken announcements (which is WAI).
,
Apr 25 2018
Watching this video and a video from another bug, it appears that accessibility announcement is cut by the progress bar, which is a bug (not RBS though). Gauthier, do you know why |stopProgressBar| method sets progress to 1 before hiding the progress indicator?
,
Apr 26 2018
Do you think it shouldn't? I think the idea is to show to the user that the loading of the page is completed, so you visually finish the loading of the progress bar. My question would be more: Should the progress bar get the voice over focus when its progress is updated?
,
Apr 26 2018
Laura, Chrome for iOS has an issue where loading progress bar receives accessibility focus, announces the progress (like "0 percent complete" or "100 percent complete") and this announcement interrupts other voice over announcements. Do you think it is useful to focus on progress bar when it gets updated?
,
May 4 2018
Laura, do you have any feedback on comment #5? Thanks!
,
May 10 2018
,
May 27 2018
Hey, really sorry for the delay -- no I don't think it's useful to steal focus here, or interrupt the user with multiple progress updates if they have shifted their focus elsewhere. I think it's most helpful to announce when progress begins and ends, but not necessarily give repeated updates in between (e.g. 40%, 50%) unless the user places focus on the progress bar to specifically check in on progress.
,
May 29 2018
Laura, this bug happens because the progress bar is focused when progress ends. Seems like we have 2 options here: - do not focus on progress bar when 100% is reached - remove "File download is available" accessibility announcement which one do you think is preferable? Thanks!
,
Jun 15 2018
So the progress bar is focused once it finishes no matter what the user is doing? I wouldn't have it steal focus, as that could be really disruptive.
,
Jun 15 2018
Correct, progress bar is focused once it finishes. Gauthier, do you think we can make progress bar smarter about updating accessibility label?
,
Jun 15 2018
,
Jun 19 2018
The accessibility label of the progress bar is done by MDC, so I don't think we have lot of possibility to really customize it. The current behavior is to post a notification when the progress bar is shown. But the notification takes some time (~2s) to steal the focus. If the page is loading too quickly, the focus is stolen after the page finish loading. We could file a feature request to the MDC team to have the possibility to avoid this focus. It means the loading bar would never steal focus, the user would have to manually focus it. WDYT?
,
Jun 26 2018
Yes, I think filing the feature request sounds good and would be respectful of not stealing focus and disrupting the user.
,
Jul 3
I have filed https://github.com/material-components/material-components-ios/issues/4470
,
Jul 3
Issue 736898 has been merged into this issue. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by sczs@chromium.org
, Apr 18 2018Owner: eugene...@chromium.org
Status: Assigned (was: Untriaged)