Commit 5da1390c authored by Katie D's avatar Katie D Committed by Commit Bot

Fix links in Chrome OS TTS documentation.

The Chromevox instructions are a relative link. All the other links
I added last were backwards.

NOTRY=true

Bug: none
Change-Id: Iec684256f0d8ced7061aded6f3562ba0fde0be6f
Reviewed-on: https://chromium-review.googlesource.com/956500Reviewed-by: default avatarDavid Tseng <dtseng@chromium.org>
Commit-Queue: Katie Dektar <katie@chromium.org>
Cr-Commit-Position: refs/heads/master@{#541914}
parent 8a5a7135
......@@ -22,11 +22,11 @@ You must hide the existing TTS extension because extension keys must not be
duplicated, and ChromeOS will crash if you try to load the unpacked extension
while the built-in one is already loaded.
To test, use the [https://chrome.google.com/webstore/detail/tts-demo/chhkejkkcghanjclmhhpncachhgejoel](TTS Demo extension)
To test, use the [TTS Demo extension](https://chrome.google.com/webstore/detail/tts-demo/chhkejkkcghanjclmhhpncachhgejoel)
in Chromeos. This should automatically recognize the unpacked TTS extension
based on its manifest key. You can also use any site that uses a web speech API
demo. In addition, the Chrome Accessibility team has a
[https://chrome.google.com/webstore/detail/idllbaaoaldabjncnbfokacibfehkemd](TTS Debug extension)
[TTS Debug extension](https://chrome.google.com/webstore/detail/idllbaaoaldabjncnbfokacibfehkemd)
which can run several automated tests.
## Updating
......@@ -102,9 +102,9 @@ git commit -a
repo upload .
```
After submitting, inform the [mailto:chrome-a11y-core@google.com](Chrome Accessibility team)
After submitting, inform the [Chrome Accessibility Team](mailto:chrome-a11y-core@google.com)
so that they can update their local copies of TTS per the
[https://chromium.googlesource.com/chromium/src/+/lkgr/docs/accessibility/chromevox_on_desktop_linux.md](Chromevox instructions).
[Chromevox instructions](chromevox_on_desktop_linux.md).
## Ebuild
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment