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

And all applkications which works properly in 2017 stop to work? I use :focus (and tabindex=0 and tabindex=-1 in all my project with emulation of  select+option elements. 
The tabindex isn't described as deprecated. My solution works in all modern browsers. Ans when they stop to work?

I do not use tab-index greater than 0 but end of support 0 and -1 will cause frustration not only my by also frustration of my clients. They want to have select like field fully styled wiyhout JS and use of native select/option is inpossible because the select and <option/> are not stylable. I cannot for example make 40px height <option> working on all mobile browsers and not all PC browsers support it. It is needed to improve accessibility. Additionally no styles to change/remove dropdown arrow in select field.

Also no select field with double dropdown lists in HTL spec and I emulate it with my own control described with span, input type=adio and label AND TABINDEX=0/-1 + CSS3.  

Please do not remove but also add alternative for sequential access. The tab-index /nav-index proposal is discuted in CSSWG and many of users need it (with additional possibility of grouping it.

Please do not forget about absolute and fixed positionad elements. Part of solutions discuted on CSSWG is vulnerable in this case. 

W dniu 2017-11-22 10:18:30 użytkownik Léonie Watson <tink@tink.uk> napisał:
> 
> 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 Friday, 24 November 2017 18:14:22 UTC