Bug 185264
| Summary: | 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 | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | James Craig <jcraig> |
| Component: | Accessibility | Assignee: | Nobody <webkit-unassigned> |
| Status: | NEW | ||
| Severity: | Normal | CC: | jdiggs, mtchllvn, phiw2, redux, thomas, webkit-bug-importer |
| Priority: | P2 | Keywords: | InRadar |
| Version: | WebKit Nightly Build | ||
| Hardware: | All | ||
| OS: | All | ||
| URL: | https://bugs.webkit.org/attachment.cgi?id=254944 | ||
James Craig
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
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Radar WebKit Bug Importer
<rdar://problem/39953581>
James Craig
*** Bug 163719 has been marked as a duplicate of this bug. ***
Thomas Logan
Any updates on this issue? It currently affects the accessibility of the paging navigation of our website's blog.