commit | 7f144ec1e0c84df4b29324f90e57fc9febe7c03d | [log] [tgz] |
---|---|---|
author | Katie Dektar <katie@chromium.org> | Thu Jun 29 22:42:43 2023 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Jun 29 22:42:43 2023 |
tree | f397ade90a028b36731f598a877ee34c8f9e3a91 | |
parent | d174c0ab8f29b65fc64d38f28050ec65c1ef1fe9 [diff] |
[Lacros a11y] ChromeVox injects gdocs script on startup Google Docs (drive, sheets, etc) has an accessibility mode that is required to be on to make pages accessible to screen readers, including ChromeVox. ChromeVox in Ash informs gdocs tabs that it is enabled by injecting an event, and ChromeVox in Lacros does this for new gdocs tabs that are opened after ChromeVox Helper is installed. This change ensures that gdocs tabs in Lacros which were open before ChromeVox was enabled also have the event injected, so that pre-existing Lacros gdocs tabs have a11y mode turned on and automatically work with ChromeVox. In short, this replicates behavior in Ash gdocs tabs from ChromeVox in Lacros gdocs tabs, specifically see chrome/browser/resources/chromeos/accessibility/chromevox/background/injected_script_loader.js. For more, see go/lacros-embedded-a11y-extensions. Also adds some required typescript definitions for the parts of the extension API used by ChromeVox helper. Bug: b/286413518 AX-Relnotes: Already open Lacros gdocs tabs turn on a11y when CVox enabled Test: Manual (we don't have browsertests on live gdocs) Change-Id: Ie361287b66da65bcbc8c64e600e8268b98e0873d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4652866 Reviewed-by: Jacob Francis <francisjp@google.com> Commit-Queue: Katie Dektar <katie@chromium.org> Reviewed-by: Demetrios Papadopoulos <dpapad@chromium.org> Cr-Commit-Position: refs/heads/main@{#1164390}
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.