Community
Participate
Working Groups
Need to add ARIA semantics to the sidebar navigator in both the tree view and the outline view. We should follow these design patterns for the tree: http://www.w3.org/WAI/PF/aria-practices/#Site_Navigator_General http://www.w3.org/WAI/PF/aria-practices/#Site_Navigator_Tree http://www.w3.org/WAI/PF/aria-practices/#TreeView and follow these design patterns for the outline view: http://www.w3.org/WAI/PF/aria-practices/#Site_Navigator_Tabbed_Style (use Option 1 for single-select list) http://www.w3.org/WAI/PF/aria-practices/#Listbox
We did some initial work on this. Added various ARIA roles and other necessary elements. * http://git.eclipse.org/c/orion/org.eclipse.orion.client.git/commit/?id=34a5f8c * http://git.eclipse.org/c/orion/org.eclipse.orion.client.git/commit/?id=12d08de However we are still having a major problem with the NVDA screenreader. While NVDA is active, it consumes keyboard events that are supposed to change keyboard focus and selection in the navigator. This completely breaks the keyboard interaction with the navigator. The Orion dropdown menus behave much better: you can navigate through them using the keyboard while NVDA is active, and it reads the active item each time you move the cursor. The dropdowns are rendered as nested HTML lists, whereas the navigator (and Orion's "explorer" widgets in general) are HTML tables.
http://git.eclipse.org/c/orion/org.eclipse.orion.client.git/commit/?id=e461c7d Follow up. Still doesnt' give the behavior we wanted.
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/msg03444.html
