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 12290 - The user agent must allow the element to be focused, should allow the element to be reached using sequential focus navigation, and should place the element in the sequential focus navigation order so that it is:
Summary: The user agent must allow the element to be focused, should allow the element...
Status: RESOLVED INVALID
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: 2011-03-11 23:52 UTC by contributor
Modified: 2011-08-04 05:17 UTC (History)
7 users (show)

See Also:


Attachments

Description contributor 2011-03-11 23:52:08 UTC
Specification: http://www.whatwg.org/specs/web-apps/current-work/multipage/editing.html
Section: http://www.whatwg.org/specs/web-apps/current-work/#negative-tabindex

Comment:
The user agent must allow the element to be focused, should allow the element
to be reached using sequential focus navigation, and should place the element
in the sequential focus navigation order so that it is:

Posted from: 76.100.64.113
User agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.15) Gecko/20110303 Firefox/3.6.15
Comment 1 Ian 'Hixie' Hickson 2011-05-06 19:44:03 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: Did Not Understand Request
Change Description: no spec change
Rationale: I don't understand. Could you elaborate?
Comment 2 Martin Kliehm 2011-05-10 15:14:38 UTC
The HTML Accessibility Task Force Bug Triage sub-team does not consider this bug to be TF priority at this time.
Comment 3 Michael[tm] Smith 2011-08-04 05:17:06 UTC
mass-move component to LC1