Issue metadata
Sign in to add a comment
|
Read selection state of files being selected in files app
Reported by
nimerjaber1@gmail.com,
Jul 27 2016
|
||||||||||||||||||||||||
Issue descriptionMode: force_next Version: 54.0.2806.0 Reproduction Steps: 1. Launch CVox Next 2. Open files app and navigate to folder with multiple files 3. Attempt to select multiple files. I attempted with holding down CTRL and using arrows to move around, pressing space to select and unselect. I also attempted holding shift key while arrowing. Expected: The name of the file that is selected would be announced. Actual: I oten could not tell what was being announced. I believe it may have been the last files selected in addition to the current selected, but I am not sure.
,
Aug 5 2016
cc'ing smckay@ and fukino@ to the bug. fukino@ is the TL for CrOS files app, smckay@ for visibility.
,
Aug 8 2016
Thank you! fukino@ can your team take on these issues that have been reported about screen reader navigation in the Files App? Happy to meet to discuss in further detail if you'd like.
,
Aug 9 2016
I'll take this bug. Can we have the list of issues, and could you tell us how to launch Chromebook Next (is it already a default one?)?
,
Aug 10 2016
I'll defer to Laura for list of issues, but to enable Next: 1. ctrl+alt+z will enable ChromeVox 2. alt+shift+q+q will switch into Next
,
Aug 10 2016
Thanks!
,
Aug 19 2016
fukino@ let me know if you have any questions as you go through this! you can learn more about the behavior of the screen reader here, or happy to chat about it over hangout: http://www.chromevox.com/en/next.html
,
Aug 19 2016
,
Aug 19 2016
,
Oct 29 2016
,
Mar 27 2017
,
Apr 21 2017
,
Apr 21 2017
,
Aug 7 2017
@fukino: is there any update here and are you still a good owner for this bug?
,
Aug 9 2017
I'm sorry I'm not working on this issue. lpalmaro@, is there a list of Files app issues about CVox Next? +yamaguchi@ as FYI.
,
Aug 9 2017
,
Aug 9
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Aug 10
,
Aug 15
Luciano - can you take a look at this accessibility issue?
,
Sep 11
I can't reproduce on my dev build: 71.0.3549.0. This probably was fixed by crrev.com/c/1023501 |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by lpalmaro@chromium.org
, Aug 5 2016Owner: dtseng@chromium.org
Status: Assigned (was: Unconfirmed)