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 16385 - Navigating to a fragment identifier should probably move focus to the indicated part of the document
Summary: Navigating to a fragment identifier should probably move focus to the indicat...
Status: RESOLVED DUPLICATE of bug 16186
Alias: None
Product: WHATWG
Classification: Unclassified
Component: HTML (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: Unsorted
Assignee: Ian 'Hixie' Hickson
QA Contact: contributor
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard:
Keywords: a11y
Depends on:
Blocks:
 
Reported: 2012-03-15 08:47 UTC by contributor
Modified: 2012-07-18 18:39 UTC (History)
6 users (show)

See Also:


Attachments

Description contributor 2012-03-15 08:47:58 UTC
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
Comment 1 Simon Pieters 2012-03-15 08:59:50 UTC
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.
Comment 2 Simon Pieters 2012-03-15 09:06:11 UTC
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".
Comment 3 Simon Pieters 2012-03-15 09:15:54 UTC
(Make sure this works also "If the scrolling fails because the relevant ID has not yet been parsed".)
Comment 4 Michael Cooper 2012-03-20 15:32:01 UTC
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.
Comment 5 Simon Pieters 2012-03-20 15:35:15 UTC

*** This bug has been marked as a duplicate of bug 16186 ***