WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: WCAG Violation for use of tabindex=0 on static elements.

for

From: Jared Smith
Date: Mar 16, 2016 2:19PM

> Are there specific WCAG AA guidelines that I can cite for this problem?

I don't think so. 2.1.1 only requires that functionality be operable
via a keyboard - which it is. It doesn't indicate anything about
efficiency, having non-actionable elements placed in the keyboard
navigation flow, etc.

F44, as Marc suggested, is quite a stretch. It deals with defining a
navigation order that is not logical. In your situation, the order is
logical - it's just that there's a lot of useless navigation elements
thrown into the mix.

Despite what WCAG requires, this is clearly an issue for end users and
should be fixed.

Any accessibility effort that is so reliant upon WCAG that it neglects
to address end user issues that are not defined as WCAG failures will
rarely result in good accessibility.

Jared