WebAIM - Web Accessibility In Mind

E-mail List Archives

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

for

From: Moore,Michael (Accessibility) (HHSC)
Date: Mar 16, 2016 3:30PM

"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."

I totally agree but am going for the stretch argument anyway. Otherwise it probably will not be fixed.

Mike Moore
Accessibility Coordinator
Texas Health and Human Services Commission
Civil Rights Office

-----Original Message-----
From: WebAIM-Forum [mailto: <EMAIL REMOVED> ] On Behalf Of Jared Smith
Sent: Wednesday, March 16, 2016 3:19 PM
To: WebAIM Discussion List < <EMAIL REMOVED> >
Subject: Re: [WebAIM] WCAG Violation for use of tabindex=0 on static elements.

> 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