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

Brooks wrote:
> So, I think I agree with where you are going with this.  … it is not OK to remove keyboard focus indication in the dropdown list of menuitems when user simply hovers menuitems, but does not click on any of them?

And Patrick said:
> As long as once the user goes back to the keyboard and moves the focus again the newly focused item is highlighted/visibly focused, that would be fine to me.


I’m not sure about that, not due to 2.5.6, but for 2.4.7 Focus Visible. It still a keyboard-operable interface, just because you move the mouse doesn’t mean it isn’t keyboard operable, so I think it still applies.

I guess “a mode of operation where the keyboard focus indicator is visible” could mean it appears when tabbing, but it doesn’t seem like a good idea to over-ride focus styles. If you haven’t tabbed and there is no focus, fine. But if something is in focus via the keyboard, shouldn’t it maintain that until the focus moves?

Cheers,

-Alastair