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

+1 to what appears to be some soft consensus firming up :-)

 

JF

 

From: Cynthia Shelly [mailto:cyns@microsoft.com] 
Sent: Monday, October 20, 2014 9:00 AM
To: chaals@yandex-team.ru; White, Jason J; Janina Sajka
Cc: Joseph Scheuhammer; Marco Zehe; public-html@w3.org; W3C WAI Protocols &
Formats
Subject: RE: Proposal to change documentation on tabindex to strongly
discourage values greater 0

 

I like the idea of this new structure.  I think we should start work on that
AND do what the original mail suggested, to change the docs to discourage
tabindex >1 in the short term. I would also like to deprecate tabindex
values >1, but that might need to wait until this new thing is more
developed.

Sent from my Windows Phone

  _____  

From: chaals@yandex-team.ru
Sent: ‎10/‎20/‎2014 7:40 AM
To: White, Jason J <mailto:jjwhite@ets.org> ; Janina Sajka
<mailto:janina@rednote.net> 
Cc: Joseph Scheuhammer <mailto:clown@alum.mit.edu> ; Marco Zehe
<mailto:mzehe@mozilla.com> ; public-html@w3.org; W3C WAI Protocols
<mailto:public-pfwg@w3.org> & Formats
Subject: Re: Proposal to change documentation on tabindex to strongly
discourage  values greater 0



20.10.2014, 15:55, "White, Jason J" <jjwhite@ets.org>:
>> -----Original Message-----
>> From: Janina Sajka [mailto:janina@rednote.net]
>> Sent: Monday, October 20, 2014 9:31 AM
>> A feature such as Charles describes is useful, and has already been
>> defined for DAISY (ANSI/NISO Z39.86).
>>
>> An important additional requirement is a reliable way to escape out of
>> the local mode--either forward beyond the structure, or back to
>> something before it. It must be easy to "go local" or "stay global."
>
> In general, I agree. However, I understood the scope of Charles' proposal
to be limited to locally influencing the navigation sequence when it reaches
a given subtree, not encompassing anything that would potentially trap the
user in a navigation cycle comprising part of a document.

Yep. I suspect we are on the same page.

And to return to Marco's original proposal, I think we would do well not to
call this thing tabindex, unless there is some sensible way of makin olduses
of the markup do new and more useful tricks.

But here, I'm not sure how to dothat without making existing things worse.

cheers

> Clarification would of course be welcome.
>
> ________________________________
>
> This e-mail and any files transmitted with it may contain privileged or
confidential information. It is solely for use by the individual for whom it
is intended, even if addressed incorrectly. If you received this e-mail in
error, please notify the sender; do not disclose, copy, distribute, or take
any action in reliance on the contents of this information; and delete it
from your system. Any other use of this e-mail is prohibited.
>
> Thank you for your compliance.
>
> ________________________________

--
Charles McCathie Nevile - web standards - CTO Office, Yandex
chaals@yandex-team.ru - - - Find more at http://yandex.com