[Webkit-unassigned] [Bug 125491] [ATK] Some elements do not show up in the ATK hierarchy

[bugzilla-daemon at webkit.org]

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

--- Comment #4 from Joanmarie Diggs (irc: joanie) <jdiggs at igalia.com> ---
In some of the cases below, I think it's correct that they are not showing up. Example: <img alt="">

In some of the cases below, it depends on the actual contents. For instance, given a proper audio or video element complete with stuff in it (as opposed to the roles-exposed test), the elements do show up properly in the ATK hierarchy. We already have tests for that (which illustrate their showing up).

In some of the cases below, the issue seems to be a combination of how the roles-exposed test works and differing hierarchies between the Mac and ATK. For example, given a meter element:

Mac hierarchy:
-> AXGroup (This is the media element, and the thing with the id attr)
   -> AXProgressIndicator (This is the RenderMeter, has the value stuff)

The ATK hierarchy is just:
-> AXProgressIndicator (This is the RenderMeter, has the value stuff)

So in ATK we are exposing the bit the user cares about. But the fact that the we're not also exposing the element (AXGroup == ATK_ROLE_PANEL) means that the roles-exposed test fails because the way it finds elements is by id.

I'm honestly not sure what to do about the meter-like failures: From an actual accessibility point of view, we're exposing the correct stuff. Should we expose the element/panel just to make the ID-dependent tests pass? Adding extra stuff in the hierarchy consumed by ATs to accommodate our test harness seems like a bad idea. Should we fold all the RenderMeter stuff into the parent element and then expose the parent element instead of the RenderMeter? That seems like a way to accommodate the test harness without impacting the ATs and user experience, but that seems like more work than should be needed. Should we add some sort of hack to the html-id object attribute? That's also a sad solution, but seems like the easiest. BUT, when an element with an id attribute is ignored, it could be that it's exposed through the parent (in the case of text), but it could be that it's exposed through the child (in the case of the meter). So all options seem pretty sucktastic to me. Suggestions?

-- 
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/20141116/f183bc77/attachment-0002.html>