New issue
Advanced search Search tips

Issue 785616 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Closed: Nov 2017
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug
Team-Accessibility



Sign in to add a comment

a11y: Unable to invoke Chromecast button with JAWS screen reader

Project Member Reported by leberly@chromium.org, Nov 16 2017

Issue description

Google Chrome	64.0.3269.0 (Official Build) canary (64-bit) (cohort: Clang-64)
Windows 10 Enterprise Version 1607 Build 14393.1770
NVDA 2017.3
JAWS 2018.1710.42 private preview release

A user submitted this issue which I have paraphrased: 
"I couldn’t get to the list of available cast devices using JAWS. I have a touch screen so I can locate it by touch if necessary. I still cannot access the list using JAWS and keyboard commands. I have multiple Chromecast devices and I would love to be able to do this on any of my PCs."

For this first round of tests I did not have a Chromecast device handy. I'll update this bug once I get access to testing with a device. 

Here are the steps I took to reproduce it:
# Launch JAWS and Chrome Canary
# Navigate to the Customize and Control Google Home menu (the icon on the toolbar)
# Navigate to "Cast..."
# Read the text in the dialog that appears
Expected: all text is read
Actual: all text is read including buttons and dropdown items 

# Close JAWS and open NVDA
# Repeat the steps to get to the Cast dialog
# Read the text in the dialog that appears
Expected: all text is read
Actual: all text is read including buttons and dropdown items 

In both cases, the initial focus was in different areas. I will also check this once I get access to a device. 

 
Status: WontFix (was: Assigned)
Google Chrome	64.0.3273.3 (Official Build) canary (64-bit) (cohort: Clang-64)
Google Chrome	63.0.3239.59 (Official Build) beta (64-bit) (cohort: Beta)
Google Chrome	62.0.3202.94 (Official Build) (64-bit) (cohort: Stable)

Hello,

I tested again with Stable, Beta, and Canary with a known-working Chromecast device so that the device was listed as a device in the dialog. 

In Stable, the first time I encountered this dialog it appeared as if buttons were unlabeled and were not read. I then closed the dialog, reopened it, and all buttons appeared to be labeled. 

However, in Beta and Canary, all of the buttons and text were read on the first time. We have recently made improvements to dialogs so it appears that these fixes applied to this dialog specifically. 

Therefore, if you want to use Stable, a workaround is to close and reopen the dialog. Then, try again when Beta is promoted to the Stable channel and the fixes are automatically updated. You could also just download Chrome Beta now and try it on your setup. 

I am therefore closing this bug as WontFix since it can't be reproduced in newer versions of Chrome. 

Please let me know if you have further questions or concerns and feel free to reopen this issue if it is still happening for you.

Thanks,

Laura

Sign in to add a comment