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 11533 - clarify if specially focusable elements mean "all elements with defined valid tabindex" or "elements with a tabindex that allows sequential focusing."
Summary: clarify if specially focusable elements mean "all elements with defined valid...
Status: RESOLVED WONTFIX
Alias: None
Product: HTML WG
Classification: Unclassified
Component: LC1 HTML5 spec (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: ---
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard:
Keywords: a11y
Depends on:
Blocks:
 
Reported: 2010-12-11 10:24 UTC by contributor
Modified: 2011-08-04 05:02 UTC (History)
8 users (show)

See Also:

Attachments

Description contributor 2010-12-11 10:24:34 UTC 
Specification: http://www.whatwg.org/specs/web-apps/current-work/multipage/editing.html
Section: http://www.whatwg.org/specs/web-apps/current-work/#sequential-focus-navigation-and-the-tabindex-attribute

Comment:
clarify if specially focusable elements mean "all elements with defined valid
tabindex" or "elements with a tabindex that allows sequential focusing."

Posted from: 203.218.234.217
Comment 1 henry.fai.hang.chan 2010-12-11 10:34:10 UTC 
Statement: "An element is specially focusable if the tabindex attribute's definition above defines the element to be **focusable**."

Should that be sequentially focusable?

or else that makes all elements to be specially focusable, because "non-focusable" elements have a tabIndex default of -1, and elements with a tabindex of -1 are required to be focusable.
Comment 2 Martin Kliehm 2011-01-10 16:54:36 UTC 
The bug-triage sub-team of the W3C HTML Accessibility Task Force doesn't think this bug is TF priority. It could affect accessibility, but it's rather a proofreading issue: comment #1 pointed put that the definition of "specially focusable" is imprecise and should be amended by the word "sequentially". We agree.
Comment 3 Ian 'Hixie' Hickson 2011-02-08 02:11:49 UTC 
EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document:
   http://dev.w3.org/html5/decision-policy/decision-policy.html

Status: Rejected
Change Description: no spec change
Rationale: No, it shouldn't be sequentially focusable. An element without a tabindex="" attribute (e.g. <div>) isn't specially focusable, for example. Don't confuse .tabIndex with tabindex="".
Comment 4 Michael[tm] Smith 2011-08-04 05:02:23 UTC 
mass-moved component to LC1