- From: Charles Pritchard <chuck@jumis.com>
- Date: Thu, 07 Jul 2011 11:06:30 -0700
- To: Benjamin Hawkes-Lewis <bhawkeslewis@googlemail.com>
- CC: Richard Schwerdtfeger <schwer@us.ibm.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>
On 7/7/2011 8:53 AM, Benjamin Hawkes-Lewis wrote: >> > 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. Rich is referring to LC and other W3C processes having to do with HTML5. SVG a11y issues are not blocking issues for HTML5; Canvas issues are blocking issues. -Charles
Received on Thursday, 7 July 2011 18:07:01 UTC