[Webkit-unassigned] [Bug 278103] New: AX: VO cursor initial position and sequential focus navigation starting point wrong when loading page with URL fragment or text fragment

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=278103

            Bug ID: 278103
           Summary: AX: VO cursor initial position and sequential focus
                    navigation starting point wrong when loading page with
                    URL fragment or text fragment
           Product: WebKit
           Version: Safari Technology Preview
          Hardware: All
                OS: All
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: Accessibility
          Assignee: webkit-unassigned at lists.webkit.org
          Reporter: zcorpan at gmail.com
                CC: andresg_22 at apple.com,
                    webkit-bug-importer at group.apple.com

When loading a page with a URL fragment targeting a non-focusable element, the VO cursor is not set to that position.

When loading a page with a URL text fragment, WebKit doesn't set the sequential focus navigation starting point to the start of the highlight, and the VO cursor is not set to that position.

- URL fragment (non-focusable): https://url-fragments.glitch.me/#interesting
  Expected: Pressing tab should focus the next focusable element after the "interesting" paragraph. VO should start reading from the target paragraph.
  Actual: Pressing tab is as expected, but VO reads from the top.

- URL fragment (focusable): https://url-fragments.glitch.me/#button
  Expected: The button should be focused. VO should start reading from the target button.
  Actual: As expected.

- Text fragment (non-focusable): https://url-fragments.glitch.me/#:~:text=interesting
  Expected: Pressing tab should focus the next focusable element after the "interesting" paragraph. VO should start reading from the target paragraph.
  Actual: Pressing tab focuses the first focusable element. VO reads from the top.

- Text fragment (focusable): https://url-fragments.glitch.me/#:~:text=%23interesting).-,a%20no%2Dop%20button,-(%23button)
  Expected: The button should not be focused, but pressing tab should focus the next focusable element. VO should start reading from the target button.
  Actual: Pressing tab focuses the first focusable element in the document. VO reads from the top.

Spec:
https://html.spec.whatwg.org/#scrolling-to-a-fragment:sequential-focus-navigation-starting-point
https://wicg.github.io/scroll-to-text-fragment/#:~:text=Move%20the%20sequential%20focus%20navigation%20starting%20point%20to%20target.
(No spec AFAIK about moving VO cursor, but seems expected.)

Tests:
https://wpt.fyi/results/scroll-to-text-fragment/sequential-focus.html?label=experimental&label=master&aligned
(No test about VO cursor.)

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20240814/c7262c1c/attachment.htm>