Reminder: September 10, 2025 - Internationalization Accessibility Community Group Meeting

Hi everyone.

My apologies for the very late reminder notice. Our next meeting is
tomorrow, Wednesday, *September 10, 2025* at the following time:

UTC NY EST
UTC -4 London
UTC +1 CEST
UTC +2 Jerusalem
UTC +3 Delhi / IST
UTC +5:30 Tokyo
UTC +9
13:00:00 9:00 AM 2:00 PM 3:00 PM 4:00 PM 6:30 PM 10:00 PM

*Agenda:*

   -

   - Review Version 2 Pattern Drafts
   <https://docs.google.com/document/d/1pnaq0fVSLsYDmrC_kpBkvE5fRALe2Jfo0Ff5H3azXcY/edit?usp=sharing>
   .
   - Review the definition of Internationalization and Localization
   <https://deploy-preview-762--i18n-drafts.netlify.app/questions/qa-i18n.en.html>
   provided by the Internationalization Working Group. “In a nutshell:
   Designers and developers internationalise products, so that they can be
   easily localised by translators and localisers.”
   - Review Script Comparison Table
   <https://r12a.github.io/scripts/script-features/>, provided by Richard
   Ishida from the Internationalization Working Group. Determine if this might
   meet the need we were targeting with our tables.
      - Richard’s feedback on our alternative table: “In the 'alternative
      table' i'm not clear about why diacritics are called out (and why
      cedillas are on a separate line).  It seems to me that the
primary function
      is less important than accessibility issues such as whether they are
      legible (or in some cases even present), whether they should or
should not
      be included in search keys, etc.  Note, btw, that Thai tone
marks, etc, are
      also a type of diacritic.  The table doesn't appear to have a clear
      objective, since it mixes rows related to diacritics with rows related to
      script types.”
   - Consider making a user story for "Cognitive Accessibility Issue Papers
   - Voice Systems and Conversational Interfaces
   <https://docs.google.com/document/d/1B1vCqlU1IF5UmqxhJAy8Khdi-kRQNPalVX8f3lCMr7w/edit?usp=sharing>"
   that addresses localization and internationalization - using “Care
   Management” vs. “Healthcare Management” as an example. Will need to draft
   the user story in a different document.
   - Review the tables under the Action Items heading
   <https://docs.google.com/document/d/1TeGEsD1JVf7L9bFW3_e7YTnqtmUnpTldJhD6N16ElAU/edit?tab=t.0#heading=h.tkl2miatc2i4>
   from our July 30, 2025 meeting. These tables will help provide feedback on
   proposed guidance and help inform testing considerations for different
   languages - please check Julie Rawe’s comment in the July Tab
   <https://docs.google.com/document/d/1Q3eVdTVfErkeXMukdiNVRC1MgIDMv_2FrgJ_62silfE/edit?tab=t.7qp43a3keop#heading=h.7crn40hv0nhj>
   in response to the question about whether a table would help.


*Meeting Minutes - Google Doc Version*
<https://docs.google.com/document/d/1TeGEsD1JVf7L9bFW3_e7YTnqtmUnpTldJhD6N16ElAU/edit?usp=sharing>

*Join the Meeting
<https://us06web.zoom.us/j/3436291299?pwd=OC9WbjZPZEdLUEgxSXRyaUFzUTlIUT09>*

Connect to the *IRC Channel*
<https://webirc.w3.org/#/connect?channels=global-inclusion>

Please let me know if you would like to have time on the agenda for any
other topics. I look forward to talking with all of you!

Many thanks,

*Jan McSorley*
*Accessibility Consultant*
*512-731-7957 (mobile)*
linkedin.com/in/janmcsorley <https://www.linkedin.com/in/janmcsorley>
@jmcsorle.bsky.social

*We put a man on the moon in the 1960's. Surely we can make information
technology fully accessible to people with disabilities. It can be done. It
must be done. It will be done!*