693644 - [e10s] Despite fix for bug 677883, screen readers relying on iSimpleDOM fail to create virtual documents from the second tab onwards

Status: RESOLVED INVALID

(Core :: Disability Access APIs, defect)

Description

[Marco Zehe (:MarcoZ)]

Tested with latest trypserver build from bug 677883. While NVDA, which relies solely on IA2, works fine with that build in second or third opened tabs/content processes, screen readers like JAWS or Window-Eyes 7.51, which rely on iSimpleDOM, still are unable to create virtual documents in anything but the first tab.

STR:
1. Run JAWS or Window-Eyes.
2. Run the try-server build from http://ftp.mozilla.org/pub/mozilla.org/firefox/try-builds/[e-mail]-800d9f2b243d/try-win32/
3. Open any page in the first tab.

Result: Virtual buffer is being created, you can navigate with the arrow keys and get information about headings, links, etc.

4. Press Ctrl+T to open a new tab and enter any address. Press Enter.

Expected: Page should load and screen reader should start reading.
Actual may be one of the following:
a) Silence.
b) Announcement of document name, nothing else.
c) Announcement of document name for previous (first) tab.

5. Try to navigate with the arrow keys.

Result is one of the following:
a) No response.
b) Response corresponds to document of the first tab (like is the case with JaWS most often).

6. Press Ctrl+L or anything that gets focus into the chrome.
Result may be:
a) Focus is announced, one can navigate (JAWS).
b) Focus is not announced, screen reader remains silent and thinks it is still in virtual document of first tab (Window-Eyes).

Comment 1

[Marco Zehe (:MarcoZ)]

Old E10S bug, no longer valid.