Meeting minutes
<Lisa> Coordinating editors draft for issue papers . see https://
<Lisa> next item
<Lisa> see https://
Lisa: Agenda item 1 - Looking at timelines
… Deliverables: Making Content Usable, update key research papers. I moved Phase 1 which was targeted for end of April.
… Phase 1 now moved to end of July
… Issue papers will have working drafts in September
<Lisa> are we ok with new timelines
<julierawe> +1
+1
+1
<Lisa> +1
<Lisa> any objections
Lisa: This new timeline gives us some breathing room.
… I think we'll end up with better results at the end of the year.
<Lisa> next item
<Lisa> close item 2
<Lisa> next item 3
<Lisa> https://
Lisa: Recaps beginning of meeting and agenda for today.
<JMcSorley> Changed the timelines a bit - we are hoping to get the editor's draft of issue papers a little earlier than we had originally thought.
<JMcSorley> The action items include supported decision making, which will need to be revisited when Becca is available. We have one issue paper that is already in and two more that are close: Way Finding and Safety
<JMcSorley> Lisa: Would love to have Supported Decision making in the editor's draft - do people feel they can make their contributions to Supported Decision Making by the end of May so that we can get it moved to GitHub?
<JMcSorley> Lisa: Should we go ahead and put this into GitHub with editor's note
<JMcSorley> Rashmi: Could we stretch the timeline by about one week?
<JMcSorley> Lisa: That sounds doable
<JMcSorley> Lisa: Janina has asked for the end of this week to make sure that she's comfortable with the structure in GitHub - right now it's in a branch.
<Lisa> https://
<JMcSorley> Lisa: We don't have an introduction, but we have a note that we will add one; we have modules, and I think we can add safety. Older issue papers are in a separate section.
<Lisa> https://
<JMcSorley> Lisa: Please review the link provided and let us know if you have any concerns. We also need to look at conversational voice systems - not so much the content, but everything around the content - is the structure okay?
<Lisa> 1 st august as review date for Cognitive Accessibility Issue Papers - Conversational Voice Systems?
<Lisa> any feedback on stucture: by end the week on https://
<JMcSorley> Lisa: I suggest the end of July or first of August for feedback on Conversational Voice Systems - look it over and give feedback on the structure by the end of this week, but on the content by the first of August.
<JMcSorley> Lisa: If I can get feedback on the structure by May 10, 2024, then I could move those structural suggestions to our other issue papers.
<JMcSorley> Lisa: just feedback on the structure and wrapping on Conversational Voice Systems by May 10, 2024.
<JMcSorley> Rashmi: How do we give feedback on Conversational Voice Systems?
<JMcSorley> Lisa: We had this as a Google Doc for a long time, but now it's in GitHub. I would say that providing an email would be okay.
<JMcSorley> Lisa: Please make sure that the email subject line says "Comment on Conversational Voice Systems" so that it's easy to track
<Lisa> next item
<Lisa> close item 3
<Lisa> next item
<julierawe> Please add me to next Thursday's Github meeting, thanks
<JMcSorley> Lisa: Anyone who is editing in GitHub, we are having a call every other Thursday at 9:00 a.m. EST / 4:00 p.m. Israel - we are doing this to support each other while we make changes in GitHub.
<JMcSorley> Julie: Is it from this coming Thursday or a week from this Thursday?
<JMcSorley> Lisa: It's a week from this Thursday - May 16th.
<Lisa> editorial list https://
<JMcSorley> Lisa: Frankie took an action item and we were thinking Julie might want to join in: when people are making a change and we've agreed to add something like a bullet point, the editing of the document is painful and it's a big document - we want to make sure that they check against the guide we have so that it's consistent across the document. We
<JMcSorley> need to be consistent throughout the document. We have a list that we did for the final edit. There's an older editorial list, but it's difficult to follow. WAI also has its own editor's guide.
<Lisa> wai style guide https://
<JMcSorley> Lisa: What Frankie was going to do was put a list in the General Editorial suggestions so that people could follow those suggestions.
<Frankie> The Google Doc link: https://
<JMcSorley> Lisa: At the time we made the General Editorial recommendations, we may not have quantified it well. We also want to add things from the WAI style guide, but we need to make sure that it does not conflict with Content Usable recommendations. Where something isn't specified in our editorial list, but is in the WAI style guide, we may want to add it,
<JMcSorley> but we just need to make sure that the recommendation does not conflict with Content Usable. That is the job - we were wondering if Julie wanted to participate and we need to highlight any suggested changes so that we can discuss and agree on final styles we will use.
<JMcSorley> Julie: Yes, this is something I need to learn how to do, so I am happy to work with Frankie on the General Editorial checklist so that it looks like the same person has done the writing.
<JMcSorley> Lisa: When do you think we can have a draft?
<JMcSorley> Frankie: Can Julie and I talk and get back to you later this week?
<JMcSorley> Lisa: Yes, it's hard to move forward without this guidance, so the sooner we have a checklist - even a draft checklist, the better.
<Lisa> next item
<JMcSorley> Lisa: the rest of the call is to discuss the new color pattern.
<JMcSorley> Lisa: we reviewed a lot of research, but this is a difficult concept because there are different cultural norms - we think we need more research, so we're hoping that maybe John K could add some additional research.
<JMcSorley> Lisa: We don't want to be specific in a way that won't work cross-culturally or with different types of content.
<JMcSorley> Rashmi: The pattern name would be use color to aid orientation and focus - this will help orient users
<JMcSorley> Rashmi: this will help with focus and support people with working memory difficulties
<JMcSorley> Rashmi: we should use limited colors to avoid cognitive overload - use color to identify main content
<JMcSorley> Rashmi: Color can affect emotions - don't use colors that can increase anxiety
<JMcSorley> Rashmi: This needs more review and research
<JMcSorley> Rashmi: Color can help users orient themselves and can help with way finding
<JMcSorley> Rashmi: Color can help understand visual hierarchy.
<JMcSorley> Rashmi: Can help users focus on tasks.
<JMcSorley> Rashmi: Can help users find key content, such as safety warnings
<JMcSorley> Rashmi: There needs to be other visual queues other than color
<JMcSorley> John: This is great, but I think we're missing one key concept: findability
+1 to adding find-ability (John's note)
<JMcSorley> Lisa: Do we want that in the title, in the text, or as a bullet point?
<kirkwood> just “Findability is the ease with which information contained on a website can be found”
<JMcSorley> Lisa: We have patterns on findability, but have not used that word. Do we want to define findability here or in a different pattern?
<JMcSorley> Lisa: I think we should define "findability" under our patterns for finding that we already have.
<JMcSorley> Lisa: We have 2 patterns related to finding content, but in the pattern on color, mention that we use color to help people find things, but then define what we mean by that.
<JMcSorley> John: Use color to increase the finability of things - I think it's important to use that term.
<JMcSorley> *findability*
<Lisa> Findability is the ease with which information contained on a website can be found
<Lisa> simpler option: Use color to help users find the content they are looking for or need.
+1 to using the plain language version
<kirkwood> i like findability ;)
<JMcSorley> Please vote: option 1 - use the term findability and have to define it, or option 2, the simpler option
<kirkwood> +1
+1
<JMcSorley> +1 - combining findability in parentheses after the simpler language
<kirkwood> +1 - combining findability in parentheses after the simpler language
<JMcSorley> Rain: I love this - there are so many reasons for helping people understand the use of color. It also extends to experiences of low vision. I am concerned as a UX designer and someone who manages UX designers - I am worried that a designer might be overwhelmed and lost on how to do this. It might negate itself with the way it's written. It's fine
<JMcSorley> as an educational piece, but not very clear as a pattern.
<JMcSorley> Rain: we need to find a way to make it actionable - go through each of the bits and think through how a designer can use this.
<tburtin> +1 Rain
<JMcSorley> Rain: for example, using different colors for different sections is helpful, but other sections are less quantifiable.
<JMcSorley> Rain: we should avoid making suggestions of specific colors because colors mean different things to different people - there may need to be some guidance for considering localization and considering personalization.
<kirkwood> +1 to Rain, & all points … wondering could language include to highlight critical information? prioritized information?
<JMcSorley> Lisa: these are parts of the reason that we need a huge amount of research to backup more quantifiable recommendations; I did not see clear research that gave us guidance on what to do. I understand the need, but without the research, we a a little stuck.
<JMcSorley> Rain: This is definitely a tricky one, but I think we need to give this more thought to how to make this more practical for designers.
<JMcSorley> Lisa: My fear is that we don't have the backup research. I hear what you're saying. I can give this a shot at reworking this, but I am not a designer, so I hesitate to take that on.
<JMcSorley> Tiffany - I agree with Rain; I am a designer. Maybe we can do a working session after GAAD - maybe late May / early June.
<kirkwood> +1 to working session
+1 to working session
<JMcSorley> Lisa: There are 2 ways to move forward: (1) Working session; (2) Have a designer like Rain or Tiffany.
<tburtin> I'm presenting for GAAD so I'm unavailable till then.
<JMcSorley> Lisa: We will do a working session, but late May / early June means that this pattern will be in the second working draft.
+1 to June 6 at proposed time
<JMcSorley> Lisa: I think we will do the first Thursday in June for this working session - an hour before our regularly scheduled COGA subgroup calls. June 6th.
<kirkwood> +1
<JMcSorley> Lisa: June 6, 2024 - 10 Eastern for a working session
<JMcSorley> Tiffany: I think I can make that work.
<Lisa> 10 easten
<JMcSorley> Lisa: John, Rain, and Tiffany can all be there at 10:00 EST, June 6th