<JMcSorley> Meeting: COGA Internationalization Subgroup Teleconference
<JMcSorley> scribe+ Frankie
<JMcSorley> Frankie: I will scribe
JMcSorley: Jan created a process
around reviewing the patterns. This was discussed in the
community meeting on May 15.
... Lisa requested we form a working group with the community
group. Jan will be asking for advice on which items to discuss
at the next community meeting on June 5.
... For context, we're trying to get people together in the
community group who have internationalization expertise or
fluency in multiple languages. People do not have to be an
invited expert or a part of a member organization to join the
community group. We want to get more feedback around
internationalization to feed back to AGWG while
working on WCAG 3.
JMcSorley: We need to consider when to have a working session with the community group. That group meets twice a month. We need to do some more recruiting and get more input on the patterns.
<JMcSorley> https://infohub.nyced.org/in-our-schools/operations/accessibility-and-websites/plain-language
JMcSorley: John Kirkwood to explain this link.
kirkwood: This grew out of implementing federal plain language guidance. The structure is very important. These six guidelines are fundamental for plain language and cognitive accessibility. This site links to some other resources, some of which might be behind firewalls. This might be something we can use as an example, since this is an
organization that delivers all of its materials in 9 languages as well.
kirkwood: There was a case related to this regarding internationalization vs localization. The scenario was that a large site needed translation into Spanish. It was done due to a lawsuit, outsourced to a company in Spain. There were so many cultural differences in the Spanish that gave improper information that the translation became incorrect and
it did not satisfy the requirements of the lawsuit.
julierawe: This seems like a very English-forward resource. For example, "use active voice" becomes an issue in Japanese. Another one is "use shorter words." For one example given in the German version, it shows a longer word, another it shows a word of the same length. This document may run into some of the same issues as a result of being so
English-forward.
kirkwood: Correct, this document was made to be understood in English.
JMcSorley: Agreed about the potential for the same issues to be present. Thoughts about the organization of the content? Content Usable is quite dense.
kirkwood: Does EO have anything?
JMcSorley: Taking an action item to determine what might be available on the WAI site around cognitive disabilities.
tburtin: Will check in with a colleague about EO personas they're working on next week. Q: Can we use a TLDR summary/plain language summary and then lead to more information?
JMcSorley: I like that.
<kirkwood> this may be helpful
<kirkwood> https://github.com/w3c/coga/issues/199
tburtin: AI can give high level summaries of documents. Gemini (previously Bard) is by Google and is free. ChatGPT 3.5 is free. Copilot is free when associated with a free Microsoft email. Perplexity AI has a few.
JMcSorley: Tiffany, can you provide links in Zoom chat?
<kirkwood> iso plain language guidance
<julierawe> https://www.iso.org/standard/78907.html
julierawe: Looking to get the new international plain language standard by ISO. It's $500.
kirkwood: What about the Plain Language Association International? plain.org is their website.
<julierawe> https://plainlanguagenetwork.org/plain-language/plain-language-around-the-world/
Plainlanguage.gov, Federal Plain Language Guidelines
Ta11y, Writing Accessible Content, https://www.ta11y.org/learning/topic?key=writing.a_intro
WebAIM, Writing Clearly and Simply, https://webaim.org/techniques/writing/
JMcSorley: Taking an action item to assemble the plain language guidelines for the community group.
JMcSorley: Next time, we plan to review the survey results. It's been a bit of a challenge to find a good meeting time. We also need to make sure we have better worldwide representation and make sure everyone feels like they are able to lend their expertise. We need a lot of different viewpoints here. Recruiting is going to be very important.
<julierawe> Awesome—would love to clean up this doc!
JMcSorley: Thanks to Julie, we have this doc we've been working on for a while. I need consensus from this group to accept the suggestions in this Google doc.
julierawe: The way the mission was bulleted out was to show that these three W3C groups will benefit from the work of the community group.
JMcSorley: It's the role of the
community group to provide recommendations to these groups
around guidance.
... Where should we capture names of people we want to make
sure are contacted about this?
<kirkwood> +1 fo editing
+1 to editing
This is scribe.perl Revision VERSION of 2020-12-31 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: Irssi_ISO8601_Log_Text_Format (score 1.00) Default Present: tburtin, JeanneEC, Jan, kirkwood, Frankie, julierawe Present: tburtin, JeanneEC, Jan, kirkwood, Frankie, julierawe No ScribeNick specified. Guessing ScribeNick: Frankie Inferring Scribes: Frankie WARNING: Could not parse date. Unknown month name "05": 23 05 2024 Format should be like "Date: 31 Jan 2004" WARNING: No date found! Assuming today. (Hint: Specify the W3C IRC log URL, and the date will be determined from that.) Or specify the date like this: <dbooth> Date: 12 Sep 2002 People with action items: WARNING: Input appears to use implicit continuation lines. You may need the "-implicitContinuations" option. 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]