New issue
Advanced search Search tips

Issue 617641 link

Starred by 2 users

Issue metadata

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



Sign in to add a comment

Chrome does not inform the JAWS screenreader when a dropdown has been collapsed.

Reported by zach.pet...@pearson.com, Jun 6 2016

Issue description

UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/50.0.2661.102 Safari/537.36

Steps to reproduce the problem:
1. Open JAWS version 17 on a Windows machine.
2. Open attached html page (jaws_dropdown.html) in a Chrome tab.
3. Tab to the dropdown on the page with title "Tutorials".
4. Expand the dropdown with the space bar.
5. Close the dropdown with the escape key. Notice JAWS is not informed that the dropdown is now collapsed.
6. Hit the down arrow button. Notice JAWS reads the menu items inside the dropdown even though it is collapsed.
7. Hit the up arrow button until JAWS reads the "Tutorial" dropdown button. Notice JAWS says the dropdown is still expanded (JAWS has not been informed the dropdown has been collapsed).

NOTE: If in step 5 you close the dropdown with the space button JAWS is informed the dropdown is collapsed, but you are still able to arrow down to the menu items inside the dropdown.

What is the expected behavior?
When the dropdown is collapsed JAWS should be informed. The menu items should not be read by the screenreader while the dropdown is collapsed.

NOTE: This expected behavior is seen on Firefox and Internet Explorer browsers.

What went wrong?
It seems that Chrome does not inform JAWS when a dropdown has been collapsed.

Did this work before? No 

Chrome version: 51.0.2704.79 m  Channel: stable
OS Version: 7
Flash Version: Shockwave Flash 21.0.0.242

This defect is not reproducible on Firefox and Internet Explorer browsers.
 
jaws_dropdown.html
1.3 KB View Download
Reproducible on OS Version: Windows 7
Labels: Te-NeedsFurtherTriage
Components: UI>Accessibility
This is a Jaws bug which has been reported to the 3rd-party vendor. I'll update this bug once we verify that it has been fixed.
Labels: NewComponent-Accessibility-Compatibility
Labels: NewComponent-Accessibility
Components: UI>Accessibility>Compatibility
Components: -UI>Accessibility
Labels: -newcomponent-accessibility-compatibility -newcomponent-accessibility
Labels: triage-aaron
Labels: -TE-NeedsFurtherTriage -triage-aaron
Status: WontFix (was: Unconfirmed)
Cannot repro.
More info. Could not repro with JAWS 18 + Chrome 60  

Sign in to add a comment