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

Re: Proposal: Canvas accessibility and a media querries approach for alternative content (Action Item 6 in the HTML Accessibility Task Force)

From: Ian Hickson <ian@hixie.ch>
Date: Wed, 20 Jan 2010 13:53:31 +0000 (UTC)
To: Steven Faulkner <faulkner.steve@gmail.com>
Cc: Henri Sivonen <hsivonen@iki.fi>, Maciej Stachowiak <mjs@apple.com>, public-canvas-api@w3.org, HTML WG <public-html@w3.org>
Message-ID: <Pine.LNX.4.64.1001201350470.3958@ps20323.dreamhostps.com>
On Wed, 20 Jan 2010, Steven Faulkner wrote:
> in the case where a user clicks on a pseudo text input on the canvas, 
> can a focus rectangle be drawn using the drawfocusring() method?


> would it not make sense for click to cause the associated
> (drawfocusring(element, ) text input in the subdom to gain focus?

Yes, in fact the script would _have_ to do that in order for the focusing 
ring mechanism to work properly. That's why it was designed that way.

> Thus the drawfocusring() method could be used to cut down on unecessary 
> duplication of event handling for all users as they would be handled by 
> the native elements regardless of whether they had a disibility and 
> required the use of the keyboard or not.

Yes, duplication of code is generally bad programming practice.

Ian Hickson               U+1047E                )\._.,--....,'``.    fL
http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'
Received on Wednesday, 20 January 2010 13:54:04 UTC

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