Changes

Accessibility clients require direct access to information about content, which in . In non-e10s was this information is queried directly using sync calls into the DOM. These calls generally came in arrive on the application main or UI thread of the application and expect a response on return. With e10s, the chrome process generally communicates with content through asynchronous interfaces. This is incompatible with current a11y clients. As such the Accessibility Team is currently working on a two phase approach to getting accessibility working under e10s:

* Initial support with sync chrome -> content calls for most common apis, with light weight caching to cut down on the heaviest api traffic. (Mostly complete.)* A black list of clients known to have issues with e10s will be addedfor roll out to Aurora and beyond. When a blacklisted client is detected Firefox will prompt the user to disable e10s and restart. This work is covdered covered by meta bug 1159326 listed below.

* Eventual removal of the blacklist once we are ready to drop support for non-e10sand A11y caching support is fully implemented.

Tracking bugs:* {{bug|1159326}} - Tracking e10s / a11y mitigation work for roll out to Aurora* {{bug|1029143}} - Implement accessibility for sandboxed e10s