- From: Ian Hickson <ian@hixie.ch>
- Date: Wed, 17 Mar 2010 22:08:30 +0000 (UTC)
- To: Maciej Stachowiak <mjs@apple.com>
- Cc: HTML Accessibility Task Force <public-html-a11y@w3.org>
On Wed, 17 Mar 2010, Maciej Stachowiak wrote:
> 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.
Given that there has to be script anyway, and that that script is going to
generate the accessible content, and that if the script fails the fallback
is actually what you would want to show to everyone (even the AT users),
and that therefore the attribute should be set by script, what is the
advantage of adding this feature? From an author perspective it seems to
replace "canvas.innerHTML = '';" with "canvas.setAttribute('...', '');",
which isn't even shorter.
--
Ian Hickson U+1047E )\._.,--....,'``. fL
http://ln.hixie.ch/ U+263A /, _.. \ _\ ;`._ ,.
Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
Received on Wednesday, 17 March 2010 22:09:01 UTC