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 8647 - Define tab order for IFrame
Summary: Define tab order for IFrame
Status: VERIFIED WONTFIX
Alias: None
Product: HTML WG
Classification: Unclassified
Component: pre-LC1 HTML5 spec (editor: Ian Hickson) (show other bugs)
Version: unspecified
Hardware: PC Windows NT
: P2 normal
Target Milestone: ---
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
URL: http://www.w3.org/TR/html5/text-level...
Whiteboard:
Keywords: a11y, a11ytf, a11y_focus
Depends on:
Blocks:
 
Reported: 2010-01-05 11:06 UTC by Gez Lemon
Modified: 2010-10-04 14:30 UTC (History)
5 users (show)

See Also:


Attachments

Description Gez Lemon 2010-01-05 11:06:49 UTC
When iframes are processed in keyboard navigation order, the tab order should tab in document order from outside the iframe, into the first focusable item in the iframe, then when it reaches the last focusable item in the iframe, the next tab should exit the iframe and move to the next item in tab order in the parent document. This is because a lot of uses of iframe are to support security in the web page.
Comment 1 Ian 'Hixie' Hickson 2010-02-05 20:29: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: Rejected
Change Description: no spec change
Rationale: I agree in principle with what is described, but I don't understand why HTML should define this. This seems like a platform convention  if a platform has a different behaviour, it should be conforming for a user agent to do it. It would be stupid, but there's no interoperability reason to disallow it. It would be like the UA insisting on having the window to all Web pages be 100 pixels square. It would be stupid, accessibility would suffer, but there may be times where it's the right thing, and more importantly it's not an interop problem, so it should be allowed.
Comment 2 Michael Cooper 2010-02-11 17:18:11 UTC
The HTML Accessibility Task Force intends to track these issues, per the proposal at http://lists.w3.org/Archives/Public/public-html-a11y/2010Jan/0245.html.
Comment 3 Michael Cooper 2010-08-28 14:48:55 UTC
http://www.w3.org/2002/09/wbs/44061/20100520_bugs/results

Close as far as the HTML bug tracker is concerned. Refer the issue to be addressed in an external user interface recommendations document, initially to be coordinated by the User Agent Accessibility Guidelines Working Group.

http://lists.w3.org/Archives/Public/public-html-a11y/2010Aug/0350.html