Nesting Site Navigators (other than trees) and aria-controls (Comment 415)

Document: WAI-ARIA 1.0 Authoring Practices Working Draft 7 March 2013
Part: Site Navigator - General (widget) (Site_Navigator_General)

"If the navigator is for a hierarchical site or application, the hierarchy may be represented in one of two ways: by using a tree for the container widget or by using a separate widget for each level of the hierarchy."

"aria-controls should be set with a value that refers to the content region that is controlled by the navigator. If multiple navigators are used to provide navigation of a hierarchy, navigation widgets that change the elements of a child navigator should have aria-controls set with a value that refers to the controlled child navigation widget."

I assume "change the elements of a child navigator" also means displaying of child navigators (for instance submenus ("If multiple menubars are used to support a hierarchy, then menubars that control another menubar should have aria-controls set with a value that refers to the controlled menubar."))

1. Not the widget, but the item changes a child. (?) - for instance a menuitem controls the visibility of a submenu.

2. aria-controls of the parent navigator would hold a list of ids of all child navigators, which does not seam very informative.

3. why not set aria-controls of the navigator to the content area and aria-controls of the navigation item to the child navigator (and possibly also the content area - not sure if this is necessary - see comment 416)?

Received on Tuesday, 9 April 2013 22:12:31 UTC