W3C

– DRAFT –
Internationalization Accessibility Community Group (global-inclusion)

23 04 2025

Attendees

Present
andy, chiace, Jan, Jean, Philipp, present
Regrets
Frankie
Chair
Jan_McSorley
Scribe
Jan

Meeting minutes

<Makoto> +present

https://docs.google.com/document/d/1GwIadQU2rmDwqPDeYX6PF7UjnD4D47vqRjvPysXNe-A/edit?usp=sharing

Review structure research

Philipp: As a person with dyslexia, having words repeated, makes it more difficult to scan. Nothing stands out when you use "make" and "use" repeatedly.

JohnK: Yes, we might be using lazy writing. Something like "Design the page to be clear." We need more thought in the action verb to differentiate (design or organize).

Andy: As long as we don't just repeat new words.

Andy: Some languages only have one word for "make" and would not be used as this is intended in the current wording.

https://docs.google.com/document/d/1GwIadQU2rmDwqPDeYX6PF7UjnD4D47vqRjvPysXNe-A/edit?usp=sharing

Regarding the compromise of making higher-level headings be formatted as an outcome (e.g. "Design is Clear" - h3), this is a good compromise that supports scanning and way finding, as long as these headings are worded in this way and not as one or two-word headings without a description. With one or two-word headings, if you have to read an entire

bulleted list to understand what the heading means, then that causes problems with international audiences. Writing lower-level headings in active voice ("Make the purpose of the page clear." - h5) is good if you don't repeat the action words so that they appear to be filler. Use something like "Design the page to be clear." If you agree with this,

please put +1, if you disagree -1, if you think this needs additional discussion, please enter 0.

<Jan> +1

<Philipp> +1

<chiace> +1

<andy> +1

<Jean> +1

<kirkwood> +1

<kirkwood> from an internationalization perspective

<kirkwood> Regarding the compromise of making higher-level headings be formatted as an outcome (e.g. "Design is Clear" - h3), this is a good compromise that supports scanning and way finding, as long as these headings are worded in this way and not as one or two-word headings without a description. With one or two-word headings, if you have to read an entire

<kirkwood> [09:57am] Jan: bulleted list to understand what the heading means, then that causes problems with international audiences. Writing lower-level headings in active voice ("Make the purpose of the page clear." - h5) is good if you don't repeat the action words so that they appear to be filler. Use something like "Design the page to be clear." If you agree with this,

<kirkwood> my thoughts

<kirkwood> Using higher-level headings formatted as outcomes (e.g., "Design is Clear" as an H3) is a strong compromise that supports both scanning and wayfinding. However, it's important that these headings are phrased as complete outcomes, not just one- or two-word labels. Short, vague headings often require users to read the entire bulleted list to understand the context, which can be especially problematic for international audiences. For lo[CUT]

<kirkwood> headings, use active voice (e.g., "Make the purpose of the page clear") to communicate intent clearly and directly.

Minutes manually created (not a transcript), formatted by scribe.perl version 244 (Thu Feb 27 01:23:09 2025 UTC).

Diagnostics

No scribenick or scribe found. Guessed: Jan

Maybe present: JohnK

All speakers: Andy, JohnK, Philipp

Active on IRC: andy, chiace, Jan, Jean, kirkwood, Makoto, Philipp