WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Keyboard focus only

for

From: Patrick H. Lauke
Date: Feb 11, 2019 5:36AM

On 06/02/2019 01:17, Jonathan Avila wrote:

> My concern is for users such as low vision users who switch back and forth between using the mouse and keyboard for navigation. There are cases where the user may use the keyboard and then the mouse and then may expect to take up where the keyboard was. Similar issue may happen for alternative input users as well who may switch between speech recognition and some other tool such as eye tracking. My preference would be to give the user control if keeping the keyboard focus is absolutely not possible. There was a discussion on github in the WICG https://github.com/WICG/focus-visible/issues/128

While this buried the lede a bit, I'd actually explicitly state that I'd
favor an approach using :focus-visible
(https://github.com/WICG/focus-visible) - as there is potential here for
user agents to provide override mechanisms if needed.

And while it's referenced from the readme of the :focus-visible
repository, I'd also point to this little musing I wrote a while ago
https://developer.paciellogroup.com/blog/2018/03/focus-visible-and-backwards-compatibility/

P
--
Patrick H. Lauke

www.splintered.co.uk | https://github.com/patrickhlauke
http://flickr.com/photos/redux/ | http://redux.deviantart.com
twitter: @patrick_h_lauke | skype: patrick_h_lauke