WebAIM - Web Accessibility In Mind

E-mail List Archives

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

for

From: Mallory
Date: Jan 2, 2021 6:20AM

I suppose technically a button which can only be activated with the "r" key also passes 2.1.1.

Yet another reason to avoid performing "WCAG audits". I believe they're hurtful, and clients who want to only stick to it are cheaper served by any fly-by-night "a11y experts".

However reports should always put the "this is 110% unusable" issues under a "UX" heading or something, and not point to an SC.

cheers,
_mallory

On Fri, Jan 1, 2021, at 10:00 PM, Patrick H. Lauke wrote:
> 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