W3C

- DRAFT -

SV_MEETING_TITLE

20 Dec 2018

Attendees

Present
MichaelC, stevelee, Lisa, Jennie, JohnRochford, kirkwood, Glenda, janina, AbiJ, Roy, Rachael
Regrets
Chair
SV_MEETING_CHAIR
Scribe
jennie

Contents


<Lisa> afeda+ updates ftf, new people coming, and register

<Lisa> :)

<Lisa> scribe: jennie

updates ftf, new people coming, and register

Lisa: please register if you have not done so already.
... Invited guests: Neil and Mark. And Jamie from the BBC.
... Any other people we should invite?

gap analsis more resucturing https://rawgit.com/w3c/coga/master/gap-analysis/

<kirkwood> coud we put face to face link in here

<Glenda> https://www.w3.org/WAI/PF/cognitive-a11y-tf/wiki/Meetings/Jan_2019

<Lisa> https://docs.google.com/document/d/18TJ8JAC0u0Fa64MnONOA2Cs8MBTcJQxfnFDqK6KVxD0/edit#

<Lisa> https://rawgit.com/w3c/coga/master/gap-analysis/

Lisa: a few things we want to change
... 1: explain a bit better the user need, the user story. Not a formal one, but to build in the case.
... 2: Restructure it, moving the summaries of issue papers to an appendix, and put in cross referencing from the user needs section.
... we also need to look more at the tables - will become more of an "importance" section.
... other suggestions?
... other comments about gap analysis?

<Lisa> https://rawgit.com/w3c/coga/master/gap-analysis/#table1

Steve: one table is still present, and it reflowed, but it had less information.

Janina: the explanation of what the issues are, through use cases are what is most important.
... Making the case by adding more information is how we typically work; but less is more is important to make the case.

Lisa: last week Abi had a good reminder about the definition of disability.

<janina> What we say about authentication in Gap Analysis 2.3.2.1 is undistinguished what is generally said about that issue, example:

<janina> https://www.nngroup.com/articles/passwords-memory/

Lisa: for each use case, could we move the personalization in a new section underneath, to reduce the amount of content in the table.
... Proposed new semantics and personalization into a separate table?

<stevelee> +1 to splitting out personalisation from the tables

Lisa: other things needed for gaps analysis or other proposals?

Janina: after this change is made, propose taking another look at that time.

<AbiJ> ?

Roy: I can separate the tables.

Lisa: once you have done that, I will add more information about the user needs and the cross referencing.

<AbiJ> Sorry I am struggling to unmute!

<AbiJ> So will type

<AbiJ> I can have a go at writing up my definition of the disability vs general needs

Janina: would like to strengthen the vocabulary for 2.3.2.1

Steve: I can take the second table once Roy has completed the separation of tables.

<Lisa> ACTION: roy to seprate personilsation and semayics from the table

<trackbot> Created ACTION-299 - Seprate personilsation and semayics from the table [on Ruoxi Ran - due 2018-12-27].

<Lisa> ACTION: abi writing up my definition of the disability vs general needs for gap analisis

<trackbot> Created ACTION-300 - Writing up my definition of the disability vs general needs for gap analisis [on Abi James - due 2018-12-27].

<Lisa> ACTION: steve add to one table section the use case etcwriting up my definition of the disability vs general needs for gap analisis

<trackbot> Created ACTION-301 - Add to one table section the use case etcwriting up my definition of the disability vs general needs for gap analisis [on Steve Lee - due 2018-12-27].

<Lisa> ACTION: lisa add to one table section the use case etcwriting up my definition of the disability vs general needs for gap analisis

<trackbot> Created ACTION-302 - Add to one table section the use case etcwriting up my definition of the disability vs general needs for gap analisis [on Lisa Seeman-Kestenbaum - due 2018-12-27].

design guide https://docs.google.com/document/d/1aJE2C0FzzzXgydEp0MNGSdDDvUTTsANViUVvciFK36k/edit#heading=h.dgd1m22rf

<Lisa> topic mockup of pages in the wai by steve

Steve: a proposal for how we might make this easier for web designers and others to find out about cognitive disabilities and techniques they can use.
... I have not made a mock up of making it collapsible.
... Mock ups: not a suggestion of what they should look like, but more about the structure and rough content.
... if proposal is accepted, we can work on content.

<stevelee> https://raw.githack.com/w3c/coga/doc-mock/coga/

Steve: looks like they are part of the WAI website, but they have not been added <smile>
... first page is for people unfamiliar with the topic. Has links to user stories, barriers people experience, then an outline of how to begin to think about designing in an inclusive way. Finally a list of W3C resources.
... that page is a stand alone page.

Janina: this would end up on the W3C.org/WAI, in the cognitive section?

Steve: yes, next to resources for older users.
... the next page is our content user group document - a high level introduction on how to support cognitive needs when doing web development. Focus on thinking more about the content, testing.

<Lisa> https://raw.githack.com/w3c/coga/doc-mock/coga/ensuring.html?env=dev

<Lisa> https://raw.githack.com/w3c/coga/doc-mock/coga/design.html?env=dev

Steve: the third page: a possible version of the design techniques document we have, or something that links through to that. This is where the collapsible information could be included.
... links to WCAG 2.0, how it relates to personalization, then design technique themes.
... bottom: theme example - demonstrates how content could expand.
... final page: for those who want to know more, has gaps analysis, issue papers, user research

<Lisa> do we all agree

<JohnRochford> +1 to Steve's approach

Jennie (as Jennie): +1 to Steve's approach

<Lisa> we want cover page and 3 drop down page

<Lisa> +1

<AbiJ> +1

<Glenda> +1

<janina> +1

<kirkwood> +1

Lisa: suggest revising audience vocabulary.
... for Gap Analysis section

<Lisa> reaserch and anlaiss sub page - hig level introductsion and is this for you

<Lisa> link though

Jennie (as Jennie): +1 to structure of Gap Analysis section

<Lisa> +1

<AbiJ> 0

Abi: people outside the W3C don't always understand what is cognitive disabilities.
... On research and analysis page, are we organizing this by difficulties?

Steve: Gap Analysis page is not organized this way.
... Design themes: more technical ideas around what technology could do to address these challenges.

Abi: consider those looking for information mental health?

Lisa: e.g. if you are interested in security issues with challenges related to those with dementia, how will people discern if gap analysis will include this topic.

Steve: What is in the Gap Analysis has an intro, but we need to consider how to balance how much information is there, but not have too much.

Lisa: if you are coming as a developer or a designer doing some research, you might be using the research section. How do we help people get to the content they want?

Abi: Someone in a meeting knew about COGA, but most people didn't understand the term cognitive disabilities in that meeting.

Jennie (as Jennie): suggest a search function/way of searching by terms, and consider how people will look for mental health issues - different internationally.

Lisa: we also need to consider that sometimes the names of disabilities change.

<kirkwood> very good. I’d rather see language like (but realize its US) https://webaim.org/articles/cognitive/

<JohnRochford> Content reuse is fine if we credit it with references.

<kirkwood> Memory, Attention, Problem Soliving, Reading (Verbal Comprehension)

Glenda: I think it is ok if we have some sections that are tagged using words that a beginner would use, but then clarify the vocabulary in a glossary or in another location.

<JohnRochford> +1 to adding tags, which will also help people find our content

<JohnRochford> For example: Autism, ASD, Autistics

Glenda: consider importance of people viewing the vocabulary they use when reading sections.

<Lisa> (sometimes called autisim

Jennie: +1 to Janina's "sometimes called"

<AbiJ> +1

<JohnRochford> Leaving now. Ciao!

<kirkwood> +q

Abi: opportunity to link to other research or glossaries. This would also help designers be aware of the differences in international terminology.

Lisa: we also need to add these into the terms document.

<Lisa> https://docs.google.com/document/d/1poEoQjuWdAfWM3aOGPCwJRx7EvBsAtQ_99sGyS9Jlgc/edit

John Kirkwood: there are some major buckets of functionality that can be addressed through proper design. Memory/attention/problem solving/reading - designing around the path each of these users would get around the page and consume the information.

<kirkwood> Memory, Attention, Problem Solving, Reading Comprehension

Jennie: offered some user testing opportunities

<kirkwood> Have a great day! well done Steve.

Lisa: next meeting is in two weeks - happy holidays!

Summary of Action Items

[NEW] ACTION: abi writing up my definition of the disability vs general needs for gap analisis
[NEW] ACTION: lisa add to one table section the use case etcwriting up my definition of the disability vs general needs for gap analisis
[NEW] ACTION: roy to seprate personilsation and semayics from the table
[NEW] ACTION: steve add to one table section the use case etcwriting up my definition of the disability vs general needs for gap analisis
 

Summary of Resolutions

[End of minutes]

Minutes manually created (not a transcript), formatted by David Booth's scribe.perl version 1.154 (CVS log)
$Date: 2018/12/20 16:06:57 $

Scribe.perl diagnostic output

[Delete this section before finalizing the minutes.]
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: MichaelC stevelee Lisa Jennie JohnRochford kirkwood Glenda janina AbiJ Roy Rachael
Found Scribe: jennie
Inferring ScribeNick: Jennie

WARNING: No meeting title found!
You should specify the meeting title like this:
<dbooth> Meeting: Weekly Baking Club Meeting


WARNING: No meeting chair found!
You should specify the meeting chair like this:
<dbooth> Chair: dbooth


WARNING: No date found!  Assuming today.  (Hint: Specify
the W3C IRC log URL, and the date will be determined from that.)
Or specify the date like this:
<dbooth> Date: 12 Sep 2002

People with action items: abi add lisa roy steve

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]