Community
Participate
Working Groups
The Orion editor doesn't work well with JAWS/NVDA in Chrome. This is odd, because the editor works very well in Firefox and IE11 with JAWS/NVDA, and Safari with VoiceOver. In Chrome, typed characters are spoken correctly, but the screen reader just says "blank" or "down arrow" (for example) when navigating from line to line (or word to word, etc). Sometimes, the first line in the editor is spoken when the editor gets focus. Tried with editor in Orion and with demo: http://libingw.github.io/OrionCodeEdit/
Decided to try ChromeVox (screen reader from Google) and navigating in the editor works much better than under JAWS/NVDA in Chrome. Not sure what's going on here.
Bizarre. Google support recommends using Firefox if you are using JAWS or NVDA with Google Docs: https://support.google.com/drive/answer/6034939?hl=en
I'd like to leave this bug open (instead of closing as "Not Eclipse") in order to investigate further if/when the Chrome accessibility problems are fixed.
This is a problem with contenteditable in Chrome. SSQ and I tried running JAWS and NVDA over a simple contenteditable example (and even a simple textarea example!) and they both failed in approximately the same way that the Orion editor fails.
Actually, <textarea> does work in Chrome under NVDA (but not JAWS). http://www.w3schools.com/tags/tryit.asp?filename=tryhtml_textarea (So ignore the bit about the simple textarea in comment 4). Back to contenteditable, which is what we need to work. Here's a Chromium bug that may be related: https://bugs.chromium.org/p/chromium/issues/detail?id=379818&q=hotlist%3DAccessibility&colspec=ID%20Pri%20M%20Stars%20ReleaseBlock%20Cr%20Status%20Owner%20Summary%20OS%20Modified
There may be hope here. I looked through a bunch of Chromium bugs. (btw, ignore the one in comment 5 for now - it's only on Mac/VoiceOver). I found this one ("implement IAccessibleText") that was marked fixed in Oct 2015: https://bugs.chromium.org/p/chromium/issues/detail?id=347859 Then I saw this NVDA bug that connected to Chrome IAccessibleText in Nov 2015: https://github.com/nvaccess/nvda/issues/2634 To get these 2 fixes, you need at least Chrome 47 (I have 49) and NVDA 2015.4 (I was still running NVDA 2015.3). I have now upgraded my NVDA to 2016.1. I see also that JAWS 17 just came out in March 2016 (I still have JAWS 16) so I will upgrade JAWS as well and test with the latest screen reader versions.
Tested Orion Editor with Chrome 49 and NVDA 2016.1, and this works quite well. I did need to remove the textbox role from the Orion editor because apparently Chrome "flattens" the contents if role="textbox" is present. (See https://bugs.chromium.org/p/chromium/issues/detail?id=542998) It's not quite as stable as in Firefox; I can cause NVDA to think it's on a different line by arrowing quickly or using pagedown multiple times in a large file. It will get back on track if you use arrows again or refocus the window. Not quite sure the precise steps to replicate this behavior. However, the general behavior is way better than before, which was just "blank". I also tried JAWS 17, which still does not work in Chrome in contenteditables. Leaving bug open to retest in newer versions of Chrome, and to retest when JAWS fixes its contenteditable support.
Here is the change to Orion Editor to remove the textbox role: http://git.eclipse.org/c/orion/org.eclipse.orion.client.git/commit/?id=b64439b0c74095cdbc7c57e184c9c0933f87e489 Still leaving bug open, as stated in comment 7.
Here's an open Chrome issue that should help JAWS read contenteditables when it is fixed: https://bugs.chromium.org/p/chromium/issues/detail?id=605670
Just a note that the chrome bug mentioned in comment 9 has been marked as Fixed. And I tried the latest development build of chromium with JAWS 18, no improvement to me.
Closing as part of a mass clean up of inactive bugs. Please reopen if this problem still occurs or is relevant to you. For more details see: https://dev.eclipse.org/mhonarc/lists/orion-dev/msg04114.html
Noticed this bug was archived, but this has been working for a while now. Closing.
