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

Old thread: the a11y reasons for additional methods in Canvas 2d

From: Charles Pritchard <chuck@jumis.com>
Date: Sat, 10 Sep 2011 12:22:47 -0700
Message-ID: <4E6BB907.4060807@jumis.com>
To: public-canvas-api@w3.org
 From an a11y vendor, AISquared:

"We do need the screen location of all content with or without focus"

This has been misunderstood as a "retained-mode" request for the Canvas API.

I hope to see some movement over the next few months, in solving this issue.
As I've pointed out, many times, Apple's VoiceOver on Mobile Safari also 
from this defect in the handling of the Canvas sub-tree.

Using transparent CSS / SVG elements atop the canvas is very 
inefficient, very
costly for authors to implement, and really quite a hackish nightmare.

It's also the only thing we have, for now. Once we can get past that 
work-around, I feel
confident that many Canvas authors will add the additional APIs 
necessary to make their
apps more accessible.

Received on Friday, 9 September 2011 19:20:48 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:10:32 UTC