8647 2010-01-05 11:06:49 +0000 Define tab order for IFrame 2010-10-04 14:30:20 +0000 1 1 1 Unclassified HTML WG pre-LC1 HTML5 spec (editor: Ian Hickson) unspecified PC Windows NT VERIFIED WONTFIX http://www.w3.org/TR/html5/text-level-semantics.html#the-iframe-element a11y, a11ytf, a11y_focus P2 normal --- 1 gez.lemon ian ian mike public-html-a11y public-html-admin public-html-wg-issue-tracking public-html-bugzilla oldest_to_newest 30495 0 gez.lemon 2010-01-05 11:06:49 +0000 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. 31502 1 ian 2010-02-05 20:29:03 +0000 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. 31773 2 cooper 2010-02-11 17:18:11 +0000 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. 38119 3 cooper 2010-08-28 14:48:55 +0000 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