New issue
Advanced search Search tips

Issue 779501 link

Starred by 3 users

Issue metadata

Status: Available
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug-Regression

Blocked on:
issue 730971



Sign in to add a comment

javascript alert() dialog not announced in screen readers

Project Member Reported by faulkner...@gmail.com, Oct 30 2017

Issue description

Chrome Version: (Version 62.0.3202.75 (Official Build) (64-bit))
OS: (win10)

What steps will reproduce the problem?
(1)go to https://s.codepen.io/stevef/debug/qVEqLN
(2)navigate to button with JAWS or NVDA running
(3)activate button

What is the expected result?
screen reader announces presence of dialog and dialog content and the content/interactive content is operable using an SR

What happens instead?
Dialog not announced and content cannot be interacted with

original issue filed on JAWS standards support tracker 
https://github.com/FreedomScientific/VFO-standards-support/issues/16

 
Components: Blink>WindowDialog
Status: Available (was: Untriaged)
I think that's what this change is trying to fix:

https://chromium-review.googlesource.com/c/chromium/src/+/653920

JAWS works correctly if you Alt+Tab away and back to Chrome. The underlying issue is that when the Focus event fires inside the dialog, we're unable to walk the accessibility tree from inside dialog up the parent chain to the root window.

I think there are related bugs to de-dup against.

Labels: Needs-Triage-M62
This is not only about alerts, but also about confirmation dialogs (Javascript confirm() function), onBeforeUnload() dialogs and prompts to save passwords or questions about allowing/denying using the webcam, microphone and so forth. I believe all of these are related.
Blockedon: 730971
Status: Fixed (was: Available)
Marked as fixed because I believe the underlying bug is fixed ( bug 730971 ).

Verification requested.

Confirmed fixed in Chrome Canary version 64.0.3273.3 on Windows 7.
However, the password save confirmation seem to be still silent. Is this unrelated?
Status: Available (was: Fixed)
chrome 66.0.3349.0 (Official Build) canary (64-bit) (cohort: Clang-64)
NVDA 2017.4

# This dialog does not behave like other dialogs such as a permission dialog.
Although the dialog is read on initial load, I cannot use NVDA+b to read the dialog. Instead, the entire window is read.
# The 'OK' button which has focus is also not read on initial load.
# "Alert" or "Dialog" is not spoken before dialog text so it is not clear to screen reader that this text is a new dialog.

Sign in to add a comment