This was was cloned from bug 16186 as part of operation convergence.
Originally filed: 2012-03-01 19:58:00 +0000
Original reporter: James Craig <jcraig@apple.com>

================================================================================
 #0   James Craig                                     2012-03-01 19:58:45 +0000 
--------------------------------------------------------------------------------
HTML 5 missing explicit directives for support full keyboard access (FKA) when navigating to a fragment identifier:

Following a hyperlink:
http://www.w3.org/TR/html5/links.html#following-hyperlinks
"When a user follows a hyperlink created by an element, the user agent must resolve the URL given by the href attribute of that element, relative to that element, and if that is successful, must navigate a browsing context to the resulting absolute URL."

Navigate:
http://www.w3.org/TR/html5/history.html#navigate
"Fragment identifiers: If the absolute URL of the new resource is the same as the address of the active document of the browsing contextbeing navigated, ignoring any <fragment> components of those URLs, and the new resource is to be fetched using HTTP GET or equivalent, and the absolute URL of the new resource has a <fragment> component (even if it is empty), then navigate to that fragment identifier and abort these steps."

Navigating to a fragment identifier:
http://www.w3.org/TR/html5/history.html#scroll-to-fragid
"When the user agent is required to scroll to the fragment identifier, it must change the scrolling position of the document using the scroll an element into view algorithm defined in the CSSOM View specification, or perform some other action, such that the indicated part of the document is brought to the user's attention."

The phrase "perform some other action such that…[the anchor]…is brought to the user's attention" is vague, but focusing the anchor is clearly the action that should be performed if full keyboard access (FKA) is enabled.

Filing this defect against HTML 5 Accessibility to get the spec to explicitly state the UA must move focus to that element if focusable, and perhaps something about moving the browsing context focus there even if it's not "focusable" and therefore can't provide a DOM focus event. For example, if the linked anchor is a non-focusable heading, pressing Tab should move to the next focusable item past the heading, even if the heading itself was not the focused document.activeElement.

This should also cover the case were a user just loads a URL with a fragID (like the ones above) without actually clicking the link.
================================================================================
 #1   Ian 'Hixie' Hickson                             2012-03-02 20:29:57 +0000 
--------------------------------------------------------------------------------
Status: Rejected
Change Description: no spec change
Rationale: This is a UI issue, we can't and shouldn't require a particular behaviour. It's up to the UA to do what they think is best for their users.
================================================================================
 #2   James Craig                                     2012-03-02 21:03:06 +0000 
--------------------------------------------------------------------------------
If you really believe that, you should take out the requirement to scroll the view, too. Reopening.
================================================================================
 #3   Michael Cooper                                  2012-03-20 15:22:23 +0000 
--------------------------------------------------------------------------------
Discussed in HTML Accessibility TF bug triage meeting 20 March 2012 http://www.w3.org/2012/03/20-a11y-bugs-minutes.html. We agree with the focus suggestions. We had questions about what truly should be left to the User Agent / User Interface, vs what should spec'd. We see need for UAs to distinguish on UI but setting focus is not a UI thing per se, it's a core accessibility need. How UAs do that specifically can be the UI differentiation. Therefore this is an issue the HTML A11y TF should follow.
================================================================================
 #4   Simon Pieters                                   2012-03-20 15:35:15 +0000 
--------------------------------------------------------------------------------
*** Bug 16385 has been marked as a duplicate of this bug. ***
================================================================================
 #5   Simon Pieters                                   2012-03-20 15:38:09 +0000 
--------------------------------------------------------------------------------
I think this isn't purely UI since focus is exposed to scripts.

(Make sure this works also "If the scrolling fails because the relevant ID has not yet been parsed" if you spec this.)
================================================================================