<mck> chair: matt_king

<scribe> scribe: AnnAbbott

APG 1.2 updates

mck: goal is to get first public working draft by Thursday so ARIA can publish 1.2
... new section for structural roles - blockquote, paragraph and 1 more
... James has new 1.2 branch

Code reviews for APG regression test project

mck: has vendor lined up to test 18 examples - kickoff meeting tomorrow
... call for volunteers to review Bocoup work

aa: are they writing tool or doing manually?

mck: integrating into webdriverIO and developing code for test assertions and configs tests

jg: can help

<jemma> jemma: I can be a back up person

Menubar issues

mck: issue is menuitem need to own/contain menu links but functionality is broken for kbd users
... bg says it isn't a bug
... need change to pattern and spec doesn't support what's in pattern

<jemma> https://github.com/w3c/aria-practices/issues/592

mck: required owned elements in spec, menu not included
... proposes submitting PR to ARIA 1.2 that required owned elements for menu role include menu

jg: required or allowed

mck: required = allowed

<jemma> The only issue I see with this guidance is that menu is not one of the required owned elements for menu. The required owned elements include: group menuitemradio menuitem menuitemcheckbox menuitemradio

<jemma> from Matt's comment

bg: can't nest links in tree either
... menu is composite widget and child elements must be menuitem, menuitemcheckbox and menuitemradion

mck: menu is container and must have at least one menuitem

bg: if defined properly and provide good example, then not a bug

mck: thinking we need to change pattern, but pattern isn't supported by spec
... more difficult problem for tree has no container equivalent like menu

bg: make links owned by group (sibling)

<mck> Perhaps the guidance should be that:

<mck> A submenu, e.g., a menu opened by menuitem, is:

<mck> • Contained inside the same menu as the menuitem that opens it.

<mck> • is the sibling element immediately following the menuitem that opens it.

mck: pattern could say that

bg: sounds good

mck: still need change to spec
... doesn't support nesting in menu

bg: aria-owns on link pointed to group then the nesting is calculated by browsers

mck: best to have spec support same structure
... needs further thought
... aria-controls would fix parent swallowing children
... wait on issue #159 - need different approach
... spec change needed and aria-controls on links and allow menus to own menus as child
... Issue #592 is not a bug - to address, need changes to pattern text (see mck: comment above)

Escape key in editor menubar

mck: issue is behavior matches pattern, but bug says pattern should say more about what Escape key does

Jemma: Escape does not close menu

mck: if focus is in submenu or on parent, Escape should close menu - requires clarification to pattern and code also
... doesn't think can get done right away

jg: changing example code won't be hard

mck: doesn't think code change is needed

Jemma: doesn't think its a bug

jg: thinks it is a bug

siri agrees

aa: agrees

<jemma> http://w3c.github.io/aria-practices/examples/menubar/menubar-1/menubar-1.html

jg; has already made code change and documentation - can make pull request

mck: talking about menubar2
... menubar1 has this and a bunch more issues

Future meetings and other business

no meeting July 2, July 23 and July 30

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)

Present: AnnAbbott BryanGaraventa jemma evan Shirisha Gubba'
Found Scribe: AnnAbbott
Inferring ScribeNick: AnnAbbott
Agenda: https://github.com/w3c/aria-practices/wiki/June-18%2C-2018-Meeting

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.)