Changes

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

=== OSX and Linux === * Initial support with sync Sync chrome -> content calls for most common apis, with light weight caching to cut down on the heaviest api traffic. (Partly complete.)* A black list of clients known to have issues with e10s will be added for 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 covered by meta bug 1159326.

Tracking bugs=== Windows === See the [https:* {{bug|1159326}} - Tracking //wiki.mozilla.org/Electrolysis/Accessibility/Windows Windows e10s / a11y mitigation work for roll out to Aurora* {{bug|1029143}} - Implement accessibility Accessibility] wiki page for sandboxed e10smore information and status.