[Bug 7011] canvas accessible fallback provison is under specified

http://www.w3.org/Bugs/Public/show_bug.cgi?id=7011


steve faulkner <faulkner.steve@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|NEEDSINFO                   |




--- Comment #6 from steve faulkner <faulkner.steve@gmail.com>  2009-06-26 09:59:18 ---
>I have no idea how to do this; if anyone has any concrete proposals for such an
>API, I would be grateful for any suggestions.

I have reopned the bug, as you not having any idea does not make the problem go
away.

please refer to:

http://lists.w3.org/Archives/Public/www-archive/2009Jun/0119.html

> hi Sam,
> 
> "if it is the case that canvas is not accessible, and that there is
> strong agreement on "We will design all features so as to ensure that
> they are accessible to users with disabilities", then I would simply
> suggest we delay Last Call until this is addressed."
> 
> There is nothing hypothetical about the inaccessibility of canvas
> content and accessible design is a cornertsone of W3C philosophy, so I
> would suggest that unless it is resolved before October, it would
> contribute to a delay.

That's why I chose it as a concrete example. :-)


and

SF: the other question is that with <canvas>.. what do you think is the best
way to get this resolved? If more accessibility stuff doesn't get added to it
could it be removed?

SR: Its possible, but unlikely
... Ian has said that he is committed to accessibility in canvas so he is
motivated also by the upcoming deadline for CR
... People want <canvas> in and accessibility is a hard problem.

http://www.w3.org/2009/06/25-html-wg-minutes.html


-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

Received on Friday, 26 June 2009 09:59:28 UTC