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 30, 2020 8:19AM

This should be a violation under either 2.4.3 (focus order) or even
2.1.1 (keyboard). If the table is large and there is no mechanism to
skip past it it could be near impossible for a keyboard only user to
navigate to anything on the page after the table.
Yes, 2.1.1 is a stretch, but I'd say 2.4.3 is applicable.
And for general keyboard usability, this is just a terrible implementation.
Not sure about this particular framework but Javascript could be added
to strip tabindex="0" from all the elements in the table (at least all
static elements, you'd just need a suitable selector to identify
The important thing is to file this as a bug with the framework
vendor. Ultimately it's their responsibility to fix, but they won't
fix unless it's logged and promoted as a bug.
I'm sure we'd all be happy to comment or promote if we know where the
bug is filed.

On 12/29/20, Vaibhav Saraf < <EMAIL REMOVED> > wrote:
> Hi Everyone,
> This is a question on fail or not to, the application in hand uses ng-grid
> of Angular 10, the grid in its defaults makes every cell tab-focusable. As
> a result all the static text and empty fields take tab-focus.
> I am really confused whether to fail this or not. I referred a few older
> discussions on the list archives and on github, what I can conclude is that
> it is not a violation to make a static text focusable, but ofcourse it is
> not the right thing for usability. I want to know your thoughts whether
> having all the cells taking focus for a large table including the empty
> cells is the right thing or not?
> And is there a good reference on how to implement a better version of this
> using ng-grid?
> Thanks,
> Vaibhav
> > > > >

Work hard. Have fun. Make history.