On Jan 21, 2010, at 11:27 AM, James Craig wrote: > I'm going to defer to Maciej on this question, since this changes the standard focus model. It would not be a major problem for us to have elements in the <canvas> subdom get focus without being rendered. It doesn't work that way today, but I can't see any major technical obstacles. Providing a caret location for non-rendered content may be a little trickier, but is also doable. Regards, Maciej > > > On Jan 7, 2010, at 8:56 AM, Richard Schwerdtfeger wrote: >> 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. >> >> http://www.w3.org/WAI/PF/HTML/track/actions/4 >> >> http://www.w3.org/WAI/PF/HTML/track/actions/5 >> >> Rich >> >> >> Rich Schwerdtfeger >> Distinguished Engineer, SWG Accessibility Architect/Strategist >> >
Received on Thursday, 21 January 2010 23:20:15 UTC