WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Tab navigation for non-interactive content?


From: Jonathan Avila
Date: Oct 28, 2016 10:38AM

> 1. Jonathan, can you post that conversation here, or link to it, I'd like to read it.



Jonathan Avila
Chief Accessibility Officer
703.637.8957 (Office)

Visit us online: Website | Twitter | Facebook | Linkedin | Blog
Check out our Digital Accessibility Webinars!

-----Original Message-----
From: WebAIM-Forum [mailto: <EMAIL REMOVED> ] On Behalf Of Birkir R. Gunnarsson
Sent: Friday, October 28, 2016 12:23 PM
To: WebAIM Discussion List
Subject: Re: [WebAIM] Tab navigation for non-interactive content?

1. Jonathan, can you post that conversation here, or link to it, I'd like to read it.
Yes, there are occasionally reasons for sometimes using tabindex="0", Ihave yet to find any reason for using tabindex>0 (it always ends up a mess).

2. Wel, if you need to format a disabled formfield you can use aria-disabled="true" use CSS to make it look disabled, and use Javascript to make sure user can't interact with it.
In any case, isn't it more politically correct to call them "form fields with disabilities" rather than "disabled form fields"? ;) -B

On 10/28/16, Patrick H. Lauke < <EMAIL REMOVED> > wrote:
> On 28/10/2016 15:06, Jonathan Avila wrote:
>> So you can visually format it more than can be done with input @readonly.
> I'm not aware of anything style-wise that can't be achieved on an
> input...but I'll take your word for it. And again, if you feel there
> is a strong enough case that can be argued, then the developer can
> safely ignore the "SHOULD NOT" wording in the warning.
> P
> --
> 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
> > > archives at http://webaim.org/discussion/archives
> >

Work hard. Have fun. Make history.