New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 595337 link

Starred by 2 users
Status: Duplicate
Merged: issue 499419
Owner: ----
Closed: Dec 2017
Cc:
aboxhall@chromium.org
lpalmaro@chromium.org
dmazzoni@google.com
pnangunoori@chromium.org
█ hdodda@chromium.org
dmazz...@chromium.org
ligim...@chromium.org
mea...@chromium.org
█ f...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug
Team-Security-UX
Team-Accessibility


Show other hotlists

Hotlists containing this issue:
EnamelAndFriendsFixIt


Sign in to add a comment

Screen readers and keyboard navigation don't work in security warning screens

Reported by agas...@gmail.com, Mar 16 2016 
If I encounter some pages blocked by google security features, Screen reader just say: "Chrome legacy window" and nothing else. Navigation within this window is not possible, with tab or arrow keys. Using JAWS and NVDA.
This page is also apeer on supervised users accounts, when message about blocked page is shown.
"Chrome legacy window".
Chrome Version       : 50.0.2661.26
OS Version: 10.0
What steps will reproduce the problem?
1. Open any page blocked by Google secure features or block some pages on supervised profile and try to open in with screen reader.
2. Try to navigate.

What is the expected result?
It need to be in webview and screen reader need to read that dialog that the page is blocked and why.

What happens instead of that?
Instead, as I stated, screen readers just saying "Chrome legacy window".

UserAgentString: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/50.0.2661.26 Safari/537.36

Comment 1 by rsleevi@chromium.org, Mar 17 2016

Cc: f...@chromium.org
Components: Security>UX UI>Accessibility

Comment 2 by palmer@chromium.org, Mar 29 2016

Summary: Screen readers and keyboard navigation don't work in security warning screens (was: Screen readers dont reading Chrome security window or chrome legacy window.)
Is this bug about the broken HTTPS and SafeBrowsing interstitials?

Comment 3 by agas...@gmail.com, Mar 29 2016 

Yes.

Screen readers just announcing "ChromeLegacyWindow" and navigation 
within that window is not possible.



29.3.2016. u 02:17, palmer@chromium.org via Monorail je napisao/la:

Comment 4 by palmer@chromium.org, Apr 1 2016

Cc: lpalmaro@chromium.org dmazz...@chromium.org aboxhall@chromium.org

Comment 5 by f...@chromium.org, Apr 4 2016 

I'm not sure why this keeps breaking. :(

Comment 6 by mea...@chromium.org, Apr 27 2016

Status: Available (was: Unconfirmed)

Comment 7 by raymes@chromium.org, Sep 6 2016

Labels: Interstitials

Comment 8 by lgar...@chromium.org, Nov 22 2016

Components: -Security>UX UI>Browser>Interstitials

Comment 9 by lgar...@chromium.org, Dec 7 2016

Labels: -Interstitials

Comment 10 by agas...@gmail.com, Dec 21 2016 

Just curious, does any movement made?
Another example, you can visit site bestprosoft.com and such warning will apeer, but screen readers wont read it.

Comment 11 by dmazz...@chromium.org, Mar 7 2017

Labels: NewComponent-Accessibility-Browser

Comment 12 by dmazz...@chromium.org, Mar 27 2017

Labels: NewComponent-Accessibility

Comment 13 by dmazz...@chromium.org, Apr 21 2017

Labels: -newcomponent-accessibility-browser -newcomponent-accessibility

Comment 14 by dmazz...@chromium.org, Aug 4 2017

Labels: triage-dominic

Comment 15 by est...@chromium.org, Nov 10 2017

Labels: Hotlist-EnamelAndFriendsFixIt

Comment 16 by sdy@chromium.org, Dec 11 2017

Cc: mea...@chromium.org hdodda@chromium.org pnangunoori@chromium.org dmazzoni@google.com ligim...@chromium.org
 Issue 726881  has been merged into this issue.

Comment 17 by sdy@chromium.org, Dec 11 2017

Labels: OS-Mac
Also affects macOS. This is pretty crappy.

Comment 18 by sdy@chromium.org, Dec 11 2017

Labels: -OS-Mac
Mergedinto: 499419
Status: Duplicate (was: Available)
Okay, it looks like there are separate bugs. Merging this into the Windows bug.
►

Sign in to add a comment