Community
Participate
Working Groups
Specifically: - Using the right/left arrow keys does not expand/collapse a tree node. - Alt+C only moves to the Contents tab. Once there, you can't use Alt+C or the right/left arrows to move between tabs. - Using the down arrow to move to the next topic node does not work. - Using the up arrow to move to the previous topic node does not work. - Using Home/End to scroll all the way up or down does not work. When Microsoft Narrator (or no screen reader at all) is used, these keyboard shortcuts work. The first two problems are significant: - With Jaws running, the user cannot expand/collapse tree nodes and so the help cannot be navigated beyond the second level navigation entries. - With Jaws running, the user cannot move to the other tabs (the Search tab can only be opened by running a search). The other problems are not as significant - all have other keyboard shortcut combinations that can achieve the same thing.
Witn Microsoft Narrator (or no screen reader at all) working well and Jaws not, it clearly poinst at Jaws as the source of the problem.
Jaws consumes key strokes and does not pass to our page for processing and navigating the tree. Almost every key or key combination I can image has a special meaning assigned. I have found out that with Jaws 6.0.407 the following combinations produce the desired result: for up arrow (moving up in the tree or selecting a tab) use ctrl + shift + up arrow, for down arrow (moving down in the tree) use ctrl + shift + down arrow, for left arrow (collapsing a branch) use alt + left arrow, for right arrow (expanding a branch) use alt + right arrow.
I met with the accessibility centre to discuss several accessibility bugs that I opened against Eclipse. They advised me to leave this bug open for now (they were going to investigate Jaws behavior with the help). I have passed your latest comment on to them and asked them what they want me to do with this bug. I wouldn't want to close it outright - I would want to transfer it to the doc component and hope that they can add the keystroke combinations that you mention to the help page that covers this stuff. For now, though, I'm going to wait to hear back from the accessibility centre.
Jennifer, who in the Accessibility Center did you contact? I also have been working with them regarding this for the standalone/infocenter help system package. I'd like to stay in sync. Konrad, thanks for finding those key combinations. How difficult was it to find them? Was it trial-and-error, or something logical that had you find the combinations? I'm asking because we're seeing inconsistent results in JAWS 6 for the key combinations to go between ToC frame, Search results, Content frame. Sometimes they work in JAWS and sometimes not. If there is a combination for that desired behavior in JAWS ("go to ToC tab and then into tree", "go to contents frame and then into page", etc), even if it is different from the other, it would be good to have. --Lee Anne
I was scared to test on Jaws as it is expensive, and an older demo version of an Jaws destroyed my Windows XP installation once, I think it was Win 2k only version. That demo is the newest and so far my machine is still working. I could not figure out key combination from Jaws Help, so I employed a monkey gave it the keyboard and it found the keys for me. :-)
Marking as P4 - unlikely to be looked at for 3.1.
The accessibility of help is being improved for Eclipse 3.3. I'll post an update as our plans get more dtail.
I have been testing with Window-Eyes and that also consumes keystrokes causing the help system and other applications to not respond as expected. Jennifer, is there any word from the accessibility center?
Added Rich on cc so that he can respond to Chris's question: "I have been testing with Window-Eyes and that also consumes keystrokes causing the help system and other applications to not respond as expected."
Chris, I do know that testing with JAWS is going to be important for our products. Not only testing with Window-Eyes.
(In reply to comment #8) > I have been testing with Window-Eyes and that also consumes keystrokes causing > the help system and other applications to not respond as expected. > Jennifer, is there any word from the accessibility center? Turn on CTRL+SHIFT+A in Window-Eyes and then navigate it. Also, I believe placeing a role of application around the tree DIV automatically will switch Window-Eyes to the appropraite mode.
I'm not seeing this problem using Jaws 11.0 and I20101005-0800.
