WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Instructions for Custom Keyboard Shortcuts

for

From: Guy Hickling
Date: Jan 13, 2020 4:47PM

> in my opinion, 2.1.1 is a fail if your custom keyboard
shortcuts are not discoverable by the user (because in that case the
user can't operate the page using the keyboard)

Birkir, I suppose I have never thought my way through this reasoning quite
as rigourously as you have. But I agree with your logic, and I have also
actually followed it in testing many times. When I'm testing some custom
component that someone's invented, I try the obvious keys (usually Enter
and spacebar). I then try the arrow keys, just in case. After that I don't
try anymore on the basis that, although the designers maybe have provided
some weird key combination to operate it, I don't want to find it. So far
as I'm concerned, if they haven't provided one of the obvious, commonly
used keypresses to do it, then it's a 2.1.1 fail and I don't want to be
stopped from reporting it as such just because I happen to stumble a
solution that no ordinary user is likely to think of.
If one day a client does push back saying "If you press CTRL Shift XYZ then
turn three somersaults it will work" I will simply reply saying I couldn't
find it and refer them to 3.3.2!