commit | 59ae24babb60c0a2a662b57630a276a9d83761aa | [log] [tgz] |
---|---|---|
author | Edman Anjos <edmanp@google.com> | Fri Dec 01 15:15:03 2023 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Dec 01 15:15:03 2023 |
tree | 7168d9c77917ea7101cf1c01a1da8e13b5e74c82 | |
parent | 12169c2f5514235fa76bba57e048f9bbb0854012 [diff] |
CRD: Alert screen reader users when the security curtain is visible Add `role="alert"` attributes to curtain_screen.html so that the screen reader will notify users about it. Previously the curtain would mute audio output immediately. We must now delay it when the screen reader is enabled so the reader has time to read the alert before we mute audio output. This is done by waiting for 20 seconds when the reader is enabled. The 20 seconds time was chosen as twice the time it takes the screen reader to read the alert with the default English voice. This also updates the curtain InitParams so that callers can configure how long the curtain should wait when muting audio output. ash/curtain/security_curtain_controller_impl_unittest.cc \ remoting/host Bug: b:268174926 Test: enable ChromeVox, start CRD from DPanel, it reads the security curtain contents Test: repeat previous test with --enable-features=EnableCrdAdminRemoteAccessV2,CrosPrivacyHubV0 Test: testing/xvfb.py tools/autotest.py -C out_/Default --run-all \ Change-Id: I290a10a504dfec51ae75b5a032923dc079dafb65 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5040714 Reviewed-by: Dominic Battre <battre@chromium.org> Reviewed-by: Joe Downing <joedow@chromium.org> Commit-Queue: Edman Anjos <edman@chromium.org> Reviewed-by: Jeroen Dhollander <jeroendh@google.com> Cr-Commit-Position: refs/heads/main@{#1231927}
Chromium is an open-source browser project that aims to build a safer, faster, and more stable way for all users to experience the web.
The project's web site is https://www.chromium.org.
To check out the source code locally, don't use git clone
! Instead, follow the instructions on how to get the code.
Documentation in the source is rooted in docs/README.md.
Learn how to Get Around the Chromium Source Code Directory Structure .
For historical reasons, there are some small top level directories. Now the guidance is that new top level directories are for product (e.g. Chrome, Android WebView, Ash). Even if these products have multiple executables, the code should be in subdirectories of the product.
If you found a bug, please file it at https://crbug.com/new.