W3C home > Mailing lists > Public > public-aria@w3.org > February 2017

RE: treeview questions

From: Bryan Garaventa <bryan.garaventa@ssbbartgroup.com>
Date: Sat, 18 Feb 2017 05:44:01 +0000
To: Matt King <a11ythinker@gmail.com>, 'ARIA Working Group' <public-aria@w3.org>
Message-ID: <BN6PR03MB2785EE0744D090A6FEE45187985C0@BN6PR03MB2785.namprd03.prod.outlook.com>
Thanks,
I'll pass this along.

How often is the draft content pulled into the primary site?



Bryan Garaventa
Accessibility Fellow
SSB BART Group, Inc.
bryan.garaventa@ssbbartgroup.com
415.624.2709 (o)
www.SSBBartGroup.com

-----Original Message-----
From: Matt King [mailto:a11ythinker@gmail.com] 
Sent: Friday, February 17, 2017 6:12 PM
To: Bryan Garaventa <bryan.garaventa@ssbbartgroup.com>; 'ARIA Working Group' <public-aria@w3.org>
Subject: RE: treeview questions

Bryan,

Review of tree view examples is open, so please provide your feedback in the treeview issue. Even after we have completed the review process for an example, it is best to provide example feedback in a github issue.

Note that several updates have been made to the treeview examples since we published on December 14. It appears to me that the problems in IE 11 have all been resolved. I tested with NVDA in FF, Chrome, and IE 11. The only issue I saw is some extra verbosity in IE 11 when NVDA incorrectly reads every item in a group after the focus moves inside the group.

When responding to people inquiring about issues like the one Rich raised, it is very helpful to test against master and then point people to the editor's draft on github if the issue has been resolved.

Matt

-----Original Message-----
From: Bryan Garaventa [mailto:bryan.garaventa@ssbbartgroup.com]
Sent: Friday, February 17, 2017 4:27 PM
To: ARIA Working Group <public-aria@w3.org>
Subject: FW: treeview questions

Hi,
As an FYI, it looks like most of the ARIA Tree examples linked to from the APG 1.1 page are broken in IE11.

I understand not wanting to support outdated browsers, however there is a difference between using standards compliant markup and using cross-browser scripting, which we must make sure we always use regardless what the markup is. Otherwise it makes it look like the APG widgets are not reliable.


Bryan Garaventa
Accessibility Fellow
SSB BART Group, Inc.
bryan.garaventa@ssbbartgroup.com
415.624.2709 (o)
www.SSBBartGroup.com


-----Original Message-----
From: Bryan Garaventa [mailto:bryan.garaventa@ssbbartgroup.com]
Sent: Friday, February 17, 2017 4:14 PM
To: Rich Morin <rdm@cfcl.com>; WAI Interest Group <w3c-wai-ig@w3.org>
Cc: Amanda Lacy <lacy925@gmail.com>
Subject: RE: treeview questions

Hello,
ARIA Tree constructs have been well supported for years going back to ARIA
1.0 when properly constructed. I don't believe we have had a chance to complete the guidance in the APG 1.1 Tree widget as yet however.

Can you please test the following implementation instead?
http://whatsock.com/tsg/Coding%20Arena/ARIA%20Trees/Tree%20(External%20XML)/
demo.htm 

Just verified using JAWS 12 through 18 in IE11, Firefox, and Chrome Canary, plus NVDA in Firefox. (Works best in FF due to better accessibility tree and integrated screen reader support within these browser/AT combinations.)

To see how this works, you can download the code for this, powered by jQuery, within the accessible widget archive at https://github.com/accdc/tsg


You can also use Visual ARIA to examine the ARIA roles and supporting attributes that are being used and compare these with the one you have referenced earlier to see how they differ.
http://whatsock.com/training/matrices/visual-aria.htm 



Bryan Garaventa
Accessibility Fellow
SSB BART Group, Inc.
bryan.garaventa@ssbbartgroup.com
415.624.2709 (o)
www.SSBBartGroup.com

-----Original Message-----
From: Rich Morin [mailto:rdm@cfcl.com]
Sent: Friday, February 17, 2017 2:31 PM
To: WAI Interest Group <w3c-wai-ig@w3.org>
Cc: Amanda Lacy <lacy925@gmail.com>
Subject: treeview questions

I'm interested in finding a highly accessible treeview implementation to adopt for my code.  So, I was quite interested to find that the "WAI-ARIA Authoring Practices 1.1" has several examples I could try out and borrow from.

However, the examples worked very poorly for Amanda Lacy, when she tried using them with NVDA.  The entries I could see on the screen didn't appear for her and the suggested keyboard interactions didn't work.  Could someone give this a try and let us know if we're simply missing something?

More generally, I gather that declared properties may work better than computed properties with some software, though they clearly increase the size of the HTML payload.  In my case, compatibility is a much bigger issue than payload size, so I've been planning to use declared properties.  Are there other considerations I should take into account?

-r

Links:

- WAI-ARIA Authoring Practices 1.1
  https://www.w3.org/TR/wai-aria-practices-1.1/#TreeView

- File Directory Treeview Example Using Computed Properties
 
https://www.w3.org/TR/wai-aria-practices-1.1/examples/treeview/treeview-1/tr
eeview-1a.html

- File Directory Treeview Example Using Declared Properties
 
https://www.w3.org/TR/wai-aria-practices-1.1/examples/treeview/treeview-1/tr
eeview-1b.html

- Navigation Treeview Example Using Computed Properties
 
https://www.w3.org/TR/wai-aria-practices-1.1/examples/treeview/treeview-2/tr
eeview-2a.html

- Navigation Treeview Example Using Declared Properties
 
https://www.w3.org/TR/wai-aria-practices-1.1/examples/treeview/treeview-2/tr
eeview-2b.html

 -- 
http://www.cfcl.com/rdm           Rich Morin           rdm@cfcl.com
http://www.cfcl.com/rdm/resume    San Bruno, CA, USA   +1 650-873-7841

Software system design, development, and documentation
Received on Saturday, 18 February 2017 05:44:39 UTC

This archive was generated by hypermail 2.3.1 : Saturday, 18 February 2017 05:44:40 UTC