See also: IRC log
<Lisa_Seeman> trackbot, start meeting
<Lisa_Seeman> agenda: this
<Lisa_Seeman> and https://docs.google.com/document/d/1EVnmFO6l8nAdBs5UiasJnZz3Ri_diKcoz8peoPWTm4Q/edit?usp=sharing
<Lisa_Seeman> scribe: JohnRochford
Lisa: Mike meant to do a reword
on accessible authentication
... Mike thinks there is a hell of a lot of work needed on
it.
Jim: Neither I nor Neil are clear on how process works for new wording.
<Lisa_Seeman> ACTION: lisa to find out what the process is for new wording, and for responcence to comments [recorded in http://www.w3.org/2017/03/20-coga-minutes.html#action01]
<trackbot> Created ACTION-205 - Find out what the process is for new wording, and for responcence to comments [on Lisa Seeman-Kestenbaum - due 2017-03-27].
Jim: Where do we update wording that was not in the first public working draft?
<Lisa_Seeman> ACTION: lisa clarify were does new wording for sc in the current working draft [recorded in http://www.w3.org/2017/03/20-coga-minutes.html#action02]
<trackbot> Created ACTION-206 - Clarify were does new wording for sc in the current working draft [on Lisa Seeman-Kestenbaum - due 2017-03-27].
<Lisa_Seeman> ACTION: lisa clarify how we track comments [recorded in http://www.w3.org/2017/03/20-coga-minutes.html#action03]
<trackbot> Created ACTION-207 - Clarify how we track comments [on Lisa Seeman-Kestenbaum - due 2017-03-27].
Lisa: Should we ask the group
about how much technology support they are comfortable
with?
... Does WCAG want us to meet a higher bar than a
technology-specific one?
<Thaddeus> +Present Thaddeus
Lisa: Does anyone have an opinion
onn how we should go with personalization?
... We could have a weekly call for those interested in
personalization. Would anyone be interested in joining on a
regular basis?
Jim, Jan, kirkwood all expressed in joining
expressed interest
Jim_S: I could use a good grounding in personalization.
Lisa: Anyone, not just WCAG or COGA people, could join the personalization discussion(s).
<kirkwood> Yes
Jan: At proposed time for personalization call, I can make it work every other week.
<Lisa_Seeman> ACTION: lisa set time 10 easten on monday [recorded in http://www.w3.org/2017/03/20-coga-minutes.html#action04]
<trackbot> Created ACTION-208 - Set time 10 easten on monday [on Lisa Seeman-Kestenbaum - due 2017-03-27].
Lisa: I'm not sure if I should
open up conversation about putting the burden on authors for
personalization.
... That leaves us with the mess we have with accessible
authentication.
... Mike is suggesting a radical scaling back. He's worried we
can't rely upon the new specification by the W3C.
... I think this needs a call with everyone who is
interested.
Thaddeus: I am in security for a living, so I am interested in accessible authentication.
<Jim_S> I'll ask Neil Milliken about being involved as this is something he is interested in.
Lisa: At the very least, Mike, Thaddeus, John Rochford, and I should be on that call.
Jan: I am interested too.
Lisa: I'm nervous about being stuck on 3 success criteria for so long when we have less than a year.
<Lisa_Seeman> https://rawgit.com/w3c/coga/master/extension/status.html
Lisa: Which do we think is the next urgent SC to address next?
<Lisa_Seeman> https://rawgit.com/w3c/coga/master/extension/status.html
Thaddeus: Will the SC we are working on get into 2.1?
Lisa: Yes.
... Which SC supports voice-menu systems?
Thaddeus: Search might be an important one.
Lisa: What about feedback or task
completion?
... Which would we like to focus on next?
... Let's move forward with task completion and feedback.
... Search does not have a SC manager. We had it tagged as
medium importance.
... The first think we need to do for feedback is get a SC
manager.
... I will reach out to the list to find one.
Lisa: Let's discuss getting out the draft for feedback.
<Lisa_Seeman> https://docs.google.com/document/d/1NBjIZgCRNRXbdC1xtrYu9vMwgEEpGDSLDZ_5IcpN0zw/edit?usp=sharing
Lisa: If anyone has criticism of this, the time to share it is now. There are only 10 days left.
Lisa to Jan: I think we should delete all commments because the are confusing to people.
Jan: okay
they, not the
<Thaddeus> This document is great. Great job!
<Thaddeus> was looking earlier this morning
Lisa to Pietro: Are you able to send that document out?
<Lisa_Seeman> https://docs.google.com/document/d/1EVnmFO6l8nAdBs5UiasJnZz3Ri_diKcoz8peoPWTm4Q/edit?usp=sharing
<Lisa_Seeman> https://docs.google.com/document/d/1NBjIZgCRNRXbdC1xtrYu9vMwgEEpGDSLDZ_5IcpN0zw/edit
Lisa: The document is the summary of WCAG 2.1 for cognitive. Then, we made a draft email at the link I am about to share.
<Lisa_Seeman> craft email is at: https://docs.google.com/document/d/1EVnmFO6l8nAdBs5UiasJnZz3Ri_diKcoz8peoPWTm4Q/edit?usp=sharing
Lisa: Are you ready to send to
European disability agencies?
... and to autism-specific angencies?
Pietro: March is a difficult
month because people are very busy.
... I did send out that email.
Lisa to All: Please send it out to as many people as possible so we can get comments.
John Rochford: I thought Josh had shut down Manageable Blocks.
Michael C: No, that's not what Josh meant.
Lisa: Agreed, because it is in
the first public working draft.
... Do we prefer to do more in parallel, or keep it at 3 at a
time?
Thaddeus: I prefer 3 at a time.
+1 to 3 at a time
<Jim_S> +1 to 3 at a time
<Thaddeus> Thank you
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: JohnRochford Jim_S kirkwood jan Susann_Keohane Pietro Thaddeus Regrets: Steve_Lee Mary_Jo_Mueller Mary_Jo_Mueller EA_Draffan Michael_Pluke Found Scribe: JohnRochford Inferring ScribeNick: JohnRochford WARNING: No meeting chair found! You should specify the meeting chair like this: <dbooth> Chair: dbooth Found Date: 20 Mar 2017 Guessing minutes URL: http://www.w3.org/2017/03/20-coga-minutes.html People with action items: lisa WARNING: Input appears to use implicit continuation lines. You may need the "-implicitContinuations" option.[End of scribe.perl diagnostic output]