Meeting minutes
<Eric_hind> +present
<lisa> Please sign up to scribe https://
<lisa> next item
<Eric_hind> lisa: Internationalization review first item
<Jan> Here's the link to the Content Usable Feedback Spreadsheet: https://
<Eric_hind> Jan: Update on i18n process, community group is offering lived experience, expertise and perspective.
<Eric_hind> Jan: From linked sheet, Katy and Jan have, in column C, flagged review items and took notes in Column E (temporarily)
<Eric_hind> Jan: Column D has high level concepts - there is an ask for additional sensitivity review.
<Eric_hind> Jan: There is some feedback around language related to terminology used - Column E has that discussion around Objectives 1,2 and 5. Objectives 3 and 4 next meeting on Dec 4.
<Eric_hind> Jan: If you check other tabs, some wording suggestions have been made - these will be review and potentially integrated. Some comments are related to editorial cleanup like punctuation. Some concerns were raised about the overuse of the elderly and they wanted some additional examples over older populations.
<Eric_hind> Jan: There is a subgroup and community group. The subgroup is oriented to coga.
<kirkwood> sorry could someone share the doc link again. thanks
<Eric_hind> Jan: Column F indicates where there may be a conflict in viewpoints with i18n group
<Eric_hind> https://
<Eric_hind> Lisa: Has there been outreach to orgs that deal with plain language or learning disability groups in different languages? Are we potentially missing things in terms of guidance? e.g. Speech language pathologist?
<Eric_hind> Lisa: There might be orgs in a given language that could give good feedback related to this.
<kirkwood> +1 .. the aging is very very important
<kirkwood> +1 to Rain’s point about alienation
<Eric_hind> Rain: Our study on new Content Usable showed a lot of quotes (50%) related to understanding the language of the document. And 40% felt the language was isolating/unfamiliar. Multiple participants mentioned they appreciated the reference to multiple languages in one pattern (as a positive)
<Eric_hind> Rain: People wanted to know if this would be applied to multiple patterns?
<Eric_hind> Rain: This could affect what we want to do and how we do it.
<Eric_hind> Lisa: Terms these users feel are hard to understand that could be defined and/or a popup
<kirkwood> +1 to putting together a page
<Eric_hind> Lisa: Should we create a page of discussion terminology?
<kirkwood> +1 for page of learnings
<Eric_hind> Jan: The information has a lot of people reviewing and updating concurrently, but having a process to gather all of this kind of information once more reviewing is done may make sense - try to complete the patterns and note that things are being worked on.
<kirkwood> unified style guide of sorts
<Eric_hind> Jennie: Is there a need for volunteers to take snippets of content to create some options (plain language). Would volunteer to do asynch.
<Rain> +1 that would be helpful, Jennie
<Eric_hind> Jan: This would be helpful. We are doing some AI tools, but there is definitely value in having COGA volunteers.
<kirkwood> maybe even creating ai commands?
<Eric_hind> Kirkwood: Would be good to have a unified style guide that would include our learning so far. Even AI commands that would be useful
<Eric_hind> Lisa: We should be collecting feedback like from Jan and Rain's subgroup and putting it into a 'next review'. Conformance to a style guide and feedback on writing in general. And then an editorial pass on the document with that guide (trying it)
<Eric_hind> Lisa: Two approaches, one is general style. The second are localized to languages that may not support the style/reference. They really are separate and the efforts per language may be very/somewhat unique.
<julierawe> Heads-up that I need to leave this call at 11:50, thanks.
<Eric_hind> Jan: Eventually we can sort it out that way, but for first reactions, things are intermixed (for now). COGA subgroup can work on a second pass to separate things out into components - style guide or more substantive. Will be helpful to prioritize patterns that had most comments and had folks most concerned about.
<Eric_hind> Lisa: Feels like certain kinds of rework could alter meaning.
<Eric_hind> Jan: We can solicit advice on wording change too.
<Eric_hind> Lisa: Dec 16 will be next pass/review.
<lisa> next item
<Eric_hind> Rain: There is some clear data to support changes - will be able to send it Wednesday. A link to a slide deck with screenshots and clickable prototype (Figma). Prototype will allow commentary (not screenreader friendly) . As well a video will be included on justification for the design changes.
<kirkwood> weee a holiday video!
<lisa> :)
<Eric_hind> Rain: A companion doc may also be ready for Wednesday.
<Eric_hind> Lisa: December 9th will be the review of the new template.
<Eric_hind> Rain: Will also be a share of the video to the community group on December 5th. Will be fewer details than our video
<kirkwood> excellent
<lisa> next item
<lisa> close item 3
<lisa> next item
<Eric_hind> Lisa: Please sign up to scribe!
<julierawe> I can't attend on Thursday
<lisa> next item
<Eric_hind> Lisa: Will setup an editors call for Thursday assuming Rashmi and Eric can make it
<Eric_hind> julierawe: Implied meaning/non literal text group will be expanding in scope to include diacritics and other items. That meeting will be today.
<julierawe> I have to drop, thank you
<lisa> thanks julie
<Rain> Figjam of the synthesis of research for those who are curious (not screen reader friendly): https://
<Eric_hind> Rain: Figjam sticky notes includes participant reference (those who had comments) - you can see how many users made similar comments.
<kirkwood> how do you want feedback? Inteereesting points: looking at overview, 18 participants. metadata was overwhelming for some. whole section on stuff to do specifically. heavy use to support for usage. access for curious. Good if need proof and testers.