Re: handling focus

Hi Steve,

I was not at the TPAC but it would be up to the author to draw visible
focus on the canvas when the id changes. Would the managing canvas
application, written in script, do the rendering based when the id changes?
The id would change when the keyboard or mouse handler changes the id to
moves focus.

We could define a standard handler that gets triggered by canvas when the
id changes for aria-activedescendant.

Rich

Rich Schwerdtfeger
Distinguished Engineer, SWG Accessibility Architect/Strategist


                                                                           
             Steven Faulkner                                               
             <faulkner.steve@g                                             
             mail.com>                                                  To 
             Sent by:                  public-canvas-api@w3.org            
             public-canvas-api                                          cc 
             -request@w3.org                                               
                                                                   Subject 
                                       handling focus                      
             11/16/2009 07:27                                              
             AM                                                            
                                                                           
                                                                           
                                                                           
                                                                           




Hi all,
at TPAC the provision of a method to draw focus rectangles on a canvas was
discussed, and it appeared that this was considered necessary,
how does this fit in with the use of active-descendent to track focus in a
shadow DOM?

The user scenarios that need to be addressed are:
keyboard only users.
screen magnifier users who use focus highlighting features.
screen magnifier users who rely upon the characteristics of focusable
elements to move focused content into their viewport.

>From the discussions so far in regards to the shadow DOM, it does not sound
as if their will be a relationship between focus on the canvas and elements
in the shadow DOM.
If this is the case then not only will a shadow dom with focus managed via
active descendent have to be created to represent content to the subset of
AT users who do not require the content to be visually rendered , but also
focus management for areas drawn visibly on the canvas, this seems like an
unecessary duplication?


--
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