Meeting minutes
scribe list : https://
close item 4
not at quarum
scribe list : https://
next item
Lisa has done a little bit of updated "COGA Action Items" but would like us to review as well.
Lisa reviewed Making Content Usable area of the document
Lisa We will need to have a detailed discussion on the testing
Rain The community is working on a couple of topics and Rain is joining the community group meeting to sync
next item
Lisa Meetings this week, Mental Health 8 est, and then a two hour block.
next item
Lisa, Holidays assuming we are taking the week of Christmas and the week after. Is this ok with everyone
<Jennie_Delisi> +1
<tiffanyburtin> +1
next item
Holiday from 23 December 2024 to 3 January 2025
2 weeks
Rain sharing structure document with two different intros to the document based on the information Rain received. The studies make it very clear that we need to make sure to be intentional where we place the information and keep a clear structure to the document. Rain believes we will need two versions of the document. One very friendly one very
structured
Rain renamed a section to Quick Start Guide.
Rain found that it was important to give an introduction currently "Abstract (introduction)"
<julierawe> Could "Stauts of this document" be a 4th accordion?
Rain Our three sections are now an accordion to meet the TR requirement
Rain Questions?
<Zakim> Lisa, you wanted to ask about buisness devlopment , mapping etc
<julierawe> (IRC kicked me out)
Lisa prefers the three button version. Would like to add a label with Legal Stuff in it to help orient users on what pieces of content reside where
Lisa and Rain want to make sure the Appendix to have the business cases available
Jennie_Delisi Concerned about Zoom
Rain has the intention of responsive design for zoomed and mobile use
Jennie_Delisi will the numbered areas be a numbered list. Rain Yes it would be an ordered list.
Jennie_Delisi last question is in the second example, concerned with semantic heading structure
Rain We need the headings to be styled as clear headings
rain: tiffinay can test is the summarised version is availible via screen reader
scribe+ present+ IRC kicked me out
scribe+ Rain the fuller table of contents would still be there, but we found in our research that the quick start guide was really needed
Jennie_Delisi if a person was looking for forms, it would be under Design and Build. We would hope that the user would do a find function to find the word Form.
<Jennie_Delisi> * That was Julie.
Jennie_Delisi Why is users under design and build. Rain said that most users who come to the document already know this is important so the design and build is first. Know your user is second for building the business case. We had users that felt seen by having the Know your user high in the heirarchy.
<Jennie_Delisi> * That comment above was Julie as well. She is making some great contributions!
Sorry Jennie, those last two comments were from julierawe
<Jennie_Delisi> * No worries tiffanyburtin - I bet it is based on the way IRC grabs the codes for people's names.
Rain and tiffanyburtin may need to huddle on design separately
<julierawe> +1 to John and Lisa—seems more logical to start with know your user
<kirkwood> we can emphasize design and build in some way.
Rain In another accordion section where we have icons to aid the meaning of the information. We originally had longer headings, but we are better off having short word heading and a descriptive sentence directing following the heading.
Rain we need to still flush out this design slightly
Lisa likes the quick sentence, but at the same time she would like to know what is included in the section.
I think we will have the TOC still to express that detail Lisa
<julierawe> +1 to Lisa suggestion to have the descriptions give sense of what kinds of things you'll find in each of these sections
findability
julierawe a short sentence of what is included and summary, but make them different. (julie please feel free to restate this)
<julierawe> If we can have short sentences that feel different from each other, great! If they start to sound similar, maybe we skip the high-level descriptions and just detail the "what you'll find"
tiffany: table of content should be always availibel as well. so tere are multiple ways for difrent types
rain: that was most interesting part of studies is the table of content is realy important
but the toc was hard to find
jennie: taggs? can that help support high frquescy use pices such as forms. so a filter
<kirkwood> keyword area?
rain: in tr we could do it in an apendix only
but in the web version we can do it
ironicly ong term w3c users did not like it. but everyone else did like it
but they will probably look at the tr version
<julierawe> Kudos to Rain and team!!!
next item
<kirkwood> well done Rain!
<Lisa> +1 too fantastic job
jan: internatiolization sub group on wensday at 9 est
Lisa: We have a Mental Health subgroup meeting at 8:00 EST on Thursday and then 2 hours of an editor's meeting and then the structures group at 11:00 EST
<julierawe> The 2-hour editors call is this Thursday, November 21st at 9am ET
Lisa: Let's see if Eric can make an agenda for the editor's meeting.
<julierawe> I agree with Lisa!
<julierawe> Lisa suggested we prioritize getting Rashmi's changes into the new template for Content Usable, and deprioritize getting the issue papers ready.
julie: new set of outcome subgroups
there is text aperence. will tak=lk about font
Julie: Question about the new set of WCAG 3.0 Outcome Subgroups - one of them is about text appearance and I think it's going to get into Cognitive territory, such as what type of font is best. Does anyone want to join any of these subgroups?
Julie: Each group has set different times to meet. Tomorrow, the groups are meeting during the 2nd half of the AG meeting.
Julie: I sent information about the subgroups when the survey went out. Julie will send out a reminder about what the groups are and how to join.
<kirkwood> +1 to lisa
Lisa: There is a lot of information out there about fonts - some of which is not true or useful
Lisa: Internationalization will be important to the text / font discussion
John: I attended the views subgroup and there are cognitive implications to that regarding changing views and the amount of information on the screen.
john: has joined the views. important for cognative design