Re: Semantic implications of tabindex="0"?

Which is kinda bad, when you think about it… Potential confusion alert. The last thing users need is a bunch of non-editable objects being announced as editable due to tabindex attributes with a value of 0 assigned to them...

/Denis



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

> 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