<scribe> scribe: AnnAbbott

Menubar pull requests

1) Update on testing of Pull 593 from Carolyn for issue 408.

mck: any regressions?
... Evan - any issue with hover?

Evan: interested in feedback from group

jg: hover shouldn't move focus. Evan agrees.

mck: submenus should not appear on focus
... should change before merging. Evan agrees.
... any other needed changes?

Group: none other noted

jg: another change: under Accessibility features - user should have to take action to have menu open

Evan: call out hover feature - expand on hover vs expand on click

mck: Carolyn to fix so hover doesn't move focus, but will expand on hover if a menu is open
... documenting this isn't Carolyn's ToDo - Matt will create issue and assign to himself

2) Do we still need Pull 589 from Jon for issue 451.

mck: once Carolyn's is integrated, is anything missing from Jon's?

jg: questions whether should apply to menu links should pop up

<siri> can any one give me number to join via phone?

mck: raise as separate issue

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.

To Siri: US toll call-in: +1-617-324-0000 Access code (meeting number): 640 859 469

<siri> Thanks Ann

mck: is there a need for relationship?

bg: there really is no need to have explicit relationship because when has focus, there's no tree type relationship because focus stays in menu.
... no need to have parent/child relationship

<siri> you mean no need to have explicit relationship

mck: seems necessary in touch mode

to Siri: yes! Thanks for catching that

mck: bg not disagreeing with guidance. mck will raise bug re: owns

bg; must be within right structure

Siri: doesn't see any difference using screen reader with aria-controls

mck: browser support for aria-owns, especially in FF

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.

Group: no strong feelings

jg: h1/h2 prefered

mck: if no need, leaning towards no guidance

jg: consistency is important

aa: address consistency

Future meetings and other business

1) No meeting on Feb 19 due to US Holiday

<siri> Iam not getting meeting notice

2) No meeting on March 19 due to CSUN

3) Matt out on Mar 26; should the TF meet? TBD

This is scribe.perl Revision: 1.152  of Date: 2017/02/06 11:04:15  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: Irssi_ISO8601_Log_Text_Format (score 1.00)

Succeeded: s/there really is need/there really is no need/
Present: matt_king AnnAbbott evan jongund Bryan Garaventa
Found Scribe: AnnAbbott
Inferring ScribeNick: AnnAbbott
Agenda: https://github.com/w3c/aria-practices/wiki/February-12%2C-2018-Meeting

WARNING: No meeting chair found!
You should specify the meeting chair like this:
<dbooth> Chair: dbooth


WARNING: No date found!  Assuming today.  (Hint: Specify
the W3C IRC log URL, and the date will be determined from that.)
Or specify the date like this:
<dbooth> Date: 12 Sep 2002

People with action items: 

WARNING: Input appears to use implicit continuation lines.
You may need the "-implicitContinuations" option.


WARNING: IRC log location not specified!  (You can ignore this 
warning if you do not want the generated minutes to contain 
a link to the original IRC log.)