<LisaSeemanKestenbaum> https://docs.google.com/document/d/1WcfVALVq8PS9CLXUuAfV9Op0wXvI2yJYedj5jO23GTk/edit# (user testing and user stories?
<LisaSeemanKestenbaum> scribe: glenda
Lisa: Cognitive Accessibility Roadmap and Gap Analysis - should be published today.
Lisa: this google doc is the draft of the email to announce the newly published roadmap and gap analysis.
... at the bottom of this google doc is a list of groups to announce this new publication. Double-check this list to see if you have suggestions for additional groups we should announce this to.
Lisa: looking at how we can make finding what you need (wayfinding) on the new COGA Roadmap and Gap Analysis.
... In the personalization semantics pub, we improved wayfinding by breaking things into modules. We may want to do this type of structure for the COGA Roadmap and Gap Analysis.
Jan: Current user needs looked like a sandbox. It wasn’t easy to consume. Idea: start with the intent of the user needs table.
Lisa: The heding for this section isn’t as clear as it could be. It currently has the heading of “Tables of User Needs” when it is really a Roadmap of next steps for different user needs.
Jan: what is the purpose of this document? Is it for people to come learn? Or is it a sandbox for the COGA task force?
Lisa: We need to define who the specific audience is for this User Needs table.
Lisa: The draft email has wayfinding help, broken into 3 different type of people who may use the COGA Accessibility Roadmap and Gap Analysis.
Shari: It still appears we have quite a bit of redundancy. Since we have the appendix that gives content developers, in the “Table of User Needs”….we have too much info. This section is trying to do too much.
Alastair: I would look at this from an Information Architecture viewpoint. Suggest listing the roles 1) content developers, designers 2) policy makers 3) people just wanting to learn about coga. Then map all the different types of content for each role. Once we do this mapping…we could have a map/wayfinding document based on role. This might lead to a simple map/wayfinding doc…or it might lead to us breaking things into modules.
Lisa: I think that is an interesting proposal.
Jan: Alastair, Shari and I could take a look at your first mapping exercise.
Jan & Shari: Agree this is a good idea.
Janina: most important thing to do is to state the problem clearly. Very useful to provide user stories in a single document. That has to be crystal clear. Then user needs flow from that.
<Zakim> janina, you wanted to talk about the classic standards process re this doc
Lisa: Would breaking this down into multiple documents, would that be good, or cause problems?
Janina: I think breaking this down into multiple documents is needed. Having a stand alone User Needs / User Stories documents will be foundational. It will help everyone understand the needs.
Alastair: Need to modularize this. Parts of this should be in TR, parts should go into Notes, parts should go into EO space.
Janina: we need to make this easier for people new to COGA to be able to consume.
... must start with User Stories. starting with HOW, before someone understands WHY (user stories).
Alastair: can I ask you, Janina, the needs from the W3C for this as a standard document, and what you can suggest for change. So, I can take an action item.
<LisaSeemanKestenbaum> ACTION: janina to sumarise what is needed AND missing from https://rawgit.com/w3c/coga/Pub_June-2018/snapshot/Overview.html#tables-of-user-needs from a w3c section [recorded in http://www.w3.org/2018/06/07-coga-minutes#action01]
<trackbot> Created ACTION-286 - Sumarise what is needed and missing from https://rawgit.com/w3c/coga/pub_june-2018/snapshot/overview.html#tables-of-user-needs from a w3c section [on Janina Sajka - due 2018-06-14].
Jan: Can you provide us an example of what other documents you were refering to, that meet the needs.
Glenda: Let’s modularize this Roadmap and Gap Analysis.
<LisaSeemanKestenbaum> ACTION: alastair to put together a gogle doc of all our publication and what they are and who they are for, and their purpse [recorded in http://www.w3.org/2018/06/07-coga-minutes#action02]
<trackbot> Created ACTION-287 - Put together a gogle doc of all our publication and what they are and who they are for, and their purpse [on Alastair Campbell - due 2018-06-14].
Lisa: also need a list of things to do.
... Do want to look into moving out of Google Docs? Would it be useful to move to Microsoft Cloud?
Alastair: Could we ask the COGA members who have a problem getting to Google Drive…if they can use Microsoft Cloud.
Lisa: Is anyone not available next week because of m-enabling.
<kirkwood> I am willing to help with versioning in google docs btw