To test the version of ChromeVox that runs on Chrome OS while running a desktop Linux, you can build the Chrome OS version of Chrome.
First add chromeos=1 to your GYP_DEFINES. (More info on GYP_DEFINES here)
If you want speech, you just need to copy the speech synthesis data files to /usr/share like it would be on a Chrome OS device:
After you do that, just run "chrome" (e.g. out/Release/chrome) and press Ctrl+Alt+Z, and you should hear it speak! If not, check the logs.
To run ChromeVox Next for all subsequently opened tabs and page navigations, open the ChromeVox options page by pressing Search+Shift+o, o; then, with focus in the web content, type ‘next’.
All newly opened tabs will run ChromeVox Next. The chrome of Chrome already uses ChromeVox Next to render its output by default.
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/chromevox.gyp. Regenerate build (ninja) files with
Subsequent builds will place unflattened files in the Chrome out directory (e.g. out/Release/resources/chromeos/chromevox/).
- hack directly on the copy of ChromeVox in out.
toggle ChromeVox to pick up your changes (via Ctrl+Alt+Z).
One can use an external debugger that talks to the Chrome debugging protocol to poke around inside of ChromeVox’s background page. An option specifically for emacs kite works ewll. Another options is to use the built-in developer console. Go to the ChromeVox options page with Search+Shift+o, o; then, substitute the “options.html” path with “background.html”.
ChromeVox can be run as an installable extension, separate from a linux Chrome OS build.
chrome/browser/resources/chromeos/chromevox/tools has the required scripts that pack ChromeVox as an extension and make any necessary manifest changes.