- From: Tab Atkins Jr. <jackalmage@gmail.com>
- Date: Wed, 29 Jun 2011 13:54:48 -0700
- To: Judy Brewer <jbrewer@w3.org>
- Cc: John Foliot <jfoliot@stanford.edu>, Paul Bakaus <pbakaus@zynga.com>, Charles Pritchard <chuck@jumis.com>, Charles McCathieNevile <chaals@opera.com>, Richard Schwerdtfeger <schwer@us.ibm.com>, Cameron McCormack <cam@mcc.id.au>, Cynthia Shelly <cyns@microsoft.com>, david.bolter@gmail.com, Frank Olivier <Frank.Olivier@microsoft.com>, Mike@w3.org, public-canvas-api@w3.org, public-html@w3.org, public-html-a11y@w3.org
On Wed, Jun 29, 2011 at 1:34 PM, Judy Brewer <jbrewer@w3.org> wrote: > For Canvas to be usable as part of HTML5, yes, it will need to support > accessibility. But there may still be additional ways to achieve that. There > are a few additional approaches being explored; hopefully one of those will > bear fruit and you'll see a posting proposing an alternative approach within > the next day or two. Can we please have a listing of the problems that are attempting to be solved by the proposals beforehand? It's impossible to evaluate a proposal without knowing what it's trying to do, and how we'll know when it's succeeded. ~TJ
Received on Wednesday, 29 June 2011 20:55:39 UTC