New issue
Advanced search Search tips

Issue 598714 link

Starred by 1 user

Issue metadata

Status: Available
Owner: ----
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows , Chrome , Mac
Pri: 2
Type: Bug
Team-Accessibility

Blocking:
issue 400674
issue 736722



Sign in to add a comment

Fire an accessibilty alert on autosign-in

Project Member Reported by vasi...@chromium.org, Mar 29 2016

Issue description

Version: 51
OS: All

What steps will reproduce the problem?
(1) Visit https://w3c.github.io/webappsec/demos/credential-management/
(2) Save one credential
(3) Relaunch the page

Autosign-in should happen. The toast should be read by the screen reader.
 
Blocking: -550906 400674
Labels: NewComponent-Accessibility-Browser
Labels: NewComponent-Accessibility
Labels: -newcomponent-accessibility-browser -newcomponent-accessibility
Owner: ----
Status: Available (was: Started)

Comment 6 by vabr@chromium.org, Jun 8 2017

Labels: Hotlist-Polish
Labels: win-a11y
Google Chrome	65.0.3294.2 (Official Build) canary (64-bit) (cohort: 64-Bit)
Windows 10 Enterprise Version 1607 Build 14393.1770
NVDA 2017.4

# Launch Chrome + NVDA and follow above steps. 
I was able to sign in and save my fake credentials, close and reopen Chrome. I was then prompted to auto-signin and the dialog text was read and buttons worked. 

However, the account user name and nickname were not read. I was able to get to them using shift + tab, but they were read as a button even though they are not a button.  

Comment 8 by kolos@chromium.org, Jan 26 2018

Blocking: 736722

Sign in to add a comment