W3C home > Mailing lists > Public > public-canvas-api@w3.org > July to September 2011

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

From: Richard Schwerdtfeger <schwer@us.ibm.com>
Date: Thu, 7 Jul 2011 11:51:24 -0500
To: Benjamin Hawkes-Lewis <bhawkeslewis@googlemail.com>
Cc: Charles Pritchard <chuck@jumis.com>, "Tab Atkins Jr." <jackalmage@gmail.com>, "public-canvas-api@w3.org" <public-canvas-api@w3.org>, public-canvas-api-request@w3.org, Doug Schepers <schepers@w3.org>
Message-ID: <OFC99D534D.E186CF0B-ON862578C6.005C2AFB-862578C6.005C985E@us.ibm.com>

SVG does not have this provision. HTML does.

SVG is not part of the HTML spec.

Right now I am working on ARIA and HTML 5. I do not have cycles to solve
SVG accessibility. This discussion is on the HTML list. Currently, the
canvas element is in HTML 5 and the HTML accessibility task force is
working on HTML 5. We are not working on SVG.

I am trying to keep focused on these problems.

If you would like to work on SVG be my guest, but that is not what the HTML
accessibility task force is set to do now.  If you can show me an SVG
element in HTML 5 then great. I don't see it.

Please understand that I am not stating that SVG accessibility is not
important but diverging the discussion to another spec. is keeping people
from focusing on the task at hand.

Rich

Rich Schwerdtfeger
CTO Accessibility Software Group



From:	Benjamin Hawkes-Lewis <bhawkeslewis@googlemail.com>
To:	Richard Schwerdtfeger/Austin/IBM@IBMUS
Cc:	Charles Pritchard <chuck@jumis.com>, "Tab Atkins Jr."
            <jackalmage@gmail.com>, "public-canvas-api@w3.org"
            <public-canvas-api@w3.org>, public-canvas-api-request@w3.org,
            Doug Schepers <schepers@w3.org>
Date:	07/07/2011 10:58 AM
Subject:	Re: You Got Your SVG in my Canvas! Mmm, Delicious!
Sent by:	public-canvas-api-request@w3.org



On Thu, Jul 7, 2011 at 2:58 AM, 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.
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 roles, relationships, state change notifications are available in
HTML content that uses canvas that are not available in HTML content
that use SVG?

> Let's stick to the problem at hand. ... canvas. Eventually we will get to
SVG but not today. Canvas is part of HTML and it needs to be fixed.

SVG is just as much a part of HTML as the canvas context, so I'm
confused by the implication that it's okay for us to fix any
accessibility problems with using canvas with HTML before we fix any
accessibility problems with using SVG with HTML.

--
Benjamin Hawkes-Lewis


graycol.gif
(image/gif attachment: graycol.gif)

Received on Thursday, 7 July 2011 16:52:01 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:10:32 UTC