This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 24105 - FKA: Need contextual scoping for tabindex
Summary: FKA: Need contextual scoping for tabindex
Status: RESOLVED DUPLICATE of bug 23960
Alias: None
Product: WHATWG
Classification: Unclassified
Component: HTML (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: Unsorted
Assignee: Ian 'Hixie' Hickson
QA Contact: contributor
URL:
Whiteboard:
Keywords: a11y, a11ytf
Depends on: 23871
Blocks:
  Show dependency tree / graph
 
Reported: 2013-12-16 05:26 UTC by Silvia Pfeiffer
Modified: 2013-12-16 21:52 UTC (History)
6 users (show)

See Also:

Attachments

Description Silvia Pfeiffer 2013-12-16 05:26:35 UTC 
+++ This bug was initially created as a clone of Bug #23871 +++

There is no contextual scoping for tabindex, so any web app attempting to maintain a non-DOM-ordered tab order has to manage focus for every focusable element in the DOM, when the scoping could behave more like positioning contexts in CSS.

Discussion from bug 23366
Comment 1 James Craig 2013-12-16 19:58:02 UTC 
I noticed that Léonie added the accessibility keywords, so I just wanted to clarify that this not an assistive technology issue, as ATs like screen readers have the ability to navigate non-linearly in a variety of ways.

This bug is about the fact that HTML is generally tedious to navigate with a keyboard, and while it's possible to resolve some of these problems in web applications using techniques like "roaming tabindex" and other "focus management" techniques, it's a non-trivial amount of work. HTML should not require authors to do an exorbitant amount of work to implement a useable keyboard behavior in web applications, regardless if their need is related to accessibility, personal preference, or general usability.
Comment 2 Ian 'Hixie' Hickson 2013-12-16 21:52:35 UTC 

*** This bug has been marked as a duplicate of bug 23960 ***