W3C home > Mailing lists > Public > public-canvas-api@w3.org > July to September 2010

Re: html5 editor responds to Canvas accessibility related bugs

From: Ian Hickson <ian@hixie.ch>
Date: Mon, 27 Sep 2010 08:27:41 +0000 (UTC)
To: Steven Faulkner <faulkner.steve@gmail.com>
cc: "public-canvas-api@w3.org" <public-canvas-api@w3.org>
Message-ID: <Pine.LNX.4.64.1009270820220.3271@ps20323.dreamhostps.com>
On Mon, 27 Sep 2010, Steven Faulkner wrote:
> you wrote:
> "Absolutely, image maps are a terrible solution to making <canvas>
> accessible."
> can you elaborate, sting its terrible , as you have said previously, 
> without providing any explanation, is not helpful.


I encourage you to try writing a usemap-based fallback for a real-world 
interactive canvas. Find a real-world use of <canvas>, and then try to 
make it accessible using an image map. The problems I describe will very 
quickly become quite apparent. (Bonus points if you find a canvas where 
the interaction is dynamic or animated, or where the painting code uses 
transforms, both of which increase the difficulty even further.)

Ian Hickson               U+1047E                )\._.,--....,'``.    fL
http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'
Received on Monday, 27 September 2010 08:28:10 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:31:50 UTC