WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Thoughts towards an accessible <canvas>


From: Joshue O Connor
Date: Mar 22, 2009 4:15AM

Maciej Stachowiak wrote:
> On Mar 19, 2009, at 8:34 AM, Charles McCathieNevile wrote:
>>> I propose that
>>> any instance of <canvas> that lacks at a minimum the 2 proposed
>>> mandatory
>>> values be non-conformant and not render on screen. The inclusion of this
>>> information should not be left to chance - the specification requires
>>> that some fallback content exist - and if it does not exist then the
>>> <canvas> element is incomplete, thus it should simply fail all users...
>> I think that this is a non-starter. As explained in a narrower
>> follow-up, the penalty to browsers who do this means that mainstream
>> browsers simply won't, in all probability.
> I agree with Chaals on this. We would likely not be willing to stop
> rendering existing <canvas> content in Safari.

Yes, all the more reason to ensure that the API is suitable /before/ it
leaves the stable so we are not facing a situation where we need to
retrofit the API for accessibility.



NOTICE: The information contained in this email and any attachments
is confidential and may be privileged. If you are not the intended
recipient you should not use, disclose, distribute or copy any of
the content of it or of any attachment; you are requested to notify
the sender immediately of your receipt of the email and then to
delete it and any attachments from your system.

NCBI endeavours to ensure that emails and any attachments generated
by its staff are free from viruses or other contaminants. However,
it cannot accept any responsibility for any such which are
transmitted. We therefore recommend you scan all attachments.

Please note that the statements and views expressed in this email
and any attachments are those of the author and do not necessarily
represent the views of NCBI