- From: Steven Faulkner <faulkner.steve@gmail.com>
- Date: Thu, 19 Nov 2009 17:29:38 +0000
- To: Richard Schwerdtfeger <schwer@us.ibm.com>
- Cc: James Craig <jcraig@apple.com>, public-canvas-api@w3.org, dbolter@mozilla.com, cyns@exchange.microsoft.com, janina@rednote.net
- Message-ID: <55687cf80911190929r6e22c63fs55a992375d74e58c@mail.gmail.com>
> can you explain how this will work? I talked to rich off-line and he got it through my thick skull: to provide a focusable area on a canvas it will be possible to use an element in the shadow DOM, setting its dimensions and position (on the canvas) via CSS. the element will be included in the document tab order and when it recieves focus a focus rectangle will be drawn on the canvas. when the element has focus events such as mouse and keyboard events will be passed to it although the user appears to be interacting with an area of the canvas. regards stevef 2009/11/19 Steven Faulkner <faulkner.steve@gmail.com> > Hi rich, > > can you explain how this will work? > > for example i have drawn a control on the canvas which corresponds to an > element in the shadow DOM, what is required is a programmatically exposed > focus rectangle that corresponds to the position and dimensions of the > control drawn on the canvas, how is the shadow dom used to acheive this? how > does CSS help to acheive this? > > regards > stevef > 2009/11/19 Richard Schwerdtfeger <schwer@us.ibm.com> > > So, I spoke to the mozilla team and with some tweaks (as the shadow dom >> is not visible) the absolute positioning information can be reflected in the >> accessibility API. It will require some browser adjustments but we would do >> this anyway for the shadow DOM. So, there is no need for scripting methods >> to set the position other than through standard CSS functionality. >> >> So, when focus is applied to a shadow DOM element a magnifier can zoom to >> location. >> >> Cynthia, >> >> I am cc'ing you as this needs to go into the HTML 5 accessibility mapping >> document when agreed upon. >> >> >> Rich >> >> >> Rich Schwerdtfeger >> Distinguished Engineer, SWG Accessibility Architect/Strategist >> >> [image: Inactive hide details for James Craig ---11/18/2009 08:27:19 >> PM---On Nov 17, 2009, at 2:56 AM, Steven Faulkner wrote:]James Craig >> ---11/18/2009 08:27:19 PM---On Nov 17, 2009, at 2:56 AM, Steven Faulkner >> wrote: >> >> >> *James Craig <jcraig@apple.com>* >> Sent by: public-canvas-api-request@w3.org >> >> 11/18/2009 08:26 PM >> >> >> To >> >> Steven Faulkner <faulkner.steve@gmail.com> >> cc >> >> public-canvas-api@w3.org >> Subject >> >> Re: handling focus >> >> On Nov 17, 2009, at 2:56 AM, Steven Faulkner wrote: >> >> > How do AT such as screen magnifiers provide focus highlighting of >> interactive parts of the canvas if native focus is not provided? >> > How are they able to follow and bring currently focused elements into >> the viewport if there focus is not programmatically exposed provided? >> >> That's can be done with standard CSS positioning on the interactive >> elements in the shadow DOM. I'll update the proof-of-concept to include that >> use case. I can't promise it before the U.S. Thanksgiving holiday though. >> >> Cheers, >> James >> >> >> >> > > > -- > with regards > > Steve Faulkner > Technical Director - TPG Europe > Director - Web Accessibility Tools Consortium > > www.paciellogroup.com | www.wat-c.org > Web Accessibility Toolbar - > http://www.paciellogroup.com/resources/wat-ie-about.html > -- with regards Steve Faulkner Technical Director - TPG Europe Director - Web Accessibility Tools Consortium www.paciellogroup.com | www.wat-c.org Web Accessibility Toolbar - http://www.paciellogroup.com/resources/wat-ie-about.html
Attachments
- image/gif attachment: graycol.gif
- image/gif attachment: ecblank.gif
Received on Thursday, 19 November 2009 17:30:19 UTC