- From: Maciej Stachowiak <mjs@apple.com>
- Date: Wed, 17 Mar 2010 03:43:45 -0700
- To: Silvia Pfeiffer <silviapfeiffer1@gmail.com>
- Cc: Steven Faulkner <faulkner.steve@gmail.com>, Richard Schwerdtfeger <schwer@us.ibm.com>, HTML Accessibility Task Force <public-html-a11y@w3.org>, "Michael(tm) Smith" <mike@w3.org>
On Mar 17, 2010, at 3:39 AM, Silvia Pfeiffer wrote: > This is an excellent document and has indeed answered many of the > questions that I still had. > > If I understand the use for the new attribute now correctly, it is a > replacement for requiring a web author to write javascript to remove > the content inside the <canvas> element in the case that the content > is not accessibility content, but rather only legacy browser fallback > content. That actually makes sense to me, in particular for > convenience purposes. For the record, it makes sense to me too, for much the same reason. - Maciej > > Best Regards, > Silvia. > > On Wed, Mar 17, 2010 at 12:35 PM, Steven Faulkner > <faulkner.steve@gmail.com> wrote: >> change proposal - Provide a method for canvas subtree to be hidden >> from all >> users >> http://www.w3.org/html/wg/wiki/ChangeProposals/canvasaccessibilitynonav >> >> a partial resolution for ISSUE 74 canvas-accessibility >> >> -- >> with regards >> >> Steve Faulkner >> Technical Director - TPG Europe >> Director - Web Accessibility Tools Consortium >> >> www.paciellogroup.com | www.wat-c.org >> Web Accessibility Toolbar - >> http://www.paciellogroup.com/resources/wat-ie-about.html >>
Received on Wednesday, 17 March 2010 10:44:19 UTC