WebAIM - Web Accessibility In Mind

E-mail List Archives

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

for

From: Snahendu Bhattacharya
Date: Mar 17, 2016 8:08AM

There are two different aspect. Accessibility and Usability.

By following the guidelines we need to ensure we have better Accessibility
rather ease of access. We should not try to make things complex.

Question is why should I make static element keyboard focusable?

Keyboard users can be of two types. 'Keyboard only' and 'screen reader +
keyboard' users.

In either cases user has option to read through the entire page, either
using 'eyes' or by using 'assistive technology'.

We should not force our user to traverse through all the elements of the
page unless those areas or elements need some user interaction. That
increases number of keystrokes and ends in a very poor user experience.

One of the major purpose of Accessibility is 'P O U R', where O is
operability. To implement this, we should not make it unusable.

I think this can be the argument to focus.
On Mar 17, 2016 9:55 AM, "Andrew Kirkpatrick" < <EMAIL REMOVED> > wrote:

> This is definitely an area that I'd like to see clarified in the future.
> I would argue that text _is_ a user interface component, and if you have:
>
> <p tabindex=0>Some text</p>
>
> You have set the name and role by using a paragraph and by the paragraph
> having the text content. The browser may report the element as clickable
> (the state), so some of these concerns may actually be addressed. Of
> course there are accessibility support issues, but we will put that aside
> for now.
>
> The questions that I have about this type of interaction (apart from "is
> this really necessary?") are:
> Will a screen reader user know that this is a link or provides some other
> interaction and if so, know how to activate it and what it is for? (perhaps
> 2.4.4 if the effect is that a link is created, or 1.1.1 to make sure that
> the control has a name that describes the input, 4.1.2 just requires a name
> - 1.1.1 requires that it describes the purpose)
>
> Will a sighted keyboard user be able to know that this control is
> interactive and how to use it? (SC 2.4.7 for focus visibility. The how to
> use it is likely a question that will affect all users)
>
> So I would say that 1.1.1 and 2.4.7 are SC that I'd look at for this.
>
> Thanks,
> AWK
>
> Andrew Kirkpatrick
> Group Product Manager, Accessibility
> Adobe
>
> <EMAIL REMOVED>
> http://twitter.com/awkawk
> http://blogs.adobe.com/accessibility
>
>
>
>
>
>
>
>
> On 3/16/16, 20:30, "WebAIM-Forum on behalf of Jonathan Avila" <
> <EMAIL REMOVED> on behalf of
> <EMAIL REMOVED> > wrote:
>
> >> Adding tabindex=0 makes it a User Interface Component so 4.1.2 now
> applies to these traditionally non-widget components
> >
> >This brings up a question I have always wondered -- what role can you
> apply to text? None? Presentation? There are some rare situations where
> you may want to place text in the focus order and if you do -- what role
> would you be required to use in order for it to meet SC 4.1.2?
> >
> >Jonathan
> >
> >