Getting Started with Orca and Chrome/Chromium
Be sure you are using at least the following versions:
Orca: Version 3.36.6 (and preferably 3.38.0 or later). IMPORTANT: Prior to Orca 3.32, Orca had absolutely no support for Chrome/Chromium. Orca 3.34.1 is the bare minimum version expected to work with Chrome/Chromium, and there have been a huge number of bug fixes in Orca's support since then.
- The current release version of Chrome/Chromium (additional fixes can be found in the "dev" channel).
How to Test
- If you're not using the versions of Orca and Chrome/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.
Most of Chrome/Chromium's keyboard shortcuts are quite similar to Firefox's. But Google has provided a list of Chrome/Chromium's native keyboard shortcuts.
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.
At this time, users are encouraged to report bugs on the Orca mailing list so that other testers can confirm the issue, and so the issue can be triaged to determine if the bug is in Orca or in Chromium.
Some key issues include, but are not limited to:
- Scrolling done by Orca is not fully working due to some issues in Chromium
- Presentation of large plain text files has a huge delay due to event floods from Chromium
- Links with a title attribute might not be presented correctly due to a bug in Chromium's accessible name calculation
- Because Chromium does not always give us the correct value for accessible_at_point, mouse review sometimes fails.
- Label inference (for form fields that the author didn't properly label) may fail if the widget is off-screen. (Still being debugged.)
- Because Chromium treats space followed by a quote as a single word boundary (unlike Firefox), Orca is combining two words into one when there's a space followed by a quote. Joanie will address this in Orca as Chromium is technically not wrong; just different.
- Live region presentation can be super chatty due to tons of events from Chromium. Joanie will attempt to filter the extra events out, but it may need to be fixed in Chromium.