WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Web application - shortcut to manual

for

From: Miriam Fukushima
Date: Jul 9, 2019 3:20AM

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.

Kind regards, Miriam

On 09.07.2019 10:25, Patrick H. Lauke wrote:
> On 09/07/2019 08:30, Miriam Fukushima wrote:
>
>> And if we provide a shortcut key, we also have to provide the option
>> to change this to any other key as this is one criteria in the German
>> equivalent of WCAG.
>
> Just on that point, I assume you're referring to
> https://testen.bitv-test.de/index.php?a=di&iid=112&s=n which is the
> BITV inclusion of WCAG 2.1 2.1.4 Character Key Shortcuts
> https://www.w3.org/TR/WCAG21/#character-key-shortcuts
>
> Note that if you were going to go with F1, that key is exempt from the
> requirement of 2.1.4, which only relates to printable characters (and
> there's text in the BITV test procedure there to clarify that the
> F1-F12 keys don't fall under the test).
>
> As for "hijacking" the F1 to provide help for the web site/app and
> overriding the browser's F1 help, I'd say that's a mild/minor point,
> and as long as it's explained to the user, it's acceptable (and they
> can still trigger the browser help in other ways, or even by just
> focusing the address bar or other parts of the browser and hitting F1).
>
> P