WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: WCAG - Fail or not to - Static text tab-focusable in tables

for

From: Patrick H. Lauke
Date: Jan 1, 2021 2:00PM

On 01/01/2021 18:50, Abi James wrote:

> I would usually apply 2.1.1 keyboard operable as, while WCAG does not define "operable", we all understand that to be that keyboard operation a site must be actually operable for the user and so match the expected keyboard patterns. Wouldn't we fail a site that overrode tab key as the keyboard operation for moving focus?

No, not necessarily. 2.1.1 doesn't define normatively that the keyboard
experience must match any "expected" patterns. Only that there must be a
way to be able to use the keyboard.

Do you fail something announced as a button, but which reacts to Enter
but not Space, for instance? Again, this normatively passes 2.1.1. Yes,
you can then tell the client that really they should change it to match
the expected behaviour of a button, but to a strict reading of 2.1.1.
And the understanding for 2.1.1 also gives no indication that the
intention ever was to fail "unexpected"/"non-standard" keyboard operation.

P
--
Patrick H. Lauke

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