Bug 132355 - AX: WebKit could infer AXDisclosedByRow correctly on this invalidly nested tree example
Summary: AX: WebKit could infer AXDisclosedByRow correctly on this invalidly nested tr...
Status: NEW
Alias: None
Product: WebKit
Classification: Unclassified
Component: Accessibility (show other bugs)
Version: 528+ (Nightly build)
Hardware: All All
: P2 Normal
Assignee: Nobody
URL:
Keywords: InRadar
Depends on:
Blocks:
 
Reported: 2014-04-29 14:30 PDT by James Craig
Modified: 2014-04-29 14:31 PDT (History)
1 user (show)

See Also:


Attachments
test case (2.02 KB, text/html)
2014-04-29 14:30 PDT, James Craig
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description James Craig 2014-04-29 14:30:50 PDT
Created attachment 230420 [details]
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.
Comment 1 Radar WebKit Bug Importer 2014-04-29 14:31:48 PDT
<rdar://problem/16761069>