W3C

– DRAFT –
Internationalization Accessibility Community Group

15 05 2024

Attendees

Present
Frankie, JMcSorley, Katy, Lisa, MURATA, Philipp
Regrets
-
Chair
Jan_McSorley
Scribe
Lisa

Meeting minutes

<JMcSorley> meeting minutes from 05/01/2024: https://docs.google.com/document/d/1TeGEsD1JVf7L9bFW3_e7YTnqtmUnpTldJhD6N16ElAU/edit?usp=sharing

last weeks muinits are at https://docs.google.com/document/d/1TeGEsD1JVf7L9bFW3_e7YTnqtmUnpTldJhD6N16ElAU/edit

Lisa, we also want to use auto captions on zoom so people can use auto translate

discusion on scedule with difficalt of getting people in diffrent sides of the world

Makutos sucgestion on changing the time every 6 month so people can participate somethimes

looking at times survey

none are all green

<JMcSorley> time survey: https://docs.google.com/spreadsheets/d/1UENV2-WYkzdsodaMM2xgSNxVO1K1YG1W6ToHn-wFaYI/edit?usp=sharing

Japan is very important

Option 1: Decide on one meeting time that is convenient for most members and stick with that consistent time for all meetings. One downside to this option is that some members will always be inconvenienced by having to meet at night.

Option 2: Stick to the schedule of two meetings per month, but hold the meeting on the 1st Wednesday of the month at a time that is convenient for people in Europe and hold the meeting on the 2nd Wednesday of the month at a time that is convenient for people in Asia. The same agenda items will be discussed at both meetings. One downside to this

option is that progress will be slowed because the same agenda has to be covered twice in a month. Also, voting might be more complicated

Option 3: Set up chairs in two parts of the world - one set that represents Europe/US and one group that represents Asia/US. The chairs will coordinate with each other to make sure they are covering the same agenda items, but they will hold meetings that are convenient for people in their respective time zones. Notes will be taken in English for

all meetings. One downside to this option is that you would never have a meeting where people from Europe and Asia are in a meeting together and you would have to rely heavily on thorough notes. Also, voting might be more complicated.

Option 4: Switch the meeting time twice a year. For 6 months, the time will be convenient for people in Europe and for 6 months, it will be convenient for people in Asia. The downside for this is that the time would not be consistent, so multiple notices would need to be made to help people understand when the time change would happen.

<JMcSorley> +1 for Option 4

option 4

<Philipp> +1 for Option 4

<MURATA> +1 for Option 4

any objections?

katie also says 4

<JMcSorley> Katy's having trouble with IRC - she voted in Zoom for Option 4

6 month at current time. gives chance to recruit in eu. and then swithch to tokoyo friendly time.

makuto: this is relatively easy compared to other groups

keeping to current time until november

<JMcSorley> Propose meeting at 9:00 a.m. from May - September; November - April will find a different time. Please vote yes/no

+1

<JMcSorley> +1

<MURATA> +1

<Philipp> +1

<JMcSorley> Katy says +1

next item

close item 1

close item 1

<Zakim> Lisa, you wanted to say we should start with a Japan friendly time

<JMcSorley> proposed process for reviewing COGA patterns: https://docs.google.com/document/d/1s_hPZNDHNEfwdS3CZsjki4FBOYx9cqArkYL4x4i8LJM/edit?usp=sharing

next item

close item 1

next item

close item 2

next item

https://docs.google.com/spreadsheets/d/1ARdgFWjFQb2vOEDQkHYu24ociCeRMDF9xQhaMQgW1MA/edit?usp=sharing

spread sheet for content useable , what patterns are problem

everyone gets there own tab

todays minits are at

https://www.w3.org/2024/05/15-global-inclusion-minutes.html Lisa

note coga still has an internationalization subgroup

there was some feedback

https://github.com/w3c/coga/labels/i18n-needs-resolution

<JMcSorley> Lisa: There's a tracker for Internationalization, so if we can find issues that have internationalization concerns in GitHub, we can find their concerns

w3c/coga#310

<JMcSorley> Lisa: COGA members copied issues into a spreadsheet because it was easier for us to work in a spreadsheet than in GitHub, and we thought issues were closed, but they were not

<JMcSorley> Lisa: We just missed some things that were important for internationalization.

<JMcSorley> Lisa: For exampled - with tense, we used language in our guidance that would not work for all languages because we didn't understand those languages, so our guidance should have been more flexible.

<JMcSorley> Lisa: text orientation is also important and we need to address it

<JMcSorley> Lisa: Reviewing patterns in COGA is not going to be enough - we also need to review the objectives.

<JMcSorley> Lisa: We tried to internationalize our personas, but we didn't do a good job - we did not do a good job of reflecting genuine experiences of people in different cultures and geographies.

<JMcSorley> Lisa: We also didn't address non-native speakers who might also have a learning disability

<JMcSorley> Lisa: People may have very different reasons for having difficulty with communication

https://github.com/w3c/coga/labels/i18n-needs-resolution

w3c/coga#310

w3c/coga#162

Jna: talk though the objectives

to get anyhing into wcag, 3.0 we have to have good tests

<Katy> Arabic, Chinese Mandarin, English, Hindi, Russian

<JMcSorley> Lisa: The purpose of coming up with different languages was to help us develop non-normative tests to help people with implementation of COGA recommendations

<JMcSorley> Lisa: We need to add a section in the document on sensitivities to help us understand what may or may not be offensive in different cultures

and also sensitivities for coga and mental health

Jan- will add to our main google docs

getting started

and add links to all our other docs there as well

Jan: should it be in googledocs or on the wiki ?

or both

katie: just one

philliep: one place - wiki is more findable

mukoto likes github, but others might not like it

Jan: comunity wiki seems good place for people to find

Phili: if we use googledocs make sure it is indexed on the wiki

Jna: draft document

<JMcSorley> draft purpose doc: https://docs.google.com/document/d/1SgfzQMEd0MYydz6WoPBbuxx5CewjiUc5bsuu592uurI/edit?usp=sharing

pourpose doc

first attemp but we can change it, depends on the vote

next call 1st june

5th june

please review beofre hand

lisa: action draft page for recuring with draft email

Minutes manually created (not a transcript), formatted by scribe.perl version 221 (Fri Jul 21 14:01:30 2023 UTC).

Diagnostics

Maybe present: Jan, Jna, katie, makuto, Phili, philliep

All speakers: Jan, Jna, katie, lisa, makuto, Phili, philliep

Active on IRC: Frankie, JMcSorley, Katy, Lisa, MURATA, Philipp