W3C home > Mailing lists > Public > public-html-a11y@w3.org > September 2011

[Bug 13181] Canvas does not allow mouse events to be directed to keyboard accessible objects in fallback content

From: <bugzilla@jessica.w3.org>
Date: Mon, 26 Sep 2011 21:34:33 +0000
To: public-html-a11y@w3.org
Message-Id: <E1R8Ior-0002G8-KB@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=13181

--- Comment #6 from Rich Schwerdtfeger <schwer@us.ibm.com> 2011-09-26 21:34:33 UTC ---
Ian, the only way to add a mouse handler in canvas is to bind it to the canvas
element. However, keyboard events do go to the actual fallback content itself
as representations of objects that are drawn on canvas. At this stage I can't:

place three buttons in fallback content, and  
place them in the keyboard navigation order, and 
produce three corresponding drawing objects on canvas, and
place a on click handler on the individual buttons in fallback content and
receive the events when a click occurs on those buttons renderings on canvas
directy. 

Rather I would have to place the onclick handler on the canvas element and
perform the hit testing to dispatch the onclick to the fallback content
elements. That is why the bug is filed.

You don't have to write an example to prove it. 

Sam, if you feel it is necessary to escalate this please let me know. As far as
I can tell this has not been closed or reopened. It is marked new.

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Received on Monday, 26 September 2011 21:34:35 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 27 April 2012 04:42:44 GMT