Re: 48 hour Call For Consensus regarding Resolutions from the May 19, 2016 ARIA Working Group meeting

I agree. I sent out what was resolved at the meeting and had the same thoughts but I was not on the call and was going to raise the same exception. We will have the same issues we have with options and lists.

+1 to keeping the proposal minus treeitem. 

Rich



Rich Schwerdtfeger




> On May 24, 2016, at 10:53 AM, Bryan Garaventa <bryan.garaventa@ssbbartgroup.com> wrote:
> 
> Currently role=treeitem is not a composite widget, and as such nothing rendered within these containers is accessible. So not including role=treeitem in this list will not solve this problem.
>  
>  
> Bryan Garaventa
> Accessibility Fellow
> SSB BART Group, Inc.
> bryan.garaventa@ssbbartgroup.com <mailto:bryan.garaventa@ssbbartgroup.com>
> 415.624.2709 (o)
> www.SSBBartGroup.com <http://www.ssbbartgroup.com/>
>  
> From: Fred Esch [mailto:fesch@us.ibm.com <mailto:fesch@us.ibm.com>] 
> Sent: Tuesday, May 24, 2016 4:21 AM
> To: Rich Schwerdtfeger <richschwer@gmail.com <mailto:richschwer@gmail.com>>
> Cc: ARIA Working Group <public-aria-admin@w3.org <mailto:public-aria-admin@w3.org>>
> Subject: Re: 48 hour Call For Consensus regarding Resolutions from the May 19, 2016 ARIA Working Group meeting
>  
> Rich,
> 
> I would like to see treeitem dropped from the list. No one wants to use treegrid and we see UIs with trees of complex widgets which should naturally use tree style navigation between the them. If we include treeitem in the list then you would not be able to call something a tree, that looks like a tree and you want it to navigate like a tree, if the leaves were complex controls that a user could choose to leave visible. Again, no one will ever call a tree of complex widgets a treegrid when where there is no concept of rows in the layout.
> 
> Suggested solutions for a tree that are compatible with treeitem only having presentational children are work arounds such as having the widget appear in a dialog when you click the treeitem. These 'solutions' are not be practical when you have flows, card layouts, or block chains that have branching. We are seeing lots of card layouts, block chains and relationships expressed in web apps that would be negatively impacted by this restriction.
> 
> Regards, 
> 
> Fred Esch 
> Watson, IBM, W3C Accessibility
> <image001.png>
> Watson Release Management and Quality
> 
> 
> <image002.gif>Rich Schwerdtfeger ---05/23/2016 04:06:45 PM---This is a Call for Consensus (CfC) to the Accessible Rich Internet Applications (ARIA) Working Group
> 
> From: Rich Schwerdtfeger <richschwer@gmail.com <mailto:richschwer@gmail.com>>
> To: ARIA Working Group <public-aria-admin@w3.org <mailto:public-aria-admin@w3.org>>
> Date: 05/23/2016 04:06 PM
> Subject: 48 hour Call For Consensus regarding Resolutions from the May 19, 2016 ARIA Working Group meeting
> 
> 
> 
> 
> This is a Call for Consensus (CfC) to the Accessible Rich Internet Applications (ARIA) Working Group regarding the following resolutions of the ARIA Working group. 
> 
> 1. Add children presentational true to checkbox, menuitem, menuitemcheckbox, menuitemradio, option, radio, spinbutton, switch, tab, and treeitem in response to Issue 1006  
> The meeting minutes are here: https://www.w3.org/2016/05/19-aria-minutes.html <https://www.w3.org/2016/05/19-aria-minutes.html>
> 
> If you object to this proposal, or have comments concerning it, please respond by replying on list to this message no later than 23:49 (midnight) Boston Time,  Wednesday, May 25, 2016.
> 
> Regards,
> 
> Rich
> 
> — 
> Rich Schwerdtfeger,   Email: richschwer@gmail.com <mailto:richschwer@gmail.com>  
> CTO Accessibility IBM Software: http://www.ibm.com.able <http://www.ibm.com.able/> 
> 
> The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI)
> Chair, Accessible Rich Internet Applications https://www.w3.org/WAI/ARIA <https://www.w3.org/WAI/ARIA> 
> 
> Rich Schwerdtfeger
> 
> 
> 
> 
> 
> 
>