16385 2012-03-15 08:47:58 +0000 Navigating to a fragment identifier should probably move focus to the indicated part of the document 2012-07-18 18:39:18 +0000 1 1 1 Unclassified WHATWG HTML unspecified Other other RESOLVED DUPLICATE 16186 http://www.whatwg.org/specs/web-apps/current-work/#scroll-to-fragid a11y P3 normal Unsorted 1 contributor ian cooper hans.hillen kennyluck mathias mike zcorpan contributor oldest_to_newest 65592 0 contributor 2012-03-15 08:47:58 +0000 Specification: http://www.whatwg.org/specs/web-apps/current-work/multipage/history.html Multipage: http://www.whatwg.org/C#scroll-to-fragid Complete: http://www.whatwg.org/c#scroll-to-fragid Comment: Navigating to a fragment identifier should probably move focus to the indicated part of the document Posted from: 85.227.157.105 by simonp@opera.com User agent: Opera/9.80 (Macintosh; Intel Mac OS X 10.7.2; U; en) Presto/2.10.229 Version/11.61 65593 1 zcorpan 2012-03-15 08:59:50 +0000 Concretely, this results in a better user experience when the user follows the "Skip to search" link in https://developer.mozilla.org/en-US/#q where in IE the text field is focused after following the link so the user can start typing in it, but in Firefox/Opera/Chrome/per spec, focus is not moved, the user still has to manually tab to the search field, rendering the skip link completely useless. 65594 2 zcorpan 2012-03-15 09:06:11 +0000 Also, the spec doesn't seem to say that the "focus caret" (for spatial or sequential focus navigation) should be moved to the indicated part of the document (in case it isn't focusable). Example: The user follows a link in a "table of contents" to section "Foo". The user then presses "tab" to focus the next focusable element. The user expects the next focusable element in the section "Foo" to get focus, not the next link in the "table of contents". 65595 3 zcorpan 2012-03-15 09:15:54 +0000 (Make sure this works also "If the scrolling fails because the relevant ID has not yet been parsed".) 65839 4 cooper 2012-03-20 15:32:01 +0000 Discussed in HTML Accessibility TF bug triage meeting 20 March 2012 http://www.w3.org/2012/03/20-a11y-bugs-minutes.html. This seems to cover the same issue as 16186, which has additional detail. Suggest this be marked as a duplicate of 16186. 65840 5 zcorpan 2012-03-20 15:35:15 +0000 *** This bug has been marked as a duplicate of bug 16186 ***