- From: James Craig <jcraig@apple.com>
- Date: Mon, 03 Feb 2014 11:23:39 -0800
- To: Richard Schwerdtfeger <schwer@us.ibm.com>
- Cc: Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no>, Steve Faulkner <faulkner.steve@gmail.com>, Joanmarie Diggs <jdiggs@igalia.com>, Cynthia Shelly <cyns@microsoft.com>, Bryan Garaventa <bryan.garaventa@whatsock.com>, "T.V Raman" <raman@google.com>, "jongund@illinois.edu" <jongund@illinois.edu>, "jason@jasonjgw.net" <jason@jasonjgw.net>, "wai-xtech@w3.org" <wai-xtech@w3.org>, "w3c-wai-pf@w3.org WAI-PFWG" <w3c-wai-pf@w3.org>
On Feb 2, 2014, at 8:22 AM, Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no> wrote: > The claim, at that page, is that the <img> defaults to img role. > However, it actually is given group role [in Safari on OS X]. On Feb 2, 2014, at 12:01 PM, Richard Schwerdtfeger <schwer@us.ibm.com> wrote: > While I understand what Apple has implemented (defaults to a group role) we have not decided on a normative mapping for SVG across browsers. Leif and Rich, your assumptions are incorrect about how these roles are treated and what is mapped. I think you’re conflating the platform role mapping with the ARIA mapping. The computed ARIA role for <img> is “img” regardless if it is an SVG or raster image. The internal WebKit mapping for <img> is “ImageRole”, again regardless of the type. However, the is output differently to different platforms. In the case of accessible SVG images on OS X, the image has a rendered subtree, and the current version of AXImage (the AX API mapping) does not support descendant contents, so it’s mapped, on that platform, to AXGroup (a platform-specific role that is not the same as the ARIA “group” role). The content is rendered and the subtree is not hidden, so it should be accessible to all. James
Received on Monday, 3 February 2014 19:24:08 UTC