Re: Update tree view examples for review on Monday APG call

Jon,

I think this is bogus explanation. At line 428 of treeview.js a click event
is created and the script has the <a> element dispatch the event. If you
look at the path array in the event when debugging on line 445, the [0]
member (or source)  is the <a> element.  In other words, the <a> element is
a source for an event. Since the <a> element is a source of an event, the
<a> element should be in the accessibility tree.

If you are suggesting folks should do JavaScript gymnastics to comply with
ARIA, then I think we need to rewrite ARIA so clean HTML and JavaScript is
allowed.
                                                              
     Regards,                                                 
                                                              
    Fred Esch                                                 
 Watson, IBM, W3C                                             
  Accessibility                                               
                                                              
 IBM Watson       Watson Release Management and Quality       
                                                              






From: "Gunderson, Jon R" <jongund@illinois.edu>
To: Fred Esch/Arlington/IBM@IBMUS
Cc: Accessible Rich Internet Applications Working Group
            <public-aria@w3.org>
Date: 06/10/2016 03:13 PM
Subject: Re: Update tree view examples for review on Monday APG call



Fred,

In the following tree view example I see the links as the “action” of the
tree, so you cannot “tab” to the links, and the links do not receive
keyboard “focus” (e.g. There DOM parent does), but the link is  activated
when you press the “space” or “enter” key.

https://rawgit.com/jongund/aria-practices/master/examples/treeview/treeview-2.html


I think this a popular way to make a treeview that has a link action.

In this example the links essentially act “presentational" since they are
only defining what will happen if you activate one of the tree items.

But the links would still come up in a list of links for a screen reader
and would be identified as links in review mode.

Are you suggesting we should add role=none to the links (e.g. A elements)
in the example?

Jon


From: Fred Esch <fesch@us.ibm.com>
Date: Friday, June 10, 2016 at 1:51 PM
To: Jon Gunderson <jongund@illinois.edu>
Cc: Accessible Rich Internet Applications Working Group <public-aria@w3.org
>
Subject: Re: Update tree view examples for review on Monday APG call



Jon,

One thing that has been discussed recently is whether an element with role
treeitem may only have presentational children. And in your example you
have a <li> element with role treeitem and a descendent <a> element with a
href. As far as I can tell, an <a> element with a href is interactive
content. So my interpretation is the <li> element with the role treeitem
does not have only presentational children. What am I not understanding? Is
a <a> element with a href presentational? Or do you not believe that a
element with a role treeitem should not be restricted to only have
presentational children?

                                                     
     Regards,                                        
                                                     
    Fred Esch                                        
 Watson, IBM, W3C                                    
  Accessibility                                      
                                                     
 IBM Watson       Watson Release Management and      
                  Quality                            
                                                     




Inactive hide details for "Gunderson, Jon R" ---06/10/2016 01:41:10
PM---Matt, James and Michiel, Here are the updated tree vie"Gunderson, Jon
R" ---06/10/2016 01:41:10 PM---Matt, James and Michiel, Here are the
updated tree view examples based on the APG discussion this we

From: "Gunderson, Jon R" <jongund@illinois.edu>
To: Matt King <a11ythinker@gmail.com>, James Nurthen <
james.nurthen@oracle.com>, Michiel Bijl <michiel@agosto.nl>
Cc: "'ARIA Working Group'" <public-aria@w3.org>
Date: 06/10/2016 01:41 PM
Subject: Update tree view examples for review on Monday APG call





Matt, James and Michiel,

Here are the updated tree view examples based on the APG discussion this
week, hopefully can discuss changes on Monday’s call.

https://rawgit.com/jongund/aria-practices/master/examples/treeview/treeview-1.html


https://rawgit.com/jongund/aria-practices/master/examples/treeview/treeview-2.html



The changes include:
1. Adding a description of the example after the title
2. Updating the keyboard support to match authoring practices
3. Added section on synchronization of visual and aria states
4. Added aria-level, aria-setsize and aria-posinset information to examples

Still todo:
1. Using character to navigate visible tree items
2. Using ‘*’ to open all descendant leaves of the current treeitem

Jon




[attachment "0A236870.gif" deleted by Fred Esch/Arlington/IBM] [attachment
"graycol.gif" deleted by Fred Esch/Arlington/IBM]