W3C home > Mailing lists > Public > public-canvas-api@w3.org > October to December 2011

Re: canvas example

From: Charles Pritchard <chuck@jumis.com>
Date: Fri, 23 Dec 2011 20:03:07 -0800
Message-ID: <4EF54EFB.20808@jumis.com>
To: Jonathan Mcdougall <jonathanmcdougall@gmail.com>
CC: public-canvas-api@w3.org
On 12/23/11 6:11 PM, Jonathan Mcdougall wrote:
> That being said, trying to come up with accessibility features for
> <canvas>  does not strike me as being a priority. It is not structured
> information, it is merely a bitmap. SVG is a much better target for
> this.

Jonathan, I figure code is easier to use to explain at this point, now 
that we've got the basics down.

Here I am turning the checkbox into something that will describe that a) 
it's a checkbox, and b) whether it is checked, unchecked or mixed.
https://github.com/Downchuck/canui/commit/36e816198000dc08fde8c2742f7bd3624c9b8935

There are some other tweaks to be had, but that shows the magic pretty well.
It took me 30 minutes to clone, boot up and edit the project to support 
accessible checkbox. There are additional subtleties to add, and when we 
see vendor support of drawFocusRing they'll be easy to do.

https://github.com/Downchuck/canui/commits/

I only altered the first example -- you can go ahead an open inspector 
and see the setAttribute firing on the checkbox element when you toggle 
it on and off.
http://downchuck.github.com/canui/examples/offline.html

That kind of information makes all the difference. There are other WCAG 
issues, but that's the biggest one and it's easy to fix.


-Charles
Received on Saturday, 24 December 2011 04:03:32 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Saturday, 24 December 2011 04:03:34 GMT