<stevelee> @LisaSeemanKest, hi - were in the meeting now
<Rachael> scribe: Rachael
<LisaSeemanKest> scribe: rachael
<LisaSeemanKest> https://www.w3.org/WAI/GL/task-forces/coga/wiki/PlanningPage#Timelines_and_actions
Lisa: Actions. The first is
sharing content-usable. The document we created has great
content. We have a google doc that tracks it and we will
discuss it.
... Janina was going to work on a persona. Did you get a
chance?
Janina: Not had a chance to work
on it yet.
... Justine's action on policy postponed 2 weeks.
EA and Abi: Working on personas. Do you want to move that to an agenda item for next week?
Abi: Emailed steve with links to open images that match up with the standards.
Lisa: So that is ready for Steve
to add.
... did you see any personas missing?
Abi: I've seen a few people use and I'm trying to find out if we can use them. Aging and dementia. Slightly different variations that might be useful to incorporate
Lisa: So the suggestion is we add persona on aging? Is that the suggestion?
Abi: I think we have 1 or 2, but these are more in depth. The current personas are aging and a disability. The personas that I'm looking at were developed based on focus groups with individuals. If we can get permission, they would be a nice addition.
<EA> is there a template for the personas as I feel we need to keep with the W3C type personas
Janina: That is a separate question about whether we'd want to publish someone else's copyrighted content. The content isn't copyrighted but we could fill out ours with missing content without violating copyright. May I see the personas?
<EA> We can easily make our own based on what we know
Abi: The content is available in a paper as part of a research activity but they are making the content available on a website so was planning on circling back with them.
Lisa: We have Alison an aging individual with mild dementia and another. Can we flush those out?
Abi: I'd prefer to send an email since this is complicated.
Janina: I like the idea of tying aging in
Abi: These cover parkinsons, dementia, and aphasia.
Lisa: Steve, you were working on
resources on the WAI website. The editorial team meeting may be
a better place for that
... The editorial team is for content usable.
Steve: I think we're going to discuss where content overlaps. I've been working on what I think is a good approach. I have something to share but it will take up a good bit of a meeting. I'm here next week to discuss.
Lisa: Getting the design guide
online will be next week
... Separate action to get resources on website.
Steve: I created a series of landing pages that point to resources. The next step is moving the personas into the existing personas rather than a separate set.
Lisa: How about we have a call midweek to work out what you've done. Steve to send Lisa some times next week and then we'll discuss this in this meeting next week.
Steve: Abi sent the pictures but I wasn't sure what to do with them. It sounds like I should add them to the personas?
Abi: They are direct illustrations with creative commons so can be used/reused with the personas.
Steve: Its a matter of picking them and putting them in a persona.
Lisa: We have quite a few.
Steve: I'm clear.
Lisa: We'll have a call to move
those two things forward.
... weekly update on 2.2. Does anyone have an update?
Steve: Authentication was started but we need a follow up meeting. John, Rachael and I will meet tomorrow. Others are welcome.
Rachael: I spoke with David and he's started. We are discussing a meeting.
Jennie: We have a draft that was sent to COGA. We are getting ready to go to the AG group in the next week or two. JF sent feedback.
<alastairc> Tracking spreadsheet: https://docs.google.com/spreadsheets/d/11IKqjRFvkRd2dAfUiyc5whhB3yIYXvSiirWct7KQIB0/edit#gid=0
Steve: New tab is for potential new SC that come up as we work
https://docs.google.com/document/d/1e46eqQnVYqdSyqo29pyJoY1QynRH9v95YW8soTTbfsU/edit?usp=sharing
Rachael: The link above is for David's.
Jennie: I noticed in the COGA resource spreadsheet, I only have read access. Do you want the leads to edit as we go?
Steve: I will add everyone who is interested to edit.
Lisa: that makes more sense. Can
you also link it into our planning page?
... Is it OK to leave any long term pending actions?
Jennie: Question. The document that was open for public comment. Is that on today's agenda?
Lisa: It is.
<LisaSeemanKest> https://www.w3.org/TR/coga-usable/
Lisa: Next item is updates. The
first is that Content Usable has been published. We can start
with the outreach. The design guide is in the appendix.
... we've got an item about disseminating it.
<Jennie> Yeah Rachael!
Alastair: We have been looking for a cofacilitator for a while to help with coordination. We're happy to announce that Rachael will be the co facilitator.
Lisa: That is a good synergy.
<LisaSeemanKest> lol
Janina: You all have known me to
only have a single hat. I speak my mind and am vendor neutral.
I took a consulting job which sends me to Silver and AG as a
representative for Amazon.
... I want to be very clear about where I am speaking in what
hat. What I say here is only with my invited expert hat.
... I will be very clear if I'm ever talking with a different
hat. Amazon is very focused on Silver. I will be using a
seperate email and login with my Amazon hat. If you have any
questions, now is a good time to ask.
Steve: Congratulations. Its important work.
<Jennie> Congrats to Janina!
Lisa: Thank you for the heads
up.
... any other updates?
<LisaSeemanKest> Glossary structure: see mockup at https://lists.w3.org/Archives/Public/public-cognitive-a11y-tf/2019Jul/0036.html
<LisaSeemanKest> https://www.w3.org/TR/2006/WD-WCAG20-20060427/appendixA.html
Lisa: The mockup is similar to WCAG. We can add categories but where we can, we should mimic.
Jennie: I need two pieces of
information. I need which document(s) the glossary item
appears. It would help to order it (alphabetically or
otherwise) in a way that makes it easy to tell whether a word
is being worked on or not.
... this is alphabetical.
... Keeping a reference to the where the words are used will
make it easier to go through and review the vocabulary.
Steve: We want a single master word list. I am trying to think of a way to do it.
Jennie: Right now we are looking at the html version but there are many ways to do so in Google Docs. I'm happy to do it in a way that works best.
Steve: A comment on each word may work.
Jennie: Janina, can you speak to whether comments in Google docs are accessible?
Lisa: It sounds like a table so that it is sortable. I think in the end we will delete the list of documents its found it. For now, perhaps a heading or should we make it alphabetical with a heading structure?
Steve: I think we make it alphabetical
Abi: I was going to suggest the right place to start is to use a spreadsheet with what we want to populate and have columns with the additional information we need. I do think its important to keep alternatives as words have different meanings in different countries. I think it will be easier in a google sheet.
Lisa: I just want to clarify that the point of the glossary is to harmonize the use. We have to say "learning disability" and use it consistently and have an alternate use "specific learning disability"
Jennie: I think part of this is clarifying the difference between vocabulary, editing process, and final format. The original conversation was about a draft document. I really like that conversation because it is helpful to those of us doing the work. I think we need to adjust the usage but we need a way to track the work.
<Jennie> +1
Lisa: I think we agree that we want alphabetical in the final and to also have a google sheet that has the extra information. Is that correct?
<Abi> +1
+1
<JustineP> +1
<stevelee> +1
Janina: I understand the spreadsheet right now. Do we agree that we won't publish the spreadsheet?
Lisa: The spreadsheet is our way of working but we expect it to end up in a document.
<Jennie> * Rachael that was Janina
Lisa: The plus of having a working document is to allow us to mark things high priority so we have a small glossary but don't lose the working content.
<Jennie> +1
Jennie: Do we need to decide to
who will move it? I am willing to do so but would like input. I
will start a google sheet and ask for feedback on the
columns.
... is there an official document space?
Lisa: If you can send it with one
filled in that would be fantastic.
... perhaps add a note that it is the internal resource. So we
are clear.
Janina: I think we want a glossary but I don't think we want an editable glossary.
<LisaSeemanKest> https://docs.google.com/document/d/11zD_-yePfku549aedni1JvfVLcvp2micQ4Own5c06is/edit#
Lisa: We've worked really hard on this publication. There is more work to do but compared to what is available right now, it is so useful. We have enough now that we can collect useful feedback on what direction it needs to go in.
<LisaSeemanKest> https://docs.google.com/document/d/11zD_-yePfku549aedni1JvfVLcvp2micQ4Own5c06is/edit#
Lisa: We're aware it editorially
we need to improve it, but what else do people need? The more
feedback we get, the better position we are in when we go for
review of the final draft.
... the page above is a list of organizations that we sent it
to last time but we likely want to expand the organizations we
send it to.
... There is a draft email to use. You can make changes you
feel are needed to the draft. You can also add your name and
list people you want to reach.
... Can I give that as a joint action item?
abi: I just wanted to clarify
that where you have organizations, do they need to be
orgs?
... we do a public review for some.
Lisa: Are we ready for that?
Abi: I think some individuals would be able to give valuable feedback. Others may find the current draft a bit too much for them.
Steve: I agree that if we change it after a public review it may cause confusion.
Lisa: Should we be very clear about that in the email?
Abi: Yes, I think we should.
Lisa: In the email, we should
perhaps say "Please note that this is an early draft that will
change. We realize there is a lot to do editorially but we
would appreciate your feedback and comments as we move
forward."
... does that allay your worry a bit?
Steve: They are getting something out of it.
Abi: May I suggest that we adjust orgs if we interact with them.
Jennie: I'm noticing a lot of these groups are national and international. What are the thoughts on sharing a next level down? State or subject matter experts?
Lisa: I think its a super idea. Part of the reason to have the table is to make sure we ask people for feedback and don't duplicate efforts.
Jennie: Is there a protocol for who is supposed to contact them? If they are local and we contact them, do we just put our names there?
Lisa: There will be a formal announcement to the WAI list but we can send out announcements before then.
Steve: Suggest pinging Roy to make sure the announcement will happen.
Lisa: Other comments?
... I think its a good point that having different types of
people looking at it will be useful.
<LisaSeemanKest> scribe: steve
<Jennie> Link without quote: https://www.w3.org/WAI/GL/task-forces/coga/wiki/Actions
<stevelee> Rachael: would like to discuss options for organising the wiki to help with our action tracking
<Jennie> Option 1: +1
<stevelee> Lisa: think lisa thinks tables
<stevelee> Steve: opt 2 (tables )Is cleaner but doesn;t tack group actions
<stevelee> lisa: how about a kanban?
<stevelee> Jennie: should record completed items as people miss meetings an might mis completed work
<stevelee> ...also should not have too many place ot find content
<stevelee> ...prefer option 1 is my preference
Lisa: Editors group meeting in about 2 hours.
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/Justina/Justine/ Succeeded: s/Justine/Janina/ Present: Jennie janina MichaelC stevelee Found Scribe: Rachael Found Scribe: rachael Inferring ScribeNick: Rachael Found Scribe: steve Scribes: Rachael, steve WARNING: No meeting chair found! You should specify the meeting chair like this: <dbooth> Chair: dbooth Found Date: 25 Jul 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]