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

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

From: Shane McCarron <shane@aptest.com>
Date: Mon, 20 Oct 2014 08:37:51 -0500
Message-ID: <CAOk_reHOe6ZvKM-2_UdpXkrovRvevogwxBNCif=Aw7FG0=7UHQ@mail.gmail.com>
To: Chaals from Yandex <chaals@yandex-team.ru>, "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>, "W3C WAI Protocols & Formats" <public-pfwg@w3.org>
We had a way to do this in the original Access element proposal.  In that
case you could also define a 'key' that got you into the local sequence of
focus points.  See
http://www.w3.org/MarkUp/2009/ED-xhtml-access-20090423/#E_access

Could have sworn we made a non-XHTML version of that in the PFWG once upon
a time, but I don't know where it ended up.

On Mon, Oct 20, 2014 at 8:31 AM, Janina Sajka <janina@rednote.net> wrote:

> 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."
>
> PS: If memory serves, DAISY speaks of these as "escapable" structures.
>
> Janina
>
> Charles Nevile writes:
> > 17.10.2014, 20:06, "White, Jason J" <jjwhite@ets.org>:
> > >> -----Original Message-----
> > >> From: chaals@yandex-team.ru [mailto:chaals@yandex-team.ru]
> >
> > >> 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.
> > >
> > > One solution might be a boolean attribute that confines the effect of
> tabindex attributes of descendant elements to that subtree, and ignores all
> values of tabindex occurring outside the subtree.
> >
> > I haven't taken the time to write up a use case in more detail. But at
> Yandex we build a massive amount of web content (hundreds of millions of
> views per day) in something like the way I described.
> >
> > My initial off-the-cuff thinking was some attribute that would scope the
> tabindex, analagous to the "itemscope" attribute in microdata. Which might
> be the same as your idea. But perhaps I need to think harder. In the
> meantime I'll go back to some of the teams who produce these things at
> Yandex - they might have futher ideas.
> >
> > cheers
> >
> > --
> > Charles McCathie Nevile - web standards - CTO Office, Yandex
> > chaals@yandex-team.ru - - - Find more at http://yandex.com
>
> --
>
> Janina Sajka,   Phone:  +1.443.300.2200
>                         sip:janina@asterisk.rednote.net
>                 Email:  janina@rednote.net
>
> Linux Foundation Fellow
> Executive Chair, Accessibility Workgroup:       http://a11y.org
>
> The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI)
> Chair,  Protocols & Formats     http://www.w3.org/wai/pf
>         Indie UI                        http://www.w3.org/WAI/IndieUI/
>
>
>
Received on Monday, 20 October 2014 13:38:30 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:45:10 UTC