[Webkit-unassigned] [Bug 166704] New: AX: DOM elements are considered before aria-flowto but not after

[bugzilla-daemon at webkit.org]

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

            Bug ID: 166704
           Summary: AX: DOM elements are considered before aria-flowto but
                    not after
    Classification: Unclassified
           Product: WebKit
           Version: Safari 10
          Hardware: iPhone / iPad
                OS: iOS 10
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: Accessibility
          Assignee: webkit-unassigned at lists.webkit.org
          Reporter: jonathan at tumult.com
                CC: webkit-bug-importer at group.apple.com

It seems odd that the DOM ordering is considered for VO until an element with aria-flowto is hit, but then it is possible to not be hit afterwards depending on the chain.

Take this for example:

<div id="item1" role="img">  Item 1 (role=img)</div>
<div id="item2" role="button" aria-flowto="item4">  Item 2 (role=button, flowto=item4)</div>
<div id="item3" role="img">  Item 3 (role=img)</div>
<div id="item4" role="img"   aria-flowto="item3">  Item 4 (role=img, flowto=item3)</div>
<div id="item5" role="radio">  Item 6 (role=radio)</div>

item1 is selected first despite no aria-flowto indicating it is in a chain of visibility.
Then item4 and item3 are visited, and it simply repeats between item4 and item3; there's no way to get to item5 at this point.

It seems like either aria-flowto should be the only source of navigation (ignoring DOM elements without it), or it should construct a flow that can let DOM elements after the flow be visited.

I am reproducing on iPad Pro with iOS 10.2.1 via:
1. Enabling VoiceOver
2. Swiping to the right

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.webkit.org/pipermail/webkit-unassigned/attachments/20170105/3fd12bea/attachment.html>