Potential failure technique for WCAG 2.1 SC 2.5.6 - Concurrent Input Mechanisms

Hi All,

I've got a question I'd like to pose to the group about a potential failure technique for the AAA WCAG 2.1 Success Criterion for Concurrent Input Mechanisms.

Here's the setup for the question:

A sighted web page user tabs with a keyboard into the content of the page and brings focus to a menu button widget.  Using a keyboard, the user opens the list of options for the menu button widget by pressing the space bar, then she arrows down in the dropdown list to the 3rd out of 5 options in the list. That 3rd option displays a visual focus indicator, as it should.  Next, the user grabs a mouse and hovers her cursor over the 1st of 5 options in the menu button drop down.

In order to satisfy SC 2.5.6, must the web page content allow for both the keyboard focused option and the mouse hovered option to display visual focus indicators simultaneously?

Is being able to see where keyboard input focus was last positioned on the page a requirement for being able to use a keyboard at any time, even if the user has hovered over the page with a mouse since the last keyboard maneuver?

Thanks for any feedback you may offer.

Brooks

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
Brooks Newton
Sr. Accessibility Specialist, Legal UX

Thomson Reuters
the answer company

Mobile: +1(918) 316-3949

brooks.newton@tr.com<mailto:brooks.newton@tr.com>

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *