<LisaSeemanKestenbaum> clear agenda
<LisaSeemanKestenbaum> make sample user need - https://docs.google.com/document/d/1NAvyzUb4cG9kp1Ao5o2UJ5Ar4cOfRTyrxBjxYzABUb4/edit?usp=sharing
<LisaSeemanKest> david do you have audio
<LisaSeemanKest> scribe: jennie
<LisaSeemanKest> https://lists.w3.org/Archives/Public/public-cognitive-a11y-tf/2019Apr/0030.html
Lisa: Steve had sent a note to
the list regarding the teams.
... there will be more people added to the groups.
So far there is John K and Rachael
Lisa: It would be good if there
were more people from COGA in each group.
... Is anyone on this call interested in being part of these
teams?
John R: yes, I would be please to lead the effort on accessible authentication
<JohnRochford> Accessible Authentication: https://rawgit.com/w3c/coga/master/extension/accessible-authentication.html
Jennie: what are the tasks required if you lead a subgroup?
Steve: there was a survey that went out.
<JohnRochford> I agree to lead the Accessible Authentication working group.
Steve: Each SC has a subgroup,
with both people from COGA and from the AG
... I'm not sure that the process has been defined yet.
Lisa: yes, it has been defined.
<LisaSeemanKest> https://www.w3.org/WAI/GL/wiki/WCAG_2.2_working_process
Lisa: Create a document, then create wording that the groups thinks will help it go through.
<LisaSeemanKest> https://www.w3.org/WAI/GL/wiki/WCAG_2.2_working_process
Lisa: Some members understand
subject matter, others understand WCAG process.
... Subgroups take the work from the task force, put together a
proposal that is likely to meet the requirements of WCAG.
Steve: yes, that is correct. They need to understand the disciplined nature of what needs to go into it.
Jennie: I am willing to help out.
Rachael: I am willing to work on
all 4, not willing to lead all 4.
... leads will coordinate each one. First task: create a plain
language statement.
... Articulate what the goal is comes first, so this doesn't
get lost during the process.
... getting the first document clean and clear is
important.
... then reviewing comments, seeing comments.
... it needs attention to the github, watching the comments,
and bringing that back to COGA to keep the intent, and address
the wording concerns.
Lisa: there were 5 in the document we proposed - they missed out "Make it easy to find help" and "Help is usable by everyone"
Steve: it may be the table that Michael had - I will check.
<LisaSeemanKest> https://docs.google.com/document/d/174PnVZUaRx7lUnZI8_xl7aeN_6Lztv7aj9C_u7ArPpg/edit#
Lisa: For example: Doing this
makes it pass, and not doing these types of things fails.
... You can look at the language that was suggested to WCAG,
but needs to have the wording that will get it through.
... We also had other patterns that were important, such as
extra symbols.
... I'm not sure if we are at max of what they are willing to
accept
John R: if you look at the WCAG 2.2 working process doc
John R: the link has proposed SC - the first one is accessible authentication.
John R: Now that we see that accessible authentication is one of them, who will be working with me on this?
Steve: it is in the email that I sent.
Lisa: 1. In the email Steve sent, there is just a name change. 2. The people listed there are the correct people.
<LisaSeemanKest> https://lists.w3.org/Archives/Public/public-cognitive-a11y-tf/2019Apr/0030.html
Steve: It appears to be missing one from the table.
Lisa: These groups are
preliminary, based on who was on the phone call.
... David would you be interested in heading one?
David: yes
Lisa: Can you pass on to the chairs: John R will do accessible authentication; Jennie and David would be willing to head one, and help out.
Steve: yes
Lisa: Last time we came out with
lots of different wording, there were objections. Main
objection: technology was not mature enough.
... now that the technology is mature enough, look at the
wording in the github from last time. There is a slew of
alternative wording.
... Reviewing this wording by the minigroup would be
important.
John R: Can you send the link to the discussion you are talking about?
<LisaSeemanKest> https://github.com/w3c/wcag21/labels/COGA
<LisaSeemanKest> https://github.com/w3c/wcag21/issues?utf8=%E2%9C%93&q=label%3ACOGA+
Lisa: for all of them, you will
find them at this link
... Our proposals are earlier on, but you can also see the
comments people made the first time round.
<LisaSeemanKest> https://github.com/w3c/wcag21/issues/23
Lisa: One objection came in
seconds before it timed out, with no time to respond to
it.
... exceptions are a really useful tool to help get things
through.
... Rachael, David, John R, John K, Jennie - does that seem
clear?
+1
David and John R: +1
John R: I think you notifying the chairs is a good thing. Will you notify us when you have done this?
Lisa: Sure. All I can do is suggest, but I will and include you on the email.
Steve: I can do it.
John R: Steve - will you tell the chairs that these are the leads from the COGA task force, or the leads for the SC for everyone?
Steve: the survey is
closed...
... I can say that John R is happy to lead the Accessible
Authentication, and David and Jennie are happy to help and
lead.
Lisa: Please correspond with the task force with any issues. We can help! You are not on your own.
<LisaSeemanKest> https://www.w3.org/WAI/GL/task-forces/coga/wiki/PlanningPage
Lisa: the planning page - this week has making sure all your patterns are done, and looking at the content usable document.
<LisaSeemanKest> https://docs.google.com/document/d/1aJE2C0FzzzXgydEp0MNGSdDDvUTTsANViUVvciFK36k/edit#
Lisa: There is the table with
everyone's patterns
... did you get to Abi's?
David: I can get to that this weekend.
Lisa: Steve and Glenda were
working on one.
... John K - did you see the questions Jennie had in there?
John K: yes I did. I will check it again.
Lisa: you were also down for
doing one of Jamie's - clear instructions. Did you complete
this one?
... if you get stuck for time, let me know, and I can help over
the weekend.
... if not done by Tuesday, Steve and Lisa can help?
John K: Steve - is there a chance to be on a call with you?
Steve: yes.
... I will send you an email.
Lisa: can you do the same thing with Abi?
Steve: did you hear from Jamie?
lisa: Steve could you "don't rely
on users memorization" - can you ask him if those are
done?
... I see he completed the user instructions - I don't know if
it is complete
... maybe this is why John K couldn't find it
Steve: form input inflexibility - this is a new one, I haven't seen anywhere.
Steve: that's a brand new one, isn't it?
Steve: this is the actual "use clear labels and instructions"
Lisa: I will be back online on
Sunday and will try to send him an email to follow up.
... can you send it if I don't?
Steve: yes
<LisaSeemanKest> https://www.w3.org/WAI/GL/task-forces/coga/wiki/PlanningPage
<stevelee> ack
<LisaSeemanKest> https://www.w3.org/2019/04/18-COGA-minutes.html
Jennie: Rachael will be following
up on the open items between Rachael and Jennie tomorrow
... request - please publish something as minutes to help those
track when no meeting occurs
Lisa: yes, we can do that.
<LisaSeemanKest> https://www.w3.org/WAI/GL/task-forces/coga/wiki/PlanningPage
John K's email address: Jkirkwood@schools.nyc.gov
Lisa: trying to ensure all the
patterns are done.
... I added actions two weeks agao, for in the meantime.
... actions for next week: your primary ones.
... other actions - important, but not urgent.
... secondary items - not on the rush list, but things people
are meant to be doing.
... for next week - make sure your patterns are done, which
seems the Tuesday deadline will work.
... I sent an email to the list asking people to look at the
Content Usable Document.
Jennie: what is the process for dealing with typos?
Lisa: either put them into the list, or start a branch in github
Jennie: ok
Lisa: part of the timeline will
be reviewing, then one or two people will review all the
patterns to look for things that need to be reviewed.
... then another person will do another review.
... does anyone want to volunteer for this task?
... I would be happy to do them along with someone else.
... I can do a first round
Rachael: are you asking for
someone to go through the entire document?
... I am willing to do that.
Lisa: great! Do you want to start with the usable doc and I can do the Design Patterns? Then we can switch.
Rachael: Yes.
Lisa: John K is down for the bots
and way finding issue papers, and John R is down for this with
you for one of them.
... for the next publication in 3 months.
... Silver prototypes.
... I did one
Rachael: I did one, then will get to the other one next week.
Lisa: Abi, Jennie and Steve are collecting items that can be collected in the terms document.
Steve: yes, I will do that
<LisaSeemanKest> https://docs.google.com/document/d/1poEoQjuWdAfWM3aOGPCwJRx7EvBsAtQ_99sGyS9Jlgc/edit
Jennie: I can do that too
Lisa: highlight the ones to do
first.
... then in the next version we can have glossary terms.
... any other issues on how to track issues?
... hearing no others...2 items left on the agenda
<LisaSeemanKest> https://docs.google.com/document/d/1NAvyzUb4cG9kp1Ao5o2UJ5Ar4cOfRTyrxBjxYzABUb4/edit?usp=sharing
Lisa: example doc of user
needs
... we were discussing a repository of user needs, mainly for
the gap analysis
... looking at the Design Pattern document, bring the examples
that we already have as a user needs, and cross reference with
relevant personas, and extra resources from other people.
... this is based on the information we have.
... Janina - what do you think of this structure?
Janina: go ahead, I'm fine
Lisa: please take a look, and I
will put it on the agenda for next week.
... think about what you want, what works for us; and we can
make a survey of what people prefer.
... in regards to tracking items. We have the tracker - part of
the IRC.
... the other way we could do it is to add things to the
planning page.
... I think we want to review the actions at the beginning of
the call.
... other comments or discussions?
John K: are all the user needs going into one document?
Lisa: that's the kind of thing we
need to decide on.
... each one could be part of an HTML snippet, but when you
look at it, it should look like one document.
John K: from a findability perspective, one document might be easier.
Lisa: straw poll - do people find it useful to go over the actions in the planning page or whichever tool we use?
<LisaSeemanKest> +1
<stevelee> +1
<johnkirkwood> +1
+1
Lisa: ok, we will start each meeting by going to through the actions.
This is scribe.perl Revision: 1.154 of Date: 2018/09/25 16:35:56 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: janina Jennie JohnRochford LisaSeemanKest MichaelC johnkirkwood Fazio Roy Rachael Regrets: Abi and EA Found Scribe: jennie Inferring ScribeNick: Jennie WARNING: No meeting chair found! You should specify the meeting chair like this: <dbooth> Chair: dbooth Found Date: 25 Apr 2019 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]