W3C home > Mailing lists > Public > public-html@w3.org > October 2014

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

From: Richard Schwerdtfeger <schwer@us.ibm.com>
Date: Fri, 17 Oct 2014 10:26:41 -0500
To: chaals@yandex-team.ru
Cc: Joseph Scheuhammer <clown@alum.mit.edu>, "White, Jason J" <jjwhite@ets.org>, Marco Zehe <mzehe@mozilla.com>, "public-html@w3.org" <public-html@w3.org>, W3C WAI Protocols & Formats <public-pfwg@w3.org>
Message-ID: <OF495C9CB9.1A5DAAD5-ON86257D74.0054AED7-86257D74.0054D76D@us.ibm.com>

We should definitely work in parallel with SVG.

Note: there is a joint task force now being formed between PF and SVG. We
are ironing out the last pieces of the charter. Fred Esch and I will be

Rich Schwerdtfeger

From:	chaals@yandex-team.ru
To:	"White, Jason J" <jjwhite@ets.org>, Joseph Scheuhammer
            <clown@alum.mit.edu>, Marco Zehe <mzehe@mozilla.com>,
            "public-html@w3.org" <public-html@w3.org>
Cc:	W3C WAI Protocols & Formats <public-pfwg@w3.org>
Date:	10/17/2014 10:13 AM
Subject:	Re: Proposal to change documentation on tabindex to strongly
            discourage  values greater 0

17.10.2014, 16:24, "White, Jason J" <jjwhite@ets.org>:
>> -----Original Message-----
>> From: Joseph Scheuhammer [mailto:clown@alum.mit.edu]
>> Whatever happens in terms of tabindex -- restrict its use to zero or -1,
>> or introduce context/hierarchy/scoping rules -- it looks like focus
>> navigation is a general issue with respect to multiple markup languages.
> In that case, if we're planning to develop a successor to tabindex as
some have suggested in this thread, it ought to be created and then
proposed for inclusion in SVG.

Given that SVG can be integrated directly into HTML, it makes more sense to
work in parallel with them.

I note that they already had a concept of focus navigation that was
probably more like what we are looking for than the current tabindex.

> Harmonization with a future version of HTML would, of course, also be
desirable. It isn't clear to me what range of use cases would need to be
addressed, nor what the requirements are.

A use case is to build a component that is used in various pages, in
different locations, and locally assign tabindex within it, but not have
that tabindex override the order of tabbing around the rest of the page.

So the requirement *might* be something like being able to scope a set of
tabindex attributes, such that they only apply within the scope.



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

(image/gif attachment: graycol.gif)

Received on Friday, 17 October 2014 15:27:13 UTC

This archive was generated by hypermail 2.4.0 : Saturday, 9 October 2021 18:46:11 UTC