Fix issue of inconsistent focus/keyboard behaviour in decktree
Description
Activity
Abi James October 3, 2017 at 7:07 PM
@Stavros Maroulis feedback on branch late 3/10/17:
need aria-hidden=true on the icons for slide and sub-deck in the tree (hide them from screen reader)
the new hidden menubar button is now in the tab order when the slide is in focus (i.e. the elipse button is on display). This isn't critical but if you can improve it easily that would be good.
Abi James October 3, 2017 at 8:51 AM
Testing on 3rd Oct 2017 - tab into the deck tree and tab out works correctly. Arrow up/down moves through slides and sub-decks. Slide in a sub-deck are not treated as nodes on the tree but I think that is correct given we are using the context menu as a sub-branch. To load a slide then must use Enter (space-bar scrolls the tree). Once a slide is loaded right arrow opens the context menu and left arrow closes it. Tab is required to move through the context toolbar.
Notes for improvement:
spacebar should also open the link that has focus
the context menu is only available once a slide is loaded. This is not the same functionality as for a mouse user but I think it is a limitation we can live with
Further testing with a screen reader is required. also the context menu tagging for a screen reader can be improved.
Abi James August 10, 2017 at 1:26 PM
Also found that context button to reveal the slide action buttons are not in the tab order. The toolbar is displayed when you use right arrow on the slide which is the correct keyboard behaviour. But as the up/down arrow keys do not affect focus, this is not a consistent behavior.
Abi James June 4, 2017 at 2:28 PM
@Stavros Maroulis Ali has suggested that if you have time to look at this issue before the hackathon it would be helpful. Otherwise we will try to fix it then.
Abi James May 26, 2017 at 12:57 PMEdited
Expected behaviour tab into the list of slides then use up/down arrows to select a slide; enter/spacebar to activate the. change of slide. Currently all slides are in the tab order as they are links.
Description of expected keyboard behaviour in a tree widgit: https://www.w3.org/TR/wai-aria-practices-1.1/#TreeView .
However as we currently do not expand/contract nodes then we could also follow the model for a menu which is a bit simpler and used in similar apps (eg Google Slides): https://www.w3.org/TR/wai-aria-practices-1.1/#menu
Tagging @Stavros Maroulis in case this has an impact on drag/drop for reordering.
Details
Assignee
Stavros MaroulisStavros MaroulisReporter
Abi JamesAbi JamesLabels
Priority
MajorWho's Looking?
Open Who's Looking?
Details
Details
Assignee
Stavros MaroulisReporter
Abi JamesLabels
Priority
Major
Once you have tabbed into the decktree so that a slide has focus, there is inconsistent keyboard behaviour
tab results in focus being moved to the next slide but the active slide stays the same. Pressing enter changed to the slide which has focus. This also works with a screen reader
using the up/down arrow within the decktree results in the slide changing to the next slide. But focus remains on the original slide. In addition when using a screen reader, the arrow keys leads to the link to the next slide being announced but the slide does not change and pressing enter activates the slide that has focus (a different one).