<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#c14">Comment # 14</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:n_wang@apple.com" title="Nan Wang <n_wang@apple.com>"> <span class="fn">Nan Wang</span></a>
</span></b>
<pre>Fred and Joanmarie,
I think both of you are right about the specs, that there's no rules saying we should expose a shape based on the parent's attribute.
However, the reason we are excluding shapes from the spec is that:
"Many SVG elements—although rendered to the screen—do not have an intrinsic semantic meaning. Instead, they represent components of the visual presentation of the document. To simplify the accessible representation of the document, these purely presentational elements would normally be omitted from the accessibility tree, unless the author explicitly provides semantic content."
To my understanding, when author provides some semantic content on the svg root parent, he's intention is to make the entire group accessible, otherwise he should just label the individual children. Maybe to make my scenario more reasonable, I think we can say when the svg parent has a semantic description and there's no other accessible children in it, we should expose the shape.
Let me know what you think. Thanks!</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>