- From: Steven Faulkner <faulkner.steve@gmail.com>
- Date: Tue, 17 Nov 2009 10:56:27 +0000
- To: James Craig <jcraig@apple.com>
- Cc: public-canvas-api@w3.org
- Message-ID: <55687cf80911170256m6fd351e2kc859cda61d359d62@mail.gmail.com>
Hi James, >In the shadow DOM proof of concept I developed, I just drew the focus ring with the canvas. I don't see any need to have a native focus ring drawn on top of >the canvas. I'd say, leave a custom view like canvas for the author to manage. 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? I consider a solution that does not satisfy the following section 508 criteria [1] as inadequate and have yet to see any proposal that satisfies this: § 1194.21 Software applications and operating systems. (c) A well-defined on-screen indication of the current focus shall be provided that moves among interactive interface elements as the input focus changes. The focus shall be programmatically exposed so that assistive technology can track focus and focus changes. [1] http://www.section508.gov/index.cfm?FuseAction=Content&ID=12#Software regards Stevef 2009/11/16 James Craig <jcraig@apple.com> > On Nov 16, 2009, at 5:27 AM, Steven Faulkner wrote: > > > at TPAC the provision of a method to draw focus rectangles on a canvas > was discussed, and it appeared that this was considered necessary, > > In the shadow DOM proof of concept I developed, I just drew the focus ring > with the canvas. I don't see any need to have a native focus ring drawn on > top of the canvas. I'd say, leave a custom view like canvas for the author > to manage. > > > how does this fit in with the use of active-descendent to track focus in > a shadow DOM? > > Only using 'active-descendant' would allow for a shadow DOM as deep as one > managed focus widget. This is fine, but a standard focus model inside the > shadow DOM is necessary, too. Otherwise you'd need to render a separate > canvas element for every complex widget, so something as complex as Bespin > could never be achieved by using a single active descendant. > > > -- 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
Received on Tuesday, 17 November 2009 10:57:08 UTC