Getting Started with Orca and Chrome/Chromium
Orca's support for Chome/Chromium is ready. But you will need at least Orca 3.34.1 because it contains fixes that did not make it into the 3.34.0 release. Chrome/Chromium's support to work with Orca is getting close, but there are still some significant bugs which need to be fixed. For that reason, you should be using at least the "dev" channel of Chrome, which you can get from https://www.google.com/chrome/dev/?platform=linux.
How to Test
- If you're not using the versions of Orca and Chromium specified above, there's an excellent chance the bugs you're encountering have already been fixed. Please do not report bugs unless you are using these (or later) versions.
- Most of Orca's Chrome/Chromium support is part of its generic web support, the same support used by Orca to provide access to Firefox. Therefore, before you report a bug as a Chrome/Chromium bug, please test the same thing in Firefox. If the bug also exists in Firefox, please do not report it as a Chrome/Chromium bug. (You can of course report it as a generic web or Firefox bug.) We want to quickly identify problems which are only in Chrome/Chromium so we can address them immediately.
- When comparing Firefox with Chrome/Chromium to reproduce an issue, you are encouraged to maximize both the Firefox window and the Chrome/Chromium window. Maximizing windows is not normally necessary, of course. And it's not needed for general testing or use. However, some pages dynamically update what gets shown and hidden based on window size. Therefore you will get the most reliable results testing an issue in both Firefox and Chrome/Chromium by ensuring the Firefox and Chrome/Chromium windows have the same size. And the easiest way to ensure they have the same size is to maximize them both.
In Firefox, caret navigation can be toggled on/off with F7. There is no such shortcut (yet) for Chrome/Chromium. However, you can enable Chrome/Chromium's native caret browsing at the command line with --enable-caret-browsing. Doing this is not necessary for reading web pages or using web apps. But it is necessary for text selection.
In Firefox, enabling accessibility support is done automatically if Orca is detected. This does not happen (yet) for Chrome/Chromium. In order to enable accessibility support, you'll need to launch it with --force-renderer-accessibility. In addition, you will want to ensure that ACCESSIBILITY_ENABLED=1 is in your environment.
If all of the above makes perfect sense to you, great! Have at it! On the other hand, if it does not or you think you'll need help doing the above, please continue to be patient. We anticipate things will be ready and "just working" out of the box soon enough.
Some key issues include, but are not limited to:
- Scrolling done by Orca is not fully working due to some issues in Chromium
- Some dialogs might not be announced or announced correctly due to some issues in Chromium
- Text selection is sometimes announced incorrectly due to some issues in Chromium
- Chromium's native caret navigation (which is needed for text selection) can occasionally get stuck
- Label inference (for form fields that the author didn't properly label) may fail if the widget is off-screen. (Still being debugged.)