– DRAFT –
International Accessibility Community Group

<Philipp> google doc from before: https://docs.google.com/document/d/1TeGEsD1JVf7L9bFW3_e7YTnqtmUnpTldJhD6N16ElAU/edit?pli=1#heading=h.6vl9v53q0fa2

Review May 15, 2024 meeting minutes: https://www.w3.org/2024/05/15-global-inclusion-minutes.html

<julierawe3> Jan: In the last meeting we decided to do the same meeting time for 6 months and then to switch for the next six months

<julierawe3> Jan: In the last meeting Lisa described how we landed on doing tests in 5 languages, in collaboration with the internationalization group.

<julierawe3> Jan: We also decided we need to come up with a way to include other languages

<julierawe3> Jan: Lisa and I talked after the meeting about trying as a group to come up with a way to appeal to people when recruiting new members.

<julierawe3> Jan: We want people with different language and cultural experiences. We also want people who care about this topic and want to contribute.

<julierawe3> Jan: We shared a spreadsheet of all the patterns in Making Content Usable for People with Cognitive and Learning Disabilities.

<julierawe3> We will not discuss the spreadsheet today but we'll focus on it at the next meeting. We need a plan to prioritize which patterns we need to focus on.

Review Survey results for the short name of the community group.

<julierawe3> Jan: We did a survey to help decide whether to change the short name for this group from "Global Inclusion" to something else

<julierawe3> Jan: We also surveyed people about possible meeting times

<julierawe3> Jan: 4 people ranked "Global Inclusion" as their first choice, no one said they don't want the name, so we're sticking with this short name

<julierawe3> Jan: For meeting times, 5 people said they don't mind current time, one person ranked as first choice, and no one said "don't want"

<julierawe3> Jan: For second suggestion (to have switch times every other meeting), 3 voted against, one said didn't mind and one ranked as 1st choice

<julierawe3> For third option (to set up two meetings in two parts of the world and use same agenda), 3 said they didn't mind, 1 said didn't want, and one chose as 2nd choice

<julierawe3> For last option (switch the meeting time twice a year), 5 said they don't mind, one said don't want, and one chose as first option

<julierawe3> Jan: Based on this survey, we're going to switch the time every six months so it's convenient for people in Europe half the year and convenient for people in Asia for half the year

<julierawe3> Jan: We'll see how that works for us

Discuss ideas for recruiting.

<julierawe3> Jan: We will talk later today about the wording in our charter

<julierawe3> Jan: We want to have representatives from three groups: COGA, AG and internationalization

<julierawe3> Jan: The group will help with WCAG 3, which is a long ways off.

<julierawe3> Jan thanked Julie for LinkedIn post summarizing where we are with WCAG 3 in general

<julierawe3> Jan: I saw Makoto comment on things that will have language-related issues for AGWG and we appreciate having that advice

<julierawe3> Jan: We will start by looking at Making Content Usable patterns and we hope to get requests soon from AGWG for helping with WCAG and internationalization

<julierawe3> Jan: Let's brainstorm on how to recruit so we have diverse representation in terms of language experience, people with disabilities, people who work in accessility

<julierawe3> Katy: I was contacted by someone in Scotland who is trying to set up another Easy Read network. I invited her to join this group. I can also share the invite to other people in that network as well, including Australia and elswhere

<julierawe3> Makoto: I've tried to invite some colleagues in the Japan DAISY consortium

<julierawe3> Jan: I will look at the community group to see if they have joined

<julierawe3> Makoto: I don't expect them to participate in teleconferences because of the language barrier

<julierawe3> Philipp: I will ask at the next XLE Tokyo monthly meetup for volunteers

<Philipp> https://a11ytyo.connpass.com

<kirkwood> use/ask AI to write a compelling email to recruit members for internationalizing cognitive accessibility to [this is for a post and email blast language]

<julierawe3> Jan: Both of you mentioned the language barrier because this meeting is in English

<julierawe3> Jan: I wonder if it would help to identify members' languages and get liaisons so we can hold separate meetings once a month in those languages so get some of the tasks done

<julierawe3> Jan: I think if we plan ahead, we can address the language barrier so it doesn't keep people away

<julierawe3> John K: That sounds good to me

<julierawe3> John K: Having dealt with internationalization a lot with the Department of Education, we used some tools. Microsoft has tools that do real-time translation into seven languages.

<julierawe3> John K: As I recall, it was on their devices rather than through enterprise software

<julierawe3> Julie: I believe W3C has a real-time translation tool that could help people attend the full-group meetings. I also like Jan's idea of having some separate language-specific meetings to get language-specific tasks done.

<julierawe3> Jan: I will follow-up about that.

<julierawe3> John K: Don't be afraid to use AI to blast out invitations on social media in different languages.

<Philipp> julierawe3 sorry its "a11y Tokyo meetup". thank you

<julierawe3> Frankie: The A11y Seattle group is restarting after a long hiatus because of COVID. There's tons of folks in the Seattle area working in this space. I will try to recruit some of those people.

<julierawe3> Makoto: I am now using auto-captions in this meeting, which is very helpful.

<Frankie> A11y Seattle: https://www.meetup.com/a11ysea/

<julierawe3> Makoto: I think if some people are very interested, auto-captions will help.

<julierawe3> Makoto: Communication in Github is very easy because you can write everything rather than speaking and listening.

<julierawe3> Makoto: Encouraging non-oral communication is easier.

<Philipp> also: https://www.meetup.com/a11ytokyo/

<julierawe3> Julie: Has anyone reached out to the language-specific groups at W3C?

<kirkwood> should we create a spreadsheet of groups?

<julierawe3> Makoto: The internationalization group already has several subgroups. For example, Japanese task force. Also for Korean, Chinese, Hindi. Lots of groups.

<julierawe3> Makoto: Some groups are very active, have multiple meetings a month. Some groups are less active.

<julierawe3> Makoto: These groups are for requirement documents and provide useful feedback to internationalization.

<julierawe3> Makoto: We want to mimic that success.

<julierawe3> Jan: So the internationalization working group has language groups that meet separately and provide feedback back to the main internationalization working group?

<julierawe3> Makoto: Yes

<julierawe3> Julie: Can we work with these groups directly? Hoping we don't need to set up parallel groups

<Philipp> https://www.w3.org/International/clreq/charter/

<Philipp> https://www.w3.org/groups/tf/i18n-jlreq/

<julierawe3> Makoto: You might want to count on existing task forces

<julierawe3> Makoto: However, most members are not experts on accessibility.

<julierawe3> Jan: Would it be helpful when we ask them for feedback to give explanation for why this section of text was recommended?

<julierawe3> Julie: We would not need them to be experts on accessibility. We would explain why the pattern or outcome is important and get their feedback on whether the pattern or outcome would work in their language or if it needs adjusting

<julierawe3> Jan: Some of the patterns involve cultural differences such as use of color

<Rachael> Survey on which Outcomes need internationalization subgroup engagement https://www.w3.org/2002/09/wbs/35422/internationalization_outcomes

<julierawe3> Rachael: It would helpful from my perspect on which WCAG outcomes we should engage this community group

<Makoto> https://www.w3.org/groups/tf/i18n-mlreq/

<Makoto> https://www.w3.org/groups/tf/iip/

<Makoto> https://www.w3.org/groups/tf/i18n-hlreq/

<Makoto> https://www.w3.org/groups/tf/i18n-elreq/

<julierawe3> Rachael: We can help share those outcomes with those language groups

<Makoto> ]https://www.w3.org/groups/tf/i18n-sealreq/

<Makoto> https://www.w3.org/groups/tf/i18n-tlreq/

<Makoto> https://www.w3.org/groups/tf/i18n-afrlreq/

<Makoto> https://www.w3.org/groups/tf/i18n-alreq/

<julierawe3> Correction: Rachael would use our survey results about which outcomes involve internationalization to help keep us in the loop about when those outcomes are being worked on

<julierawe3> Julie: Just wanted to flag that some of the entries in the survey are not easy to understand

<julierawe3> Jan: I think Julie is going to have the perspective of all three of these groups

<Rachael> If it's more helpful for the group to go through it together in a future meeting, that would also work.

<KatyB> I am sharing the easy language networks here for future reference: https://www.linkedin.com/groups/12970417/ and https://www.facebook.com/ELINnetwork/

<julierawe3> Jan: Our first task is deciding what our charter is going to be

<Makoto> I am unhappy with the current section.

<Makoto> https://www.w3.org/TR/WCAG22/#visual-presentation

<julierawe3> Julie: Possible for Rachael to create version of the survey that puts in the first section all the wording and text appearance outcomes and puts everything else in the second section and makes clear it's OK if you aren't sure whether this second bucket requires internationalization

<Philipp> Makoto great points!

<julierawe3> Makoto pointed out several outcomes that are biased for non-vertical languages

<julierawe3> Makoto The first goal is to eliminate what is harmful for all languages

<julierawe3> Makoto: Things that involve line spacing, paragraph spacing, line height that might not be applicable to the whole world

<julierawe3> Rachael: In WCAG 2.2, we attempted to address those in collaboration with the internationalization working group

<julierawe3> Rachael: We want to get it right.

<julierawe3> Rachael: It would be time-consuming to adjust the survey. It would be easier to give you a spreadsheet so you can go through section by section.

<julierawe3> Makoto: It's not possible to go through for all languages in the world.

<julierawe3> Makoto: It's not impossible in Japanese, but in Mongolian, I don't know anything about Mongolian language.

<Rachael> Excel sheet for future use https://docs.google.com/spreadsheets/d/1MVNJiibdvaVbdWv452fAbDw1s7pwNmDy_YpQzZWJwwU/edit?usp=sharing

<kirkwood> heee hee argh i just finished it. oops

<julierawe3> Makoto: I would like WCAG 3 to be more abstract so they work for more languages and avoid things that might be dangerous for some languages

<julierawe3> Julie: I think the first step is to flag problems and then see how we can adjust the guidance so it's not harmful

<julierawe3> Jan: Next time we will look at the Making Content Usable patterns

<julierawe3> Jan: If Rachael can share spreadsheet, I will share it with the group

<julierawe3> Jan: I can send guidance in a few days on how to fill those out