<stevelee> john, roy are you joining us? on webex
<alastairc> scribe: alastairc
stevelee: Quick update from the
F2F. WCAG working on 2.2, we've picked on 3 of our design
patterns to put forward. In order to make that work, we'll be
looking for some people to shepard it through.
... just a heads up at the moment.
John: With that, and building on what you did, not sure I understand was come up with during the design patterns.
Working process doc: https://www.w3.org/WAI/GL/wiki/WCAG_2.2_working_process
<JohnRochford> +1 to Alastair's description of the process to get COGA SC approved
proposed SC (last item) https://docs.google.com/spreadsheets/d/11IKqjRFvkRd2dAfUiyc5whhB3yIYXvSiirWct7KQIB0/edit?usp=sharing
stevelee: I couldn't find some of
the patterns, we didn't seem to have addressed some
items.
... is anyone able to pick up some of these items?
Jennie: I think my name got taken
off the list, perhaps there have been some changes between
meetings?
... there was one I was supposed to work on, but waiting to
find out if it had merged.
... Use a consistent visual design was what you and EA were
working on, just looking it up.
... the one that had issues 26 & 39. I'll send you the info
tomorrow.
stevelee: I thought these were
missing - making each step clear.
... also one that has a long name, with headings, visual
heirarchies and whitespace.
... provide feedback was another.
Rachael: I could pick up 'undo'.
Jennie: Saw from twitter Jamie hasn't been back home for a while, so worth just asking.
stevelee: Could you do 'make each
step clear'? (Rachael)
... I'll chase Jamie.
<stevelee> https://docs.google.com/document/d/1GvlmwHCsWobTgXx9LTWmbRBM6jT8s5lZcardq8u_Ge4/edit#
Jennie: Showing the review for
the design guide, and Lisa and I went through it together, went
through each step. Also, checking links.
... e.g. the first link to the template didn't go where we
thought. The google doc adds an extra H2, so you might have to
scroll down a few lines to review the template.
... Lisa helped me understand this, the multiple layers.
... 1st thing - don't get into the details, just check
everything is present.
... 2 - review the github issues. There are times you might
find something in github hasn't been accounted for in the table
for the design guide.
... 3 - is it clear what you need to do? I.e. what are we
asking people to do.
... that all needs doing before the 4th step.
... 4 - plain english review. BUT, as we might re-work it,
leave this until the end.
... I wasn't sure when to make the change in the doc or when to
ask people to change it.
... we discussed doing minor stuff in the doc, e.g. typos,
spelling. However, if it could change the meaning, need to go
back to the person who wrote it.
JohnRochford: just a reminder, I'll tackle the plain language at the end of the process.
Jennie: Yep, just wanted to make sure it was concrete first.
JohnRochford: I'm listed for objective 2, not sure what it is about?
stevelee: Looks like you were down to look at sub-menus?
JohnRochford: No.
Stevelee: Looks like you were down for review?
JohnRochford: Looks like JohnK will be doing those things.
stevelee: probably just have the wrong letter!
JohnRochford: Looks like there are more?
<Glenda> Yep.
<scribe> scribe:Glenda
stevelee: what about other sources of information for the pattern. are we just supposed to look at the github issues? I thought there were more sources.
jennie: yes. see item 2 in “reviewing design guide pattern” https://docs.google.com/document/d/1GvlmwHCsWobTgXx9LTWmbRBM6jT8s5lZcardq8u_Ge4/edit#heading=h.um7nz5ganbi3
stevelee: we may need to remove links to these things later.
jennie: helpful to have historical references at the bottom
Rachael: can we add more status on the review column. There is an intermediate state of “I’ve reviewed, but now I’m waiting on the group for feedback.”
stevelee: adding “questions” as a status for review
<JohnRochford> +1 to understanding Jennie's explanation
stevelee: checking on progress
for reviews. let’s set some dates for reviews to be
finished.
... suggests a week from now as a due date.
jennie: Lisa had originally said March 23rd as a review target date
<Jennie> Deadlines for reviewing +1
jennie: do we have a calendar location of the deadlines for tasks (for individuals or a group)?
stevelee: there is a planning page on the wiki, but I don’t think it has detailed target dates
<stevelee> https://www.w3.org/WAI/GL/task-forces/coga/wiki/PlanningPage
jennie: is there another way that the AG is managing tasks/timelines
stevelee: MichaelC is there a way of tasks/timeline?
MichaelC: there is no formal calendar or way of tracking used by all the groups
Jennie: I’ve been making my own notes and keeping reminders in my calendar. It would be helpful to have a way to tracking tasks and important timelines.
MichaelC: it would be a good thing for someone to pick up to do. Lisa keeps the high level timeline.
Jennie: i’d be willing to do it if I had some support.
MichaelC: I can give you some guidance.
Jennie: You can put me down for that task: managing a task timeline for this Design Guide project.
stevelee: anyone have any questions on their design review?
jennie: I have met with Lisa on mind
Stevelee: Lisa suggested a working call on Tuesday, Mar 26 10am eastern
kirkwood: sounds good to me
<Jennie> I cannot make Tuesday but will read any summaries posted.
stevelee: any other business
jennie: thank you Steve for chairing the meeting
trackbot, end meeting
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) Succeeded: s/listing/listed/ Succeeded: s/steveless/stevelee/ Default Present: JohnRochford, stevelee, Jennie, Roy, Glenda, kirkwood, Rachael Present: JohnRochford stevelee Jennie Roy Glenda kirkwood Rachael Found Scribe: alastairc Inferring ScribeNick: alastairc Found Scribe: Glenda Inferring ScribeNick: Glenda Scribes: alastairc, Glenda ScribeNicks: alastairc, Glenda WARNING: No meeting chair found! You should specify the meeting chair like this: <dbooth> Chair: dbooth Found Date: 21 Mar 2019 People with action items: 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]