Bug 57066 - AX: Accessibility tree for iframes has inconsistent values set for accessibilityIsIgnored
Summary: AX: Accessibility tree for iframes has inconsistent values set for accessibil...
Status: UNCONFIRMED
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: 2011-03-24 17:01 PDT by Dominic Mazzoni
Modified: 2016-12-15 20:29 PST (History)
4 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Dominic Mazzoni 2011-03-24 17:01:05 PDT
Some AccessibilityObjects have accessibilityIsIgnored()=true, which keeps the tree of AccessibilityObjects shallower and simpler.

When iterating over the children of an AccessibilityObject, you always get only unignored children. To find the original parent of one of those children, you can retrieve the unignored parent.

This rule is useful in Chromium's implementation of accessibility. For example, a table cell is a child of both the row and the column - however, the cell's unignored parent is the row object, so we can use that to avoid processing the same node twice when walking the entire tree.

This rule seems to be broken for iframes. The child of an iframe is a scroll area, but the unignored parent object of the scroll area is an object with role=group that isn't ignored.

It'd be nice to make this more consistent, so that either the unignored parent of the scroll area is the iframe, or the intermediate nodes between the iframe and the scroll area are marked as ignored.
Comment 1 chris fleizach 2011-03-24 17:31:08 PDT
agreed. was not aware this was occurring.
Comment 2 James Craig 2013-11-18 15:38:01 PST
<rdar://problem/15497064>
Comment 3 James Craig 2013-11-19 10:52:38 PST
<rdar://problem/15499513>