WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Web application - shortcut to manual

for

From: Patrick H. Lauke
Date: Jul 9, 2019 3:45AM

On 09/07/2019 10:20, Miriam Fukushima wrote:
> Thank you very much.
>
> That is the criteria I was referring to.
>
> Can a shortcut key then be considered as an alternative for the visual
> button? So that the button doesn't have to be accessible, only for mouse
> users.
>
> Because the visual indicator is a requirement of the application's
> concept, too.

Nominally, I think that yes, you can argue that while the visible button
is not keyboard-focusable/actionable (I assume), the same functionality
can be triggered using the keyboard by pressing F1, so 2.1.1 Keyboard is
nominally satisfied.

However, it may be confusing for sighted/partially-sighted keyboard
users nonetheless.

It probably depends on how long/complex the form is. If it's only a
handful of fields, I'd say that perhaps having an actual focusable
button next to each field that triggers the help is ok (even though it
adds a few extra tab stops). Whereas if the form is very long, doubling
the number of focus stops needed to complete it may end up
harming/inconveniencing keyboard users again as well. This is possibly
something that falls more in the usability/user testing side of the
debate...

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