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

RE: Canvas shadow DOM question for interactive HTML5 elements

From: Frank Olivier <franko@microsoft.com>
Date: Thu, 7 Jan 2010 17:16:15 +0000
To: Richard Schwerdtfeger <schwer@us.ibm.com>, David Bolter <dbolter@mozilla.com>, "jcraig@apple.com" <jcraig@apple.com>
CC: public-canvas-api <public-canvas-api@w3.org>
Message-ID: <DBB7A800D05F0C44A5EBA0231C567C392065CB10@TK5EX14MBXW651.wingroup.windeploy.ntdev.microsoft.com>
Invisible input controls should be able to work without any issue in Windows/Internet Explorer; I will double-check the details (for controls and contenteditable areas) with my team ASAP and report back to the group.


From: Richard Schwerdtfeger [mailto:schwer@us.ibm.com]
Sent: Thursday, January 07, 2010 8:56 AM
To: David Bolter; jcraig@apple.com; Frank Olivier
Cc: public-canvas-api
Subject: Canvas shadow DOM question for interactive HTML5 elements

Hi David, James, Frank,

The canvas working group has reached consensus that we should provide a shadow DOM for <canvas> where the canvas UI is bond to accessible objects in the shadow DOM. Two things we need to agree on is being able to use standard input controls and contenteditable areas in the shadow DOM as will already be accessible in the browser. Since these interactive components are not visible and would be in the keyboard navigation sequence we need to know if this will be a problem for Firefox, Safari, or IE. Also, contenteditable provides a caret location, without which we would need to provide an API for the caret location to support magifiers and screen readers. We need to address these action items in the next 2 weeks.




Rich Schwerdtfeger
Distinguished Engineer, SWG Accessibility Architect/Strategist
Received on Thursday, 7 January 2010 17:16:57 UTC

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