Skip to content

February 12, 2018 Meeting

Jump to bottom
Matt King edited this page Feb 13, 2018 · 3 revisions

Agenda for February 12, 2018

Menubar pull requests

  1. Update on testing of Pull 593 from Carolyn for issue 408.
  2. Do we still need Pull 589 from Jon for issue 451.

Ownership of submenu elements

issue 592 - In nested menu example, the element with role="menu" should be owned by the parent with role="menuitem" points out that the FAQ submenu in the navigation menubar example is a sibling of its parent menuitem. Thus, it does not follow the guidance in the pattern that says that submenus are contained or owned by the parent menuitem.

The guidance in the pattern is not required by the spec. The only language about submenus in the spec's menuitem role description is:

If the menu item has its aria-haspopup attribute set to true, it indicates that the menu item may be used to launch a sub-level menu, and authors SHOULD display a new sub-level menu when the menu item is activated.

  • This menuitem language is distinctly different from the treeitem role, which explicitly states that parent treeitems contain their branches.
  • There is nothing in the aria-haspopup description that indicates that the submenu needs to be owned or contained by the parent element.
  • Basically, the spec does not require a relationship between a menuitem and the submenu it controls.
  • A spec requirement is not a prerequisite for best practice, but it is common for related elements.

Should we:

  1. Soften the guidance
  2. Remove the guidance
  3. Change the spec

Heading level for dialog title

Issue 551 - Modal Dialog Example: Heading level could be H1 suggests using H1 for dialog titles. The examples are using H2.

Matt's response:

Because they are a child window, I have usually recommended a level lower than 1. The lack of a level 1 could actually help some people understand they are not on the main page.

But, I don't think there is any hard and fast rule here. It is one of those subjective calls where there is rationale that could probably justify either approach or a variety of others as well.

Let's see what others have to say. If consensus develops around another approach, we could potentially provide some guidance on this in a future release.

We have had not any input on this issue. Discuss best course of action.

Future meetings and other business

  1. No meeting on Feb 19 due to US Holiday
  2. No meeting on March 19 due to CSUN
  3. Matt out on Mar 26; should the TF meet?

Meeting Resources

Clone this wiki locally