<scribe> scribe: AbiJ
Steve: introducing Shawn & WAI website. Looking at a landing page for particular topics including COGA
<shawn> Requirements https://github.com/w3c/wai-cognitive/wiki/Landing-Page-Requirements-Analysis
<JohnRochford> Shawn, once again, I thank you for the wonderful work you did on https://www.w3.org/WAI/!!!
Shawn: requirements covers purpose of the page, the audience
<shawn> draft page "Cognitive Accessibility at W3C" https://www.w3.org/WAI/cognitive/
stevelee: this is a staff page, written & maintained by w3c staff. They are asking for input
shawn: this page will probably sit under standards and guidelines. The COGA team pages are likely to flow from this
<JohnRochford> I am done.
<JohnRochford> All looks really good.
JohnRochford: question - the text on the section linking to guidelines, its not clear that these are just a few examples.
shawn: this can be reworded. But in the future it will also link to other standard (ATAG, Sliver etc)
JohnRochford: Get asked for a resource that lists all the guidelines related to coga
shawn: we are working on that
AbiJ: will share the paragraph on the extended description of coga
<shawn> to open new issue https://github.com/w3c/wai-cognitive/issues/new
shawn: send further comments by raising issues in GitHuB or by email
<johnkirkwood> Cognitive and learning disabilities impact how people process *or remember* information. -suggestion
<shawn> https://github.com/w3c/wai-cognitive/issues/2 link to Understadning or TR ?
shawn: there is an open issue about where to link to
<stevelee> https://www.w3.org/WAI/PF/cognitive-a11y-tf/
<stevelee> https://www.w3.org/WAI/GL/task-forces/coga/
<stevelee> https://www.w3.org/WAI/GL/task-forces/coga/work-statement
stevelee: introducing that updated task-force page on the new WAI website
<JohnRochford> Looks good, Roy!
<JohnRochford> +1
+1
shawn: wai site has notable increase in traffic since the redesign
stevelee: please let Roy know if there are any comments or tweaks needed on the task-force page
<stevelee> https://w3c.github.io/wai-coga/coga-draft/guide/
stevelee: introducing the latest iteration of the design guide online. Based on the mock up
JohnRochford: is every items that are redundant, is there overlap?
stevelee: there does seem to be. We need to review the content all together, once it is all drafted
<JohnRochford> Great start, Steve!
<EA> +1
<johnkirkwood> +1
<EA> I agree with everyone about the new designs
<johnkirkwood> Provide help for complex information. Maybe give a plain language description of complex information {s.a data/graph} element ... not sure if its the time to say this
AbiJ: should the patterns be
numbered? It helps with communication particularly if the text
is translated
... would also help to have a link to the overview in the
navigation (thinking hierarchical structure being transparent
to all)
stevelee: will look into possible designs through the WAI sites
EA: will this part of the site be standalone and look different?
<stevelee> https://www.w3.org/WAI/WCAG21/quickref/
shawn: I am looking to intergate as much as possible and it will be consistent (e.g. the understanding documents are moving to the WAI site)
<JohnRochford> FYI for Shawn and All: This article has a list of SC for COGA - http://www.davidmacd.com/blog/wcag-for-low-vision-cognitive-disabilites.html
stevelee: update on WCAG work.
Still alot of discussion whether 2.2 will go ahead, but looking
likely. But expect less new SCs that 2.1 and take 2 years to
get to recommendation
... we will need to work closely with the WCAG2.2 group to make
sure they have the info they need from us. Possibly a
sub-group
... asking for volunteers
EA: I have raised that felt
unable to vote on CFC due to the technical requirements of
SCs.
... concerned that we are still trying to embed 2.1 so
concerned about moving on to 2.2
steve: we need someone to shepard our requirements to the group
EA: that person needs to have a technical understanding to ensure that the techniques and testable statements can be drafted correctly
AbiJ: have concerns that 2.1 is not fully embedded and that we will be diluting effort
stevelee: moving on to drafting the design guide
<stevelee> https://docs.google.com/document/d/1aJE2C0FzzzXgydEp0MNGSdDDvUTTsANViUVvciFK36k/edit#
AbiJ: how are we allocating patterns to review
stevelee: we should be adding our
name in the first column and then add complete in the same cell
when ready to review
... will communicate with lisa and group to confirm
process
... there are still a couple of patterns that do not have a
name against them
... The table at the top of the google doc contains a link to
the github version.
... idea is that everything will be drafted and reviewed in the
google doc.
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/They are asking for feedback/They are asking for input/ WARNING: Replacing previous Present list. (Old list: Steve, Abi, Shawn, John, Shari, Roy, JohnRochford, johnkirkwood) Use 'Present+ ... ' if you meant to add people without replacing the list, such as: <dbooth> Present+ Michael WARNING: Replacing previous Present list. (Old list: Michael, MichaelC) Use 'Present+ ... ' if you meant to add people without replacing the list, such as: <dbooth> Present+ Steve, Abi, Shaw, JohnRochford, shari, johnkirkwood, michael WARNING: Replacing previous Present list. (Old list: Steve, Abi, Shaw, JohnRochford, shari, johnkirkwood, michael) Use 'Present+ ... ' if you meant to add people without replacing the list, such as: <dbooth> Present+ Steve, Abi, Shawn, JohnRochford, shari, johnkirkwood, michael, Roy Present: Steve Abi Shawn JohnRochford shari johnkirkwood michael Roy EA Found Scribe: AbiJ Inferring ScribeNick: AbiJ WARNING: No "Topic:" lines found. Found Date: 28 Feb 2019 People with action items: WARNING: Input appears to use implicit continuation lines. You may need the "-implicitContinuations" option. WARNING: No "Topic: ..." lines found! Resulting HTML may have an empty (invalid) <ol>...</ol>. Explanation: "Topic: ..." lines are used to indicate the start of new discussion topics or agenda items, such as: <dbooth> Topic: Review of Amy's report 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]