[Webkit-unassigned] [Bug 156774] AX: SVG images are not exposed in the AX api

Fri Apr 22 11:29:54 PDT 2016

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

--- Comment #20 from Joanmarie Diggs (irc: joanie) <jdiggs at igalia.com> ---
(In reply to comment #19)
> Thanks for the clarification. I think the problem is that we are ignoring
> the empty group even if it's exposed. Maybe we should fix it in the
> screenreader side.

Either that or the role mapping should be changed.

I just did a quick test case on my Mac:

<html>
<head></head>
<body>
<svg aria-label="hello world">
  <circle cx="50"cy="100" r="30"/>
</svg>
</body>
</html>

When I look at that using the Accessibility Inspector, I get the following hierarchy:

-> AXScrollArea
   -> AXWebArea
      -> AXGroup
         -> AXGroup with AXDescription "hello world"

And it's a similar situation on my platform:

-> SCROLL_PANE
   -> DOCUMENT_WEB
      -> PANEL
         -> PANEL with accessible name "hello world"

So the one thing with accessible information IS there.

That said.... On my platform (and I'm guessing on yours), group-like roles are expected to have stuff in them. :) So a group of nothing is admittedly not great. And if that's the problem you're trying to solve, I don't think the way to solve it is by given it a <fingerquotes>useless</fingerquotes> child. But I'll grant you solving it is probably a good idea. :)

What about mapping exposed SVG root elements which lack accessible children as AXImage on each of our platforms? NOTE: SVG root elements which have accessible children should, I think still be AXGroup (my platform's PANEL). Because if there are children, we'd really have a group.

Would that work? (And does that make sense to everyone?)

-- 
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/20160422/6aa53279/attachment.html>