W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > January to March 2017

RE: treeview questions

From: Bryan Garaventa <bryan.garaventa@ssbbartgroup.com>
Date: Sat, 18 Feb 2017 00:14:06 +0000
To: Rich Morin <rdm@cfcl.com>, WAI Interest Group <w3c-wai-ig@w3.org>
CC: Amanda Lacy <lacy925@gmail.com>
Message-ID: <BN6PR03MB2785CAA682B602893FF10A18985C0@BN6PR03MB2785.namprd03.prod.outlook.com>
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?

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

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.

Bryan Garaventa
Accessibility Fellow
SSB BART Group, Inc.
415.624.2709 (o)

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



- WAI-ARIA Authoring Practices 1.1

- File Directory Treeview Example Using Computed Properties

- File Directory Treeview Example Using Declared Properties

- Navigation Treeview Example Using Computed Properties

- Navigation Treeview Example Using Declared Properties

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 00:14:42 UTC

This archive was generated by hypermail 2.3.1 : Saturday, 18 February 2017 00:14:42 UTC