New issue
Advanced search Search tips

Issue 876395 link

Starred by 1 user
Status: Duplicate
Merged: issue 875843
Owner:
ellyjo...@chromium.org
Closed: Aug 23
Cc:
aleventhal@chromium.org
dmazz...@chromium.org
pbomm...@chromium.org
ellyjo...@chromium.org
phanindra.mandapaka@chromium.org
aboxhall@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 1
Type: Bug-Regression
Team-Accessibility



Sign in to add a comment

VoiceOver no longer speaks ARIA alerts in Chrome 69 beta

Reported by st...@desmos.com, Aug 21 
UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/66.0.3359.181 Safari/537.36

Steps to reproduce the problem:
1.  Enable VoiceOver with COMMAND+F5.
2.  In Chrome, visit https://www.w3.org/TR/2017/NOTE-wai-aria-practices-1.1-20171214/examples/alert/index.html
3.  Click the "Trigger Alert" button.

What is the expected behavior?
VoiceOver speaks "Hej, hello, ciao, こんにちは, 안녕"

What went wrong?
Nothing is spoken.

Did this work before? Yes Chrome 68 stable

Chrome version: 69.0.3497.42  Channel: beta
OS Version: 10.13.6
Flash Version: 

This was also not working in the Chrome 68 betas. Also tested against OSX Mojave beta 8 and observed identical results.

Comment 1 by st...@desmos.com, Aug 21 

Also forgot to mention that this issue is specific to the Mac port. JAWS and NVDA still read alerts on the Chrome 69 beta channel in Windows 10.

Comment 2 by ja...@desmos.com, Aug 21 

I have also reproduced this issue in Chrome 70.0.3529.3 (canary) on MacOS 10.13.6.

Comment 3 by chrishtr@chromium.org, Aug 22

Components: -Blink Blink>Accessibility
Labels: -Pri-2 ReleaseBlock-Stable Needs-Bisect Target-69 FoundIn-69 Pri-1

Comment 4 by gov...@chromium.org, Aug 22

Cc: pbomm...@chromium.org dmazz...@chromium.org
+pbommana@, could you pls try to repro and bisect?

+dmazzoni@,could you ptal as this is M69 stable blocker?

Comment 5 by dmazz...@chromium.org, Aug 22

Cc: aleventhal@chromium.org
Is it possible that you had MacViews on? It's an experiment, and there are known issues with live regions and alerts...

Comment 6 by gov...@chromium.org, Aug 22

Cc: ellyjo...@chromium.org
+ellyjones@, Any chance this is a macviews-related regression?

Comment 7 by aleventhal@chromium.org, Aug 22

Owner: aleventhal@chromium.org
@dmazzoni, live regions have regressed even with MacViews off.

This is probably the same as  issue 875843

Comment 8 by susan.boorgula@chromium.org, Aug 23

Labels: Needs-Triage-M69

Comment 9 by phanindra.mandapaka@chromium.org, Aug 23

Cc: phanindra.mandapaka@chromium.org
Labels: -Needs-Bisect hasbisect-per-revision Triaged-ET M-69 Target-70 RegressedIn-69 FoundIn-70
Owner: ellyjo...@chromium.org
Status: Assigned (was: Unconfirmed)
Able to reproduce issue on reported chrome version 69.0.3497.42 & on latest chrome 70.0.3530.0 using Mac 10.13.5. Hence providing bisect information below.
NOTE:Issue related to Mac
Bisect Info:
================
Good build: 69.0.3496.0
Bad build: 70.0.3500.0

CHANGELOG URL:
https://chromium.googlesource.com/chromium/src/+log/bcb7db78edc13f57577f0a9562c98918bdcc10ae..67d21d10815fe6d87d1785a65a50fbc386e6605b

suspect: https://chromium.googlesource.com/chromium/src/+/67d21d10815fe6d87d1785a65a50fbc386e6605b

Reviewed-on: https://chromium-review.googlesource.com/977949

ellyjones@: Please confirm the issue and help in re-assigning if it is not related to your change.

Thanks...!

Comment 10 by ellyjo...@chromium.org, Aug 23

Mergedinto: 875843
Status: Duplicate (was: Assigned)
My change enabled a gigantic experiment by default, so it certainly wasn't that specific change that caused this - especially if per #7 it regressed even with that experiment off. Per #7 this is a dupe of  issue 875843 .
►

Sign in to add a comment