Move accessibility component extensions into shared accessibility/ directory
As part of a transition to share code and tooling more easily between
ChromeVox, Switch Access, Select-to-Speak, autoclick, and any future
accessibility component extensions, move them into a shared
accessibility/ directory in chrome/browser/resources/chromeos.
Bug: 706981
Change-Id: Icaec4981380ac37e42d12706c2ec5693f58c334c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1913122
Commit-Queue: Anastasia Helfinstein <[email protected]>
Reviewed-by: Scott Violet <[email protected]>
Reviewed-by: David Tseng <[email protected]>
Cr-Commit-Position: refs/heads/master@{#717744}
diff --git a/docs/accessibility/chromevox.md b/docs/accessibility/chromevox.md
index c45edd5..05f6928 100644
--- a/docs/accessibility/chromevox.md
+++ b/docs/accessibility/chromevox.md
@@ -13,7 +13,7 @@
## Developer Info
-Code location: ```chrome/browser/resources/chromeos/chromevox```
+Code location: ```chrome/browser/resources/chromeos/accessibility/chromevox```
Ninja target: it's built as part of "chrome", but you can build and run
browser_tests to test it (Chrome OS target only - you must have target_os =
@@ -36,10 +36,12 @@
When developing a new feature, it may be helpful to save time by not having to
go through a compile cycle. This can be achieved by setting
```chromevox_compress_js``` to 0 in
-chrome/browser/resources/chromeos/chromevox/BUILD.gn, or by using a debug build.
+chrome/browser/resources/chromeos/accessibility/chromevox/BUILD.gn, or by using
+a debug build.
In a debug build or with chromevox_compress_js off, the unflattened files in the
-Chrome out directory (e.g. out/Release/resources/chromeos/chromevox/). Now you
+Chrome out directory
+(e.g. out/Release/resources/chromeos/accessibility/chromevox/). Now you
can hack directly on the copy of ChromeVox in out/ and toggle ChromeVox to pick
up your changes (via Ctrl+Alt+Z).
