<scribe> scribe: AnnAbbott
First draft of APG 1.2 ready for review
<mck> https://github.com/w3c/aria-practices/issues/564
https://rawgit.com/w3c/aria-practices/apg-1.2/aria-practices.html
mck: issue #564
... moving to second working draft of 1.2
jn: agrees
mck: adding task to make milestone publication ready
mck: wants to address issues we
can - scope changes to be as narrow as possible
... Issue #451 and #595
jg: will handle
mck: asks jg to backout css changes
jg: PR 716
mck: Props to Evan!
... integrated into master
<mck> Alert dialog in master: https://github.com/w3c/aria-practices/issues/564
oops - wrong link
<mck> Alert dialog in master try 2: http://w3c.github.io/aria-practices/examples/dialog-modal/alertdialog.html
mck: separate commit backed out
sections and no visible header for Related links area
... email from Siri re: issues on mobile - please put in
github
... Compare what was published in Dec with master branch
Siri: will do and will put in github
mck: if problems are in Dec
published - need new issue
... else go in existing issue
... Evan will research color of text in Issue #738
... Issue #736 for reviews by Siri, James and Ann of Alert
dialog
<mck> Example of treegird, current draft: https://rawgit.com/w3c/aria-practices/treegrid/examples/treegrid/treegrid-1.html
mck; "same example can be used in 3 ways" changes how example works (focus and kbd)
mck: likes beauty of maintaining only one page
jg: which is right way or are all right way?
mck: all right way
jg: why would I choose any?
... if all right way, need text explaining why choose one over
another
mck: maybe should have one that makes most sense, save others to be demo'd with different content
jn: thinks that it is ok
now
... already gives use cases
mck: rationale isn't based on screen reader usage
aa: thinks giving rationale based
on screen reader usage is good idea
... if we don't tell them, designers and devs will not know
screen reader usage
mck: will add text - no opposition
jg: documentation needs to be reviewed and kbd documentation to make sure it makes sense for all 3
mck: decision: keep 3 examples (modes of operation), publish and get feedback
<mck> Current open bugs: https://github.com/w3c/aria-practices/issues?utf8=%E2%9C%93&q=is%3Aissue+sort%3Aupdated-desc+milestone%3A%221.1+APG+Release+2%22+label%3Abug+label%3A%22code+example%22+is%3Aopen+
mck: Issue #559 - bug in Dec publish, jg made fix and made PR, mck can't find bug in master
jn: in master, seeing problem with Chrome on MAC
jg: wasn't clearing text in text box with ESC
jn: needs to be merged
mck: Issue #568 needs verbiage
re: styling
... moving Issue #408 to next milestone
no meetings on 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 jamesn cbellew spectranaut evan matt_king jongund siri Found Scribe: AnnAbbott Inferring ScribeNick: AnnAbbott 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]