Hi Brian,
It is not terrible but if we do allow role on every element in SVG it will
often be for not as there will be no mapping to platform accessibility
services. We would cover this in the SVG User Agent Implementation Guide
but the web author would likely not look at it.
It is easy to add the aria attributes to all the elements. It would not
take more than 10 minutes to do it and rebuild.
Rich
Rich Schwerdtfeger
From: Brian Birtles <bbirtles@mozilla.com>
To: Richard Schwerdtfeger/Austin/IBM@IBMUS
Cc: Kurosawa Takeshi <taken.spc@gmail.com>, "'www-svg'"
<www-svg@w3.org>
Date: 01/16/2014 06:51 PM
Subject: Re: Outlines for new Implementation guide documents for Core
(previously WAI-ARIA), HTML 5.1, and SVG2
Hi Rich,
Thanks for your prompt response.
(2014/01/17 9:28), Richard Schwerdtfeger wrote:
> Well, for example, it would not apply to <desc>, <radius>,
> <rendering-intent>, etc.
<radius> and <rendering-intent> are not elements. If HTML allows role on
<title> and <meta>, is there an issue with allowing it on <desc> in SVG?
Or have I misunderstood HTML?
I'm just trying to understand what the benefit is of disallowing these
attributes?
> I did not think we agreed to put it on all elements - just not to limit
> it to rendered elements.
That's right, we didn't agree to anything. We decided to wait for your
input.
> I think that definitions.xml is fine. Did you find a problem?
Yes, please see the original discussion.[1][2]
Thanks,
Brian
[1] http://www.w3.org/2014/01/09-svg-minutes.html#item01
[2] http://lists.w3.org/Archives/Public/www-svg/2013May/0000.html
