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

RE: recommended attribute use in hierarchies?

From: Sean Murphy (seanmmur) <seanmmur@cisco.com>
Date: Sun, 5 Feb 2017 23:18:41 +0000
To: Rich Morin <rdm@cfcl.com>, WAI Interest Group <w3c-wai-ig@w3.org>
Message-ID: <118cea6eadc24ea6917dad86e2a2a9da@XCH-RCD-001.cisco.com>

Q: If I'm just generating static headings and lists, what attributes should
   I be including (and why)?

Ans: When using elements for structure then using the standard heading, unordered and ordered lists, etc should be used. As the screen reader will by default understand these elements and permit the screen reader user to navigate between them using builtin shortcut keys. In fact, it is best practise to use standard browser elements where possible.

Q: If the example referenced above uses additional attributes, what is the
   reason for this?

Ans: The example you provided is for a tree view widget. In other words, when the focus is placed on a unordre list element with a ARIA role of Tree. The screen reader is informed this is a node (item) of the tree. The level of the treeview node is provided and if the node is collapsed or not. The example has two levels within the treeview. The UI is using an advance navigation structure. The screen reader user needs to gain more information so they know where they are located within the wigit.

I hope this helps.

Received on Sunday, 5 February 2017 23:19:15 UTC

This archive was generated by hypermail 2.3.1 : Sunday, 5 February 2017 23:19:17 UTC