Re: You Got Your SVG in my Canvas! Mmm, Delicious!

Hi, Tab-

Tab Atkins Jr. wrote (on 7/7/11 1:14 PM):
> On Wed, Jul 6, 2011 at 6:58 PM, Richard Schwerdtfeger<schwer@us.ibm.com>  wrote:
>> I agree. and title and description are insufficient for dynamically
>> changing drawings. This is an SVG deficiency but NOT a canvas
>> deficiency.
>
> I don't understand.  Why are they insufficient?  They seem to
> adequately solve one of the presented use-cases (which I've begun
> recording at<http://wiki.whatwg.org/wiki/Active_Image_Accessibility_Use-cases>).
>   Can you elaborate either why they don't solve that use-case well, or
> why that use-case is unimportant to solve?

Thanks for writing those up.  I've linked to them from the wiki page I 
created on the topic:
  http://www.w3.org/WAI/PF/HTML/wiki/Canvas_Accessibility_Use_Cases

They have a different level of granularity, but I think it's useful to 
discuss all the concrete use cases we have.


I agree with Rich that title and description are not always enough 
(though I maintain that they sometimes are); obviously, more information 
is better, such as may be available and readily AT-consumable through 
ARIA attributes.  But ARIA attributes can be used with SVG as well.


>> Although important, the bounds of an object are only a piece of all
>> the things to support interoperability. You need roles,
>> relationships, state change notifications, and so on. We have those
>> in canvas now. We do not in SVG.
>
> What problems are you trying to solve with those things?  The
> use-cases I've been able to extract so far don't appear to need any of
> those.  Do you have more use-cases?

Yes, please share any use cases on either (or both) of the wiki pages, 
so we can have them easily available for discussion.  This will 
ultimately be useful for SVG anyway, regardless of what happens with Canvas.


Regards-
-Doug Schepers
W3C Staff Contact, SVG, WebApps, Web Events, and Audio WGs

Received on Thursday, 7 July 2011 17:53:36 UTC