- From: Richard Schwerdtfeger <schwer@us.ibm.com>
- Date: Thu, 19 Nov 2009 10:36:32 -0600
- To: James Craig <jcraig@apple.com>
- Cc: Steven Faulkner <faulkner.steve@gmail.com>, public-canvas-api@w3.org, public-canvas-api-request@w3.org, dbolter@mozilla.com, cyns@exchange.microsoft.com, janina@rednote.net
- Message-ID: <OF44D0F9FC.97243C1E-ON86257673.005A9455-86257673.005B3C79@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 James Craig <jcraig@apple.com > To Sent by: Steven Faulkner public-canvas-api <faulkner.steve@gmail.com> -request@w3.org cc public-canvas-api@w3.org Subject 11/18/2009 08:26 Re: handling focus PM 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
Attachments
- image/gif attachment: graycol.gif
- image/gif attachment: pic18116.gif
- image/gif attachment: ecblank.gif
Received on Thursday, 19 November 2009 16:37:33 UTC