[Webkit-unassigned] [Bug 174099] New: AX: VoiceOver does not follow browser focus on container elements

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Mon Jul 3 09:45:45 PDT 2017


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

            Bug ID: 174099
           Summary: AX: VoiceOver does not follow browser focus on
                    container elements
           Product: WebKit
           Version: Safari 10
          Hardware: iPhone / iPad
                OS: iOS 10.3
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: Accessibility
          Assignee: webkit-unassigned at lists.webkit.org
          Reporter: alexlande at gmail.com
                CC: webkit-bug-importer at group.apple.com

Created attachment 314491

  --> https://bugs.webkit.org/attachment.cgi?id=314491&action=review

HTML file to demonstrate issue

On iOS, VoiceOver does not follow browser focus when using JS to focus on an element that:

- Is not in the default tab order
- Uses tabindex='-1' to allow focus to be set via JS
- Has multiple child elements

In these cases, although the browser focus moves, the VoiceOver cursor stays in place. If you reduce the number of child elements to one, VoiceOver follows focus as expected.

I've attached an HTML file to reproduce the bug, it's also available on JSBin: http://output.jsbin.com/wemuhex


Steps to Reproduce:

1. Open the attached page on an iOS device running iOS 10 and open VoiceOver.
2. Select the button labelled "Focus" and activate it.


Actual Results:

The VoiceOver cursor does not move to the div containing two p tags, although browser focus does.


Expected Results:

The VoiceOver cursor should move to the div containing two p tags and VoiceOver should begin reading the contents of that div.


Additional Information:

To see the expected behavior, you can remove the second p tag from the demo, or test the demo using VoiceOver + Safari for macOS, which handles the situation in the expected way.

-- 
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/20170703/20d0e4a7/attachment.html>


More information about the webkit-unassigned mailing list