commit | ea7ea1287136d52fc60750c896a03d0a9a08f239 | [log] [tgz] |
---|---|---|
author | Nektarios Paisios <nektar@chromium.org> | Wed Sep 02 11:23:52 2020 |
committer | Commit Bot <commit-bot@chromium.org> | Wed Sep 02 11:23:52 2020 |
tree | 3ae27b4cfe9cca1b40fc557162667e439b1c192f | |
parent | 3657d37c39698793046e26d8eb88dda70cc46da9 [diff] |
Attaches intents to accessibility text changed events When an accessibility text or value changed event is raise, assistive software, such as VoiceOver and ChromeVox, doesn't really know how the previous text was modified. The event doesn't specify for example if: a character has been typed, a new line inserted, a piece of text has been cut, something was pasted, or the current selection replaced with a new piece of text. Assistive software, such as screen readers, need to either monitor key presses, or rely on heuristics to determine what to announce. This patch adds such information to text and value changed events through a list of event intents which describe the command that was carried out. R=dmazzoni@chromium.org, yosin@chromium.org AX-Relnotes: n/a Bug: 989156 Change-Id: Ie33cfd73d195086c80883315ee8fef13bdff251e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2214951 Commit-Queue: Nektarios Paisios <nektar@chromium.org> Auto-Submit: Nektarios Paisios <nektar@chromium.org> Reviewed-by: Dominic Mazzoni <dmazzoni@chromium.org> Reviewed-by: Yoshifumi Inoue <yosin@chromium.org> Cr-Commit-Position: refs/heads/master@{#803823}
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.
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.