Bug 185264 - FKA: activating a fragment ID URL (in-page link or external link with hash) should transfer focus and caret to the fragment target element with ID or name matching the fragment identifier
Summary: FKA: activating a fragment ID URL (in-page link or external link with hash) s...
Status: NEW
Alias: None
Product: WebKit
Classification: Unclassified
Component: Accessibility (show other bugs)
Version: WebKit Nightly Build
Hardware: All All
: P2 Normal
Assignee: Nobody
URL: https://bugs.webkit.org/attachment.cg...
Keywords: InRadar
: 163719 (view as bug list)
Depends on:
Blocks:
 
Reported: 2018-05-03 14:00 PDT by James Craig
Modified: 2019-04-01 14:22 PDT (History)
6 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description James Craig 2018-05-03 14:00:45 PDT
The patches for bug 17450 and bug 116046 either did not fix all the problems or regressed some time later. Refiling again here.

FKA: activating a fragment ID URL (in-page link or external link with hash) should transfer focus and caret to the fragment target element with ID or name matching the fragment identifier

This needs to work for full keyboard access (FKA) as well as VoiceOver, and should work with in-page links (href="#foo") as well as on page load of external links with hash fragments (href="./bar.html#baz"). The patch for bug 17450 only fixed the problem for one use case: VoiceOver users using VO navigation only, not Tab navigation. 

This should bring WebKit in-line with the expected behavior in both Gecko and Trident.

~30 test cases in: https://bugs.webkit.org/attachment.cgi?id=254944
Comment 1 Radar WebKit Bug Importer 2018-05-03 14:01:19 PDT
<rdar://problem/39953581>
Comment 2 James Craig 2018-05-16 02:32:36 PDT
*** Bug 163719 has been marked as a duplicate of this bug. ***
Comment 3 Thomas Logan 2019-04-01 14:22:12 PDT
Any updates on this issue? It currently affects the accessibility of the paging navigation of our website's blog.