W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > January to March 2014

Re: Semantic implications of tabindex="0"?

From: Mike Elledge <melledge@yahoo.com>
Date: Tue, 7 Jan 2014 20:02:06 -0500
Message-Id: <8B9C8C65-342A-4996-82F2-BA26CC4723CB@yahoo.com>
Cc: "Gunderson, Jon R" <jongund@illinois.edu>, "w3c-wai-ig@w3.org" <w3c-wai-ig@w3.org>
To: Karl Groves <karl@karlgroves.com>
Thanks, Karl and Jon. Your explanations make perfect sense. 

Mike

On Jan 7, 2014, at 5:47 PM, Karl Groves <karl@karlgroves.com> wrote:

> Certainly, and I should've mentioned in my response that it is important to add whatever role is appropriate when trying to create a custom widget. I was responding mostly to Mike's question "are there assumptions that users will have" -   the assumption they'll have is that the control will have whatever keyboard functionality a control with that role would have.  i.e. a textbox will accept arbitrary text input, a button will respond to keypress, arrow keys will traverse radio button options, etc.
> 
> 
> On Tue, Jan 7, 2014 at 5:39 PM, Gunderson, Jon R <jongund@illinois.edu> wrote:
>> Typically things that are focusable have some interactive behavior.
>> 
>>  
>> 
>> The use of “tabindex” to make natively non-interactive elements like DIV and SPAN interactive (e.g. keyboard focusable) is the basis of how ARIA technology allows developers to create keyboard accessibility widgets using ARIA technology.
>> 
>>  
>> 
>> http://www.w3.org/TR/wai-aria/usage#managingfocus
>> 
>>  
>> 
>> http://www.w3.org/TR/wai-aria-practices/#focus_tabindex
>> 
>>  
>> 
>> Jon
>> 
>>  
>> 
>>  
>> 
>> From: karlgroves@gmail.com [mailto:karlgroves@gmail.com] On Behalf Of Karl Groves
>> Sent: Tuesday, January 7, 2014 4:13 PM
>> To: Mike Elledge
>> Cc: w3c-wai-ig@w3.org
>> Subject: Re: Semantic implications of tabindex="0"?
>> 
>>  
>> 
>> Mike,
>> 
>> Natively tabbable items are a[href], area[href], button, input, object, select, and textarea. HTML5 adds menuitem.  IOW, things people can interact with.
>> 
>> Consequently, if focus arrives on something the assumption on the part of the user is likely to be "I can act on this.".   In fact when an element that is not focusable by default has a tabindex="0" (most elements that have no mapping), the element is mapped as 'editable text' in MSAA.  As a consequence, JAWS will read "editable" for the following  <h1 tabindex="0">Some heading</h1>
>> 
>>  
>> 
>> On Tue, Jan 7, 2014 at 4:27 PM, Mike Elledge <melledge@yahoo.com> wrote:
>> 
>> Hi All--
>> 
>>  
>> 
>> I have a question I hope you can answer. In reading about tabindex="0" it seems as if there are no limits to its application to non-focusable elements. I wonder, however, when it makes the most sense to use it. For example, are there assumptions that users will have based on the traditional targets of tabbing (i.e., form fields and links)?
>> 
>>  
>> 
>> Any thoughts on this?
>> 
>>  
>> 
>> Many thanks,
>> 
>>  
>> 
>> Mike Elledge
>> 
>> 
>> 
>> 
>> -- 
>> 
>> Karl Groves
>> www.karlgroves.com
>> @karlgroves
>> http://www.linkedin.com/in/karlgroves
>> Phone: +1 410.541.6829
>> 
> 
> 
> 
> -- 
> 
> Karl Groves
> www.karlgroves.com
> @karlgroves
> http://www.linkedin.com/in/karlgroves
> Phone: +1 410.541.6829
Received on Wednesday, 8 January 2014 01:02:37 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 13 October 2015 16:21:50 UTC