<scribe> scribe: AnnAbbott
<jongund> Thank you Ann
1) Matt is working on documenting 2018 priorities and plans.
2) Using wiki to summarize and do high-level mapping.
3) Using milestones to schedule issues by release.
4) This is work in progress.
<mck> https://github.com/w3c/aria-practices/wiki/Scope
5) Cleaned up and added deliverables section to top of scope page.
mck: intention is to make scope available to all
6) Added release planning page.
<mck> https://github.com/w3c/aria-practices/wiki/Release-Plans
mck: next release scheduled end of June
jn; thinks this is a Firefox/Chrome bug that he reported a long time ago
7) Added APG 1.1 Release 2 Plan.
https://github.com/w3c/aria-practices/wiki/APG-1.1-Release-2-Plan
mck: APG 1.2 will release when ARIA 1.2 releases
<jamesn> https://bugzilla.mozilla.org/show_bug.cgi?id=1005271
<mck> https://github.com/w3c/aria-practices/wiki/APG-1.1-Release-2-Plan
<jamesn> is the display:block bug I logged
jg: thinks carousel is almost done
mck: doesn't want to take
time/effort away from high priority issues
... lots more coming if can get contract resources onboard
<mck> https://github.com/w3c/aria-practices/issues/587
jn: if mouse user can't close, why should kbd-only user be able to?
mck: no compelling need to differ from desktop
jn: should we drop space entirely?
mck: space just activates option, doesn't close menu
<mck> https://github.com/w3c/aria-practices/issues/576
based on WCAG 2.1 SC 2.5.2: https://www.w3.org/TR/WCAG21/#pointer-cancellation
Jemma agrees with James, who will draft response
<mck> https://github.com/w3c/aria-practices/issues/578
mck: think of ARIA like CSS, you
cannot predict or prohibit necessary purpose
... if role="region" with aria-expanded=false, clicking on it
will expand. Should be allowed or prohibited?
jg: doesn't think should be allowed
email from Evan and Ann: doesn't think should be allowed
<evan> https://developer.mozilla.org/en-US/docs/Web/HTML/Attributes
mck: aria-expanded should only be applied to widget roles
1) Reminder: on Feb 5, we will take up discussion of outline vs boarder for custom focus.
2) No meeting on Feb 19 due to US Holiday
3) No meeting on March 19 due to CSUN
4) Matt out on Mar 26; should the TF meet?
Mar 26 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) Present: jongund evan JaEunJemmaKu AnnAbbott jamesn matt_king Bryan Garaventa Found Scribe: AnnAbbott Inferring ScribeNick: AnnAbbott Agenda: https://github.com/w3c/aria-practices/wiki/January-29%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.)[End of scribe.perl diagnostic output]