W3C home > Mailing lists > Public > public-html@w3.org > February 2010

Re: Ease of testing canvas accessible subtree

From: Ian Hickson <ian@hixie.ch>
Date: Fri, 5 Feb 2010 19:35:57 +0000 (UTC)
To: Philip Taylor <pjt47@cam.ac.uk>
Cc: HTML WG <public-html@w3.org>, Henri Sivonen <hsivonen@iki.fi>
Message-ID: <Pine.LNX.4.64.1002051928370.26790@ps20323.dreamhostps.com>
On Fri, 5 Feb 2010, Philip Taylor wrote:
> To develop and test an accessible canvas application with focus 
> management, I'd expect it would be much easier if the author could see 
> the bitmap and the fallback content simultaneously, using their normal 
> mouse and keyboard input to interact with either version, and check that 
> both representations stay in sync and that the focus highlighting is 
> handled correctly. Once they've finished testing, they would want the 
> published version to work like it currently does (i.e. users are shown 
> the bitmap if possible, else the fallback content is shown instead).
> Is this possible with the current spec? If not, I think there should be 
> a way to make the fallback content and bitmap visible together, e.g. 
> <canvas showfallback>...</canvas> (and authors can add some CSS to the 
> fallback content so it's rendered in a sensible position), to help with 
> this kind of testing.

That's a good point. I'm skeptical about allowing elements outside of 
<canvas> be focused while drawFocusRing() renders, because that means the 
screen would have two focus rings... but maybe that's ok?

Ian Hickson               U+1047E                )\._.,--....,'``.    fL
http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'
Received on Friday, 5 February 2010 19:36:28 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 29 October 2015 10:15:58 UTC