<scribe> scribe: jeanne
Results of survey: Four were happy with the time, one wanted a different day
AC: I will follow up with Lisa who has a conflict with the call
AM: This works for me, except for August when I have conflicts.
AC: How frequently would you like
this call? Some said weekly, others said every two weeks.
... we will see the momentum, I think it will be every two
weeks, except when I am on holiday at the end of this month
https://www.w3.org/WAI/GL/task-forces/silver/wiki/Main_Page
<alastairc> Jeanne: Various links, starting with wiki. Working since 2016, tasked to beginn the prelim-work on next major version. Aiming to be more broad, so not 'wcag 3', been using silver ("AG") as the working name.
<alastairc> Jeanne: Been doing research, the wiki page links to all of those. In March, at CSUN, we did a design sprint. Had 27 top-people from accessibility, CEOs, designers, devs, people from policy, lawyers, and PwD.
https://www.w3.org/community/silver/2018/04/23/suggestions-of-silver-design-sprint/
<alastairc> Jeanne: Gave them all the problems from the research, and said: go solve them. Many good ideas coming from that. Report came from that. It is quite long, but there's a shorter blog post.
<alastairc> Jeanne: Anyone can join the community group, just needs a free W3C account, so please do join.
<alastairc> Jeanne: Would like people from various locations to discuss things themselves, in their location/language. We'll be testing prototypes soon, that's our current work. Making & testing them.
https://w3c.github.io/silver/requirements/index.html
<alastairc> Jeanne: Also working on the requirements document for Silver, which is what we've been discussing in the group.
<alastairc> Jeanne: Would be great to talk about this in Australia, which is the github 'repo', which has the links & prototypes.
<scribe> scribe: jeanne
<alastairc> https://www.w3.org/WAI/GL/wiki/Wcag21-techniques#List_of_Techniques
AC: We have published 2.1, every
success criterion has an Understanding document
... we have 70 Techniques to write. We have 10 in process.
\
... there are many to choose from, we would like help in
working on them
... color contrast: how to meet. One of the techniques could be
about contrasting colors in a pie chart.
AM: Good timing. I just worked on the practice of going through the Understanding document and working on the easiest way to test it.
<alastairc> https://www.w3.org/WAI/GL/wiki/Wcag21-techniques#Creating_Technique_documents
AM: I'll have a proper look at it
next week.
... we have a template for the sections. Once you get used to
it, it takes about 20 minutes to write a first draft for the
Technique. Then the group will comment on it.
... in Github, create your own branch tech-(technique
name)-(your name)
... write your technique, then create a pull request.
... put in an explanation including the success criterion it is
for
... a handful of people will comment on it, then put it in the
weekly survey
<alastairc> https://github.com/w3c/wcag
AM: it is an easier process than writing a Technical Report document, so if anyone finds an error we can just update it.
AM: Starting July 1 I have some
designated time for W3C groups
... I also participate in EO
<alastairc> Questions: AGWG Chairs <group-ag-chairs@w3.org>
AM: I am excited to have some Australia-friendly timing
<alastairc> trackbot end meeting
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) Default Present: Roy, jeanne, AMace Present: Roy jeanne AMace Found Scribe: jeanne Inferring ScribeNick: jeanne Found Scribe: jeanne Inferring ScribeNick: jeanne Found Date: 12 Jul 2018 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]