[Webkit-unassigned] [Bug 132355] New: AX: WebKit could infer AXDisclosedByRow correctly on this invalidly nested tree example

[bugzilla-daemon at webkit.org]

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

           Summary: AX: WebKit could infer AXDisclosedByRow correctly on
                    this invalidly nested tree example
           Product: WebKit
           Version: 528+ (Nightly build)
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: Accessibility
        AssignedTo: webkit-unassigned at lists.webkit.org
        ReportedBy: jcraig at apple.com
                CC: webkit-bug-importer at group.apple.com


Created an attachment (id=230420)
 --> (https://bugs.webkit.org/attachment.cgi?id=230420&action=review)
test case

AX: WebKit could infer AXDisclosedByRow correctly on this invalidly nested tree example.

This markup example leaves much to be desired, b/c are a bunch of extraneous groups in the tree.

- non-presentational LIs in-between the tree and the first-level treeitems.
- extraneous non-presentational DIVs in-between the first-level items and second-level items. 
- irrelevant/extraneous @aria-owns relationships pointing to descendant nodes.

That said, WebKit does a pretty good job of cleaning it up for the AX tree. The AXOutlineRows and AXLevels are exposed correctly. I think the only bug I noticed is that AXDisclosedByRow is <nil> on the second-level rows, so VO speaks "0 items enclosed". The ancestor hierarchy is intact, so we may just need WebKit to walk higher up the DOM tree to find the correct disclosing row. WebKit should normalize this scenario if possible.

Hearsay: ~"JAWS+FF works with this example." If so, one or both of those is normalizing the invalid markup.

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.