WebAIM - Web Accessibility In Mind

E-mail List Archives

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


From: Birkir R. Gunnarsson
Date: Dec 31, 2020 9:29PM

That's why I do it very rarely, and only in cases where I believe
there's an honest and major fail for certain users with disabilities,
e.g. keyboard only users. In those cases I back the opinion up with a
documented explanation, sometimes accompanied by a test page or video.

WCAG does not cover all major accessibility/usability fails. More
often, the success criteria are vague or open ended enough to require
interpretation or context. While adherence to a standard is good;
having standards is absolutely necessary;
but usability for the largest possible group of people is what
ultimately makes a difference.

At the end of the day (or year), accessibility is making sure people
with differing abilities can use your website/mobile app/digital
platform. I am willing to stake my reputation on that stance. So far
it's not been called into question frequently.

On 12/31/20, Patrick H. Lauke < <EMAIL REMOVED> > wrote:
> On 31/12/2020 16:42, Birkir R. Gunnarsson wrote:
>> I guess it's the luxury of working with one program ;) I can use the
>> "Birkir says it's a fail" without having to exercise WCAG gymnastics.
> A counterpoint, of course, is that in the worst case you're just making
> stuff up and saying it fails WCAG, which does the client (and your
> reputation) a disservice...
> 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
> > > > >

Work hard. Have fun. Make history.