Ensure simulated controls are keyboard accessible - Morpheus
GENERAL
TESTING
GENERAL
TESTING
Description
The left hand side navigation of the environment provides a series of links that can be used to navigate through pages of content. A control is provided at the top of the navigation that when activated allows the user to either expand or collapse the side navigation entirely. However, this control currently does not receive keyboard focus and therefore cannot be activated by a keyboard only user.
Developers must ensure that all simulated controls implemented provide support for keyboard accessibility. As this control is created by placing event handlers on an <li> element, the element itself must be assigned <tabindex="0"> in order to draw keyboard focus, as well as device-independent event handlers to allow keyboard only users to activate the control with the "Enter" key.
Order isn't perfect, and the control is a little finicky as tested in Chrome, this does indeed bring this functionality into keyboard-only use and removes reliance on touch/mouse.
Matt Clare April 5, 2017 at 1:35 PM
Affects 12/Master as of Wednesday April 5, 2017
Matt Clare October 3, 2016 at 1:50 PM
... this could use a more prescriptive response...
The left hand side navigation of the environment provides a series of links that can be used to navigate through pages of content. A control is provided at the top of the navigation that when activated allows the user to either expand or collapse the side navigation entirely. However, this control currently does not receive keyboard focus and therefore cannot be activated by a keyboard only user.
Developers must ensure that all simulated controls implemented provide support for keyboard accessibility. As this control is created by placing event handlers on an <li> element, the element itself must be assigned <tabindex="0"> in order to draw keyboard focus, as well as device-independent event handlers to allow keyboard only users to activate the control with the "Enter" key.