Re: Proposal to change documentation on tabindex to strongly discourage values greater 0

On 22/11/2017 00:17, Vader wrote:
> In my opinion the tabindex shall be moved to CSS as nav-index or 
> tab-index with current behaviour and values because the tab order is 
> dependent on layout of website. For example absolute or fixed 
> positioning to bottom. Only meaning of 0 shall be clarified as FIRST 
> FREE NOT USED INDEX. Then setting tab-index to 1000 shall put the 
> element at the end of tab queue.

It's unlikely that the tabindex attribute will be dropped from HTML, but 
there are discussions happening about the disconnect between the tab 
sequence and the visual sequence of content. The CSS Accessibility Task 
Force (a joint TF between the CSS WG, APA WG, and ARIA WG) is one place 
where this is happening:
https://www.w3.org/WAI/APA/task-forces/css-a11y/

There are also proposals for CSS based spacial navigation, as an 
alternative to conventional tab navigation. One such proposal is being 
discussed in the Web Platform Incubator Community Group (WICG):
https://discourse.wicg.io/t/proposal-spatial-navigation-for-the-web/2402

> Because elements with tab-index="-1" (I use this, please don't remove 
> behaviour for click!) are focusable ALSO BY MOUSE or TOUCH, there shall 
> be additional value "none" as true default value (not focusable by click 
> and not focusable by tab key.
> the "-1" is not true default now. elements without tabindex are not 
> focusable by mouse. ALL BROWSERS treat elements with tabindex="-1" as 
> focusable by mouse. Only IE have here small problem with <span> element 
> inside element with tabindex="-1".

The definition for the tabindex attribute is here:
http://w3c.github.io/html/editing.html#the-tabindex-attribute

If you think it can be improved, please file an issue and include your 
suggested changes, here:
https://github.com/w3c/html/issues/new/

Thanks.

Léonie.


-- 
@LeonieWatson @tink@toot.cafe tink.uk carpe diem

Received on Wednesday, 22 November 2017 09:19:06 UTC