W3C home > Mailing lists > Public > public-pfwg-comments@w3.org > January to March 2013

PFWG Public Comment

From: Mandana Eibegger <mandana@schoener.at>
Date: Sat, 09 Mar 2013 00:54:03 +0100
Message-ID: <513A7A1B.2070205@schoener.at>
To: public-pfwg-comments@w3.org
Hello,

i am writing an email instead of submitting the comment form, because 
resetting my password didn't seam to work.

I have some comments concerning the WAI-ARIA design patterns on
http://www.w3.org/TR/2013/WD-wai-aria-practices-20130307/
for
* Site Navigator - Tree
* Site Navigator - Tabbed Style for Menu

All my comments refer to HTML implementations.

############################################
Site Navigator - Tree
http://www.w3.org/TR/2013/WD-wai-aria-practices-20130307/#Site_Navigator_Tree

- aria-controls:
"The element with role tree should have aria-controls set with a value 
that refers to the content region controlled by the navigator. 
Typically, this is the element with role main."
This works perfectly, if you use AJAX or some other means of displaying 
content dynamically within a single page. But what does aria-controls 
refer to, if i have a menu with "normal" links, eg open a new page on click?

- Keyboard Interaction: "Focus: When the tree receives focus, the item 
in the tree that is marked as currently displayed should receive focus."
This works, if the tree receives focus the first time, because i can 
ensure that the node representing the currently displayed page is 
visible. But after interaction with the tree, the visibility of the node 
is not guaranteed.
I see three possibilities to solve this:
a) focus the current node if it is visible, and if not, focus the first 
top level node.
b) have "The last visited node in the tree control is retained in the 
tab order when the user navigates away from the tree control." (as for 
the "normal" tree view)
c) nodes from a top level node to the current node can not be closed

-------------------------------------------------------------------
Tree View
http://www.w3.org/TR/2013/WD-wai-aria-practices-20130307/#TreeView

- Keyboard Interaction: "Typing a letter key moves focus to the next 
instance of a visible node whose title begins with that letter. "
   - Does "letter key" only refer to a-z? Or also non-standard letters 
as , etc? If a title begins with for instance  (or ), would the next 
letter be used for the hotkey or rather the letter 'a'?
   - What if there are no letters in the title - for instance if the 
menu-items consist of year dates?

- Description: General behavior for tree views: "On first load of the 
tree component, the top level node is in the tab order."
Maybe it should rather say "first top level node" (than "top level node")

############################################
Site Navigator - Tabbed Style - Menu (Option 3)
http://www.w3.org/TR/2013/WD-wai-aria-practices-20130307/#Site_Navigator_Tabbed_Style

- Keyboard Interaction: "Focus: When the menubar receives focus, the 
menuitemradio element in the menubar that is marked as currently 
displayed should receive focus."
There is also the possibility, that no menuitemradio is currently 
displayed. So i think it should say something like
"When the menubar receives focus and there is a menuitemradio element in 
the menubar that is marked as currently displayed, it should receive 
focus. Otherwise the first menuitemradio should receive focus"

- How would i implement a drop-down menu? This would be implemented as 
nested menus (nested Tabbed Style Site Navigators) - the top level would 
be a menubar, but (if i understand the design patterns of menus and role 
definitions correctly) the submenus would have to have role "menu"? But 
tabbed style navigation is only defined for menubar.

- WAI-ARIA Roles, States, and Properties: "The menuitemradio element for 
the page or content that is currently displayed should be indicated by 
setting aria-checked true".
What happens if i have a menubar with the main sections of my site and 
some subpage (not present in the menubar) is displayed? How would i 
mark, that the current page is from a certain section? Would 
aria-selected be appropriate in this case?
For instance if i have a menubar (drop down menu) with 1st and 2nd level 
navigation; once the user is in one of the main sections, the 2nd, 3rd 
etc level navigation is available through a submenu (tree) and the 
submenu of the menuitem in the menubar is not presented anymore. 
Shouldn't there be a way to formally present the path to the current 
page (connection of the main menu to the submenu) through the elements 
in the navigation regions?

- If i understand it correctly, if i build a "normal" menu, i can nest 
menus (or menubars) and pressing "enter" opens submenus.
If i need "enter" to open a page, i have to implement it as nested 
tabbed style widgets and one structural difference is that in need to 
enclose the submenus in containers with role "navigation". What for?

-------------------------------------------------------------------
Menu
http://www.w3.org/TR/2013/WD-wai-aria-practices-20130307/#menu

Keyboard Interaction:
"If a menu bar item has focus and the menu is not open, then:
     * Enter, Space, and the up down arrow keys opens the menu and 
places focus on the first menu item in the opened menu or child menu bar
     * Left or right arrow keys move focus to the adjacent menu bar item. "
- I am wondering about the the "up down arrow keys opens the menu and 
places focus on the first menu item". Would it not be logical to say 
"down places focus in the first, and up on the last item"?
- Maybe add
     * "Right arrow on the last item moves focus to the first item"
     * "Left arrow on the first item moves focus to the last item"
At least this is the way it is programmed in windows applications.


Best regards,
Mandana Eibegger
Received on Saturday, 9 March 2013 21:42:39 GMT

This archive was generated by hypermail 2.3.1 : Saturday, 9 March 2013 21:42:39 GMT