WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Tab navigation for non-interactive content?


From: Jonathan Avila
Date: Oct 28, 2016 8:06AM

> But then why isn't it in a readonly field?

So you can visually format it more than can be done with input @readonly.


-----Original Message-----
From: WebAIM-Forum [mailto: <EMAIL REMOVED> ] On Behalf Of Patrick H. Lauke
Sent: Friday, October 28, 2016 10:05 AM
Subject: Re: [WebAIM] Tab navigation for non-interactive content?

On 28/10/2016 14:57, Jonathan Avila wrote:

> Sam Joehl and I had a twitter conversation with Steve that doesn't
> seemed to be listed in the thread where we list some situations where
> it is important. For example, for terms of service or scrolling
> areas. If the scrolling area is not keyboard focusable or there is
> not keyboard focusable content in it a keyboard only user or a user of
> speech recognition will not be able to access that content outside the
> scrollable area.

And this is why the warning is a "SHOULD NOT", rather than a "MUST NOT".
If you can justify the use of tabindex greater than zero on something with good conscience, then that's fine.

> There also may be some other readonly type content that isn't in a
> readonly field like redemption or promotion codes or other things that
> may need to be copied via the keyboard where the user may not have
> access to caret browsing, etc.

But then why isn't it in a readonly field?

Patrick H. Lauke

www.splintered.co.uk | https://github.com/patrickhlauke http://flickr.com/photos/redux/ | http://redux.deviantart.com
twitter: @patrick_h_lauke | skype: patrick_h_lauke