<html>
<head>
<base href="https://bugs.webkit.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - AX: SVG images are not exposed in the AX api"
href="https://bugs.webkit.org/show_bug.cgi?id=156774#c24">Comment # 24</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - AX: SVG images are not exposed in the AX api"
href="https://bugs.webkit.org/show_bug.cgi?id=156774">bug 156774</a>
from <span class="vcard"><a class="email" href="mailto:jcraig@apple.com" title="James Craig <jcraig@apple.com>"> <span class="fn">James Craig</span></a>
</span></b>
<pre>I can confirm that the shapes should not be exposed on their own, but I don't think this bug is complete.
However, going back to the original test cases, this bug (rather the Radar associated with this) was not about SVG shape elements. It was about the containing <svg> element.
In the following test case:
<svg aria-label="foo" height="100" width="100">
<circle cx="50" cy="50" r="40" stroke="black" stroke-width="3" fill="red"></circle>
</svg>
The circle itself should not be exposed, but the author labeled the image, so the image should be exposed. Since there are no accessible contents of the SVG, I'd expose this as a single AXImage with a label "foo".
In the next test case:
<svg height="100" width="100">
<circle cx="50" cy="50" r="40" stroke="black" stroke-width="3" fill="red"></circle>
</svg>
Neither the <svg> or the <circle> is labeled, so you could either expose this as an unlabeled AXImage, or as an ignored element. I think it's safe to leave this one ignored.
Ignore the test cases that tried to use the <label> element to point to SVG. Those don't make any sense.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>