New issue
Advanced search Search tips

Issue 648005 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner: ----
Closed: Oct 2016
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug
Team-Accessibility



Sign in to add a comment

Files app: list of drives and folders is not read by either without using ChromeVox specific commands

Project Member Reported by chaok@google.com, Sep 18 2016

Issue description

Mode: force_next
Version: 55.0.2858.0
ChromeVox has acted differently in the Files app. Both ChromeVox Next and Classic act similarly in the app at the time of this writing. It is possible to navigate menus, buttons, and lists of files and folders without using specific ChromeVox commands with Classic and Next, but the list of drives and folders is not read by either without using ChromeVox specific commands. When moving from one file or folder to another, ChromeVox Next will read the previously selected folder or file before reading the file or folder that is currently selected, which means you have to wait through a repeat before hearing your currently selected item. If you navigate using ChromeVox Classic, or ChromeVox Next specific commands, only the newly focused file or folder is read. One major benefit of using ChromeVox Next with the Files app is that you have access to the context menu for items. This menu is not announced when it is launched but it is possible to navigate and operate the menu when it has been evoked. Because of this, ChromeVox Next does provide some benefit in the Files app over ChromeVox Classic.
 
Project Member

Comment 1 by sheriffbot@chromium.org, Sep 18 2016

Labels: Hotlist-Google
Labels: Phase3 files.app
Status: Available (was: Untriaged)

Comment 3 by dtseng@chromium.org, Oct 25 2016

Status: wontfix (was: Available)
Unsure what the specific bug is here. In Phase4, we will audit every shipping app in ChromeVox; doesn't matter whether it's classic or next, in non-web-based UI, it's the same.

Sign in to add a comment