12:54:55 RRSAgent has joined #global-inclusion 12:54:59 logging to https://www.w3.org/2024/06/05-global-inclusion-irc 12:54:59 RRSAgent, make logs Public 12:55:00 please title this meeting ("meeting: ..."), JMcSorley 12:55:07 chair: Jan_McSorley 12:55:38 Meeting: International Accessibility Community Group 12:55:50 date: 05 06 2024 12:56:02 zakim, clear agenda 12:56:02 agenda cleared 12:56:51 Agenda+ Review May 15, 2024 meeting minutes: https://www.w3.org/2024/05/15-global-inclusion-minutes.html 12:57:16 Agenda+ Review Survey results for the short name of the community group. 12:57:38 Agenda+ Discuss ideas for recruiting. 12:58:20 Agenda+ Review the draft description and mission of the group and discuss the process for turning this into a group charter: https://docs.google.com/document/d/1SgfzQMEd0MYydz6WoPBbuxx5CewjiUc5bsuu592uurI/edit?usp=sharing 12:58:27 present+ JMcSorley 13:00:11 KatyB has joined #global-inclusion 13:00:29 kirkwood has joined #global-inclusion 13:00:59 Philipp has joined #global-inclusion 13:02:39 Makoto has joined #global-inclusion 13:02:51 present+ 13:02:56 present+ 13:03:14 google doc from before: https://docs.google.com/document/d/1TeGEsD1JVf7L9bFW3_e7YTnqtmUnpTldJhD6N16ElAU/edit?pli=1#heading=h.6vl9v53q0fa2 13:04:29 Rachael has joined #global-inclusion 13:05:00 zakim, next item 13:05:00 agendum 1 -- Review May 15, 2024 meeting minutes: https://www.w3.org/2024/05/15-global-inclusion-minutes.html -- taken up [from JMcSorley] 13:06:43 julierawe3 has joined #global-inclusion 13:06:54 present+ 13:07:07 scribe+ Julie 13:07:30 present+ 13:07:59 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 13:08:45 Jan: In the last meeting Lisa described how we landed on doing tests in 5 languages, in collaboration with the internationalization group. 13:08:56 present+ 13:09:00 Jan: We also decided we need to come up with a way to include other languages 13:09:25 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. 13:09:59 Jan: We want people with different language and cultural experiences. We also want people who care about this topic and want to contribute. 13:10:45 Jan: We shared a spreadsheet of all the patterns in Making Content Usable for People with Cognitive and Learning Disabilities. 13:11:18 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. 13:11:51 zakim, next item 13:11:51 I see a speaker queue remaining and respectfully decline to close this agendum, JMcSorley 13:11:57 Q+ 13:12:27 ack Lisa 13:12:35 q? 13:12:45 ack JMcSorley 13:12:53 Frankie has joined #global-inclusion 13:12:55 zakim, next item 13:12:55 agendum 2 -- Review Survey results for the short name of the community group. -- taken up [from JMcSorley] 13:13:00 present+ 13:13:36 Jan: We did a survey to help decide whether to change the short name for this group from "Global Inclusion" to something else 13:13:47 Jan: We also surveyed people about possible meeting times 13:15:29 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 13:16:29 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" 13:17:40 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 13:18:25 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 13:19:01 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 13:20:22 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 13:20:43 q? 13:20:44 Jan: We'll see how that works for us 13:20:53 zakim, next item 13:20:53 agendum 3 -- Discuss ideas for recruiting. -- taken up [from JMcSorley] 13:21:53 Jan: We will talk later today about the wording in our charter 13:22:14 Jan: We want to have representatives from three groups: COGA, AG and internationalization 13:22:51 Jan: The group will help with WCAG 3, which is a long ways off. 13:23:15 Jan thanked Julie for LinkedIn post summarizing where we are with WCAG 3 in general 13:23:32 Philipp has joined #global-inclusion 13:23:47 Jan: I saw Makoto comment on things that will have language-related issues for AGWG and we appreciate having that advice 13:24:04 q+ 13:24:17 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 13:25:07 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 13:25:11 q- 13:25:48 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 13:26:42 Makoto: I've tried to invite some colleagues in the Japan DAISY consortium 13:26:58 Jan: I will look at the community group to see if they have joined 13:27:26 Makoto: I don't expect them to participate in teleconferences because of the language barrier 13:28:00 Philipp: I will ask at the next XLE Tokyo monthly meetup for volunteers 13:28:25 https://a11ytyo.connpass.com 13:28:43 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] 13:28:45 Jan: Both of you mentioned the language barrier because this meeting is in English 13:28:50 q+ 13:29:02 q+ 13:29:32 q+ 13:29:36 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 13:29:56 Jan: I think if we plan ahead, we can address the language barrier so it doesn't keep people away 13:30:02 John K: That sounds good to me 13:30:38 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. 13:30:57 John K: As I recall, it was on their devices rather than through enterprise software 13:31:43 +q 13:33:16 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. 13:33:23 Jan: I will follow-up about that. 13:33:56 John K: Don't be afraid to use AI to blast out invitations on social media in different languages. 13:34:09 q+ 13:34:41 q- 13:34:43 julierawe3 sorry its "a11y Tokyo meetup". thank you 13:34:46 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. 13:35:09 Makoto: I am now using auto-captions in this meeting, which is very helpful. 13:35:32 A11y Seattle: https://www.meetup.com/a11ysea/ 13:35:42 Makoto: I think if some people are very interested, auto-captions will help. 13:36:01 Makoto: Communication in Github is very easy because you can write everything rather than speaking and listening. 13:36:11 Makoto: Encouraging non-oral communication is easier. 13:37:10 also: https://www.meetup.com/a11ytokyo/ 13:38:01 Julie: Has anyone reached out to the language-specific groups at W3C? 13:38:18 should we create a spreadsheet of groups? 13:39:06 Makoto: The internationalization group already has several subgroups. For example, Japanese task force. Also for Korean, Chinese, Hindi. Lots of groups. 13:39:22 Makoto: Some groups are very active, have multiple meetings a month. Some groups are less active. 13:39:46 Makoto: These groups are for requirement documents and provide useful feedback to internationalization. 13:39:53 Makoto: We want to mimic that success. 13:40:21 Jan: So the internationalization working group has language groups that meet separately and provide feedback back to the main internationalization working group? 13:40:24 q? 13:40:26 Makoto: Yes 13:40:28 q+ 13:41:37 Julie: Can we work with these groups directly? Hoping we don't need to set up parallel groups 13:42:01 https://www.w3.org/International/clreq/charter/ 13:42:11 https://www.w3.org/groups/tf/i18n-jlreq/ 13:42:35 Makoto: You might want to count on existing task forces 13:42:49 Makoto: However, most members are not experts on accessibility. 13:43:13 Jan: Would it be helpful when we ask them for feedback to give explanation for why this section of text was recommended? 13:43:15 q+ 13:44:17 Makoto has joined #global-inclusion 13:44:26 present+ 13:45:19 q? 13:45:25 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 13:45:29 q- 13:45:35 ack Makoto 13:45:41 Jan: Some of the patterns involve cultural differences such as use of color 13:46:09 Survey on which Outcomes need internationalization subgroup engagement https://www.w3.org/2002/09/wbs/35422/internationalization_outcomes 13:46:10 Rachael: It would helpful from my perspect on which WCAG outcomes we should engage this community group 13:46:23 https://www.w3.org/groups/tf/i18n-mlreq/ 13:46:35 https://www.w3.org/groups/tf/iip/ 13:46:43 https://www.w3.org/groups/tf/i18n-hlreq/ 13:46:57 https://www.w3.org/groups/tf/i18n-elreq/ 13:47:09 Rachael: We can help share those outcomes with those language groups 13:47:30 ]https://www.w3.org/groups/tf/i18n-sealreq/ 13:47:37 https://www.w3.org/groups/tf/i18n-tlreq/ 13:48:14 https://www.w3.org/groups/tf/i18n-afrlreq/ 13:48:25 https://www.w3.org/groups/tf/i18n-alreq/ 13:50:06 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 13:50:13 q? 13:50:40 Julie: Just wanted to flag that some of the entries in the survey are not easy to understand 13:50:43 q- 13:51:04 Jan: I think Julie is going to have the perspective of all three of these groups 13:51:14 If it's more helpful for the group to go through it together in a future meeting, that would also work. 13:51:17 I am sharing the easy language networks here for future reference: https://www.linkedin.com/groups/12970417/ and https://www.facebook.com/ELINnetwork/ 13:51:20 Jan: Our first task is deciding what our charter is going to be 13:51:28 q+ 13:52:45 I am unhappy with the current section. 13:54:01 q+ 13:54:26 https://www.w3.org/TR/WCAG22/#visual-presentation 13:55:24 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 13:55:35 Makoto great points! 13:55:51 Makoto pointed out several outcomes that are biased for non-vertical languages 13:56:07 Makoto The first goal is to eliminate what is harmful for all languages 13:56:08 q+ 13:56:42 Makoto: Things that involve line spacing, paragraph spacing, line height that might not be applicable to the whole world 13:57:11 Rachael: In WCAG 2.2, we attempted to address those in collaboration with the internationalization working group 13:57:18 Rachael: We want to get it right. 13:59:34 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. 13:59:45 Makoto: It's not possible to go through for all languages in the world. 14:00:17 Makoto: It's not impossible in Japanese, but in Mongolian, I don't know anything about Mongolian language. 14:00:25 Excel sheet for future use https://docs.google.com/spreadsheets/d/1MVNJiibdvaVbdWv452fAbDw1s7pwNmDy_YpQzZWJwwU/edit?usp=sharing 14:00:46 heee hee argh i just finished it. oops 14:01:09 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 14:02:02 Julie: I think the first step is to flag problems and then see how we can adjust the guidance so it's not harmful 14:02:21 Jan: Next time we will look at the Making Content Usable patterns 14:02:34 Jan: If Rachael can share spreadsheet, I will share it with the group 14:03:18 Jan: I can send guidance in a few days on how to fill those out 14:03:34 rrsagent, make minutes 14:03:35 I have made the request to generate https://www.w3.org/2024/06/05-global-inclusion-minutes.html julierawe3 14:33:59 JMcSorley has joined #global-inclusion 14:34:06 zakim, end meeting 14:34:06 As of this point the attendees have been MURATA, JMcSorley, Frankie, Katy, Makoto, KatyB, julierawe, Philipp, kirkwood 14:34:08 RRSAgent, please draft minutes 14:34:09 I have made the request to generate https://www.w3.org/2024/06/05-global-inclusion-minutes.html Zakim 14:34:15 I am happy to have been of service, JMcSorley; please remember to excuse RRSAgent. Goodbye 14:34:16 Zakim has left #global-inclusion 14:34:29 rrsagent, bye 14:34:29 I see no action items