RE: accessible tree example

I agree with Bryan that context menus can be especially helpful in trees.

 

I’d like to emphasize a point that was more subtle in Bryan’s response. He said what roles you can use for nodes in a tree, which is also saying what you can not use. That is, you can not put other widgets inside of treeitems; tree items are static, per the spec.

 

If you need to arrange a set of arbitrary widgets in a tree structure, one option is treegrid. Gridcells are generic containers, each of which  could hold one of your Q widgets, and you could implement an interaction model very much like what you described. Could is the operative word here … I do not know how good the result would be. We need more consistent implementation of grid support across screen readers before you would likely get a good experience for screen reader users. For keyboard only users, it would be more a matter of how you did the visual styling vs what kind of ARIA you put under the covers.

 

This could be an aspirational pattern that would be worth putting into the ARIA APG … want to build it?

 

Matt

 

From: Bryan Garaventa [mailto:bryan.garaventa@ssbbartgroup.com] 
Sent: Monday, April 4, 2016 2:19 PM
To: Ku, Ja Eun <jku@illinois.edu>; Fred Esch <fesch@us.ibm.com>
Cc: James Nurthen <james.nurthen@oracle.com>; Michiel Bijl <michiel@agosto.nl>; Matt King <a11ythinker@gmail.com>; Gunderson, Jon R <jongund@illinois.edu>; ARIA <public-aria@w3.org>
Subject: RE: accessible tree example

 

Hi Fred,

Yes, the roles currently are role=tree, role=group, and role=treeitem for a tree.

 

For branch and leaf nodes that include complex interactions, the options are currently limited.

 

The use of aria-expanded conveys a branch node, and its absence conveys a leaf node on role=treeitem.

 

The whole shortcuts thread conveys what is being worked on for something like this, which isn’t in the spec yet for conveying specific keyboard shortcuts that are available on one node versus another.

 

You can use aria-describedby on a node so that additional information will be announced when focus is moved to the control, though this will likely not be announced when arrowing between tree item nodes in some screen readers.

 

So at the moment, the only reliable or somewhat reliable method for conveying variable options for variable tree item nodes is to include aria-haspopup=”true” on the tree item node and have a Menu popup up when right clicked or when Shift+F10 or the Applications key is pressed, so that the user can see and arrow to the action that they wish to invoke and click or press Enter on it to initiate the action.

 

This makes it unnecessary to have all possibilities on all nodes announced every time focus is moved from one tree item to another, because they may vary unpredictably.

 

 

 

 

From: Ku, Ja Eun [mailto:jku@illinois.edu] 
Sent: Monday, April 04, 2016 1:52 PM
To: Fred Esch <fesch@us.ibm.com <mailto:fesch@us.ibm.com> >
Cc: James Nurthen <james.nurthen@oracle.com <mailto:james.nurthen@oracle.com> >; Michiel Bijl <michiel@agosto.nl <mailto:michiel@agosto.nl> >; Matt King <a11ythinker@gmail.com <mailto:a11ythinker@gmail.com> >; Gunderson, Jon R <jongund@illinois.edu <mailto:jongund@illinois.edu> >; Bryan Garaventa <bryan.garaventa@ssbbartgroup.com <mailto:bryan.garaventa@ssbbartgroup.com> >
Subject: RE: accessible tree example

 

Unfortunately, I am a novice in the field ‘yet’ to answer your question, Fred. 

I am also ccing Matt, Bryan and Jon here in case they can answer to your question. (You mentioned Brayan and Matt in the last email thinking that they may have any good suggestions) 

 

Jemma

 

From: Fred Esch [mailto:fesch@us.ibm.com] 
Sent: Monday, April 04, 2016 3:29 PM
To: Ku, Ja Eun <jku@illinois.edu <mailto:jku@illinois.edu> >
Cc: James Nurthen <james.nurthen@oracle.com <mailto:james.nurthen@oracle.com> >; Michiel Bijl <michiel@agosto.nl <mailto:michiel@agosto.nl> >
Subject: RE: accessible tree example

 

Jemma,

Thanks for looking into this. I would think widgets embedded in a structure would be a pattern that you would have recommendations on and would follow some general rule about containers. For instance, widget Q does XYZ and contains several controls. When you replicate widget Q, it seems like you would simply have one behavior for moving between the widget Q's controlled by the organization/structure and a behavior for dropping focus into an instance of widget Q and popping out of a widget Q. Whatever organization/structure you used for the widget Q's would control how you move between them, for instance you could have widget Qs in a tree, grid, list or whatever. 

So another way to look at what I was asking is - is there a general rule about containers that should be followed? For instance, can you put a widget Q in a tree. Expect to move through the tree using your normal tree keys? And expect to enter a widget Q using the enter key and leave a widget Q using an escape key? 


Regards, 

Fred Esch 
Watson, IBM, W3C Accessibility




Watson Release Management and Quality 



"Ku, Ja Eun" ---04/04/2016 03:00:20 PM---Hi Fred, I asked about having an interactive dialog tree builder example at today's APG meeting.

From: "Ku, Ja Eun" <jku@illinois.edu <mailto:jku@illinois.edu> >
To: Fred Esch/Arlington/IBM@IBMUS
Cc: James Nurthen <james.nurthen@oracle.com <mailto:james.nurthen@oracle.com> >, Michiel Bijl <michiel@agosto.nl <mailto:michiel@agosto.nl> >
Date: 04/04/2016 03:00 PM
Subject: RE: accessible tree example

  _____  




Hi Fred, 

I asked about having an interactive dialog tree builder example at today’s APG meeting. 
At this time, we would not be able to work on that example and decide to work on two basic tree views first.
I hope you can share with us if you get to have accessible interactive dialog tree builder. 

Best, 

JaEun Jemma Ku, PhD
Internet Applications Systems Specialist
University library
University of Illinois at Urbana-Champaign
424 Library, M/C 522
1408 West Gregory Dr.
Urbana, IL 61801
1-217-244-2145
jku@illinois.edu <mailto:jku@illinois.edu> 



From: Fred Esch [mailto:fesch@us.ibm.com] 
Sent: Thursday, March 24, 2016 2:48 PM
To: Ku, Ja Eun <jku@illinois.edu <mailto:jku@illinois.edu> >
Subject: Re: accessible tree example

Hi Jemma,

I am looking for an up to date example of a tree with complex leaves (leaflets?). I believe there are still 3 roles involved in trees: tree, group and treeitem. I was wondering what the current recommendations are when the leaves (treeitem) are complex and have multiple actions associated with them.

For example, if you were to make an interactive dialog tree builder and each leaf could have actions such as duplicate, move, delete, edit text, edit mood, add alternative or make new leaf. And a leaf would have text, a list of alternatives (that mean the same thing), a mood and information value. What is the recommended structure for the branches (which have the same stuff as leaves + leaves) and leaves? 

Anyhow I saw in the  <https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_w3c_aria_wiki_Aria-2DAuthoring-2DPractices-2DPatterns-2DStatus&d=BQMFAg&c=8hUWFZcy2Z-Za5rBPlktOQ&r=tYy0Yf6x95Anoyy4MyCJ-w&m=HLmxv7KZkMYKtY3sHF2tUvOlic4P-73dAH0myUBbjrs&s=X53VIydjgKxeEGg75JJHfD53PEy_oasnhobg-BbE5_k&e=> Aria Authoring Practices Patterns Status table that tree view appeared to be done. Bryan and Matt can have strong opinions on how things should be structured to maximize usability so I assumed a reviewed pattern would reflect their input and minimize a user's frustration.


Regards, 

Fred Esch 
Watson, IBM, W3C Accessibility




Watson Release Management and Quality 



"Ku, Ja Eun" ---03/24/2016 03:08:12 PM---Hi Fred, I was assigned to make tree example at the last APG meeting before CSUN . However, I did no

From: "Ku, Ja Eun" <jku@illinois.edu <mailto:jku@illinois.edu> >
To: Fred Esch/Arlington/IBM@IBMUS
Date: 03/24/2016 03:08 PM
Subject: Re: accessible tree example

  _____  





Hi Fred,
I was assigned to make tree example at the last APG meeting before CSUN . However, I did not started it yet other than gathering some keyboard requirement for Tree example from James, Michiel, and Matt. 
Do you need it urgently with some reason? 

Jemma

On Mar 24, 2016, at 12:03 PM, Fred Esch < <mailto:fesch@us.ibm.com> fesch@us.ibm.com> wrote:

Hi Jemma,

Can you point me to the accessible tree example? I can't find it in GitHub :(


Regards, 

Fred Esch 
Watson, IBM, W3C Accessibility


<08676269.gif>

Watson Release Management and Quality 


[attachment "08676269.gif" deleted by Fred Esch/Arlington/IBM]