Meeting minutes
Review the following i18n resources: Internationalization Best Practice for Spec Developers (https://www.w3.org/TR/international-specs/ ); Short i18n review checklist (https://www.w3.org/International/i18n-drafts/techniques/shortchecklist )
short version of i18n guidance: https://
longer version of i18n guidance: https://
Philipp: Where are all of the W3C resources? Is there a place where all accessibility-related specifications are centralized.
Lisa wants the community group to note new patterns that we identify as we review the internationalization guidance.
There are questions about what happened with the Education and Outreach working group. Philipp was hoping they could create an index of all W3C guidance, resources, community groups, etc. There are too many guidance documents that exist and it's difficult to find them.
Andy: search by itself is not sufficient because you may not even know what to look for.
Jan and Andy will dig into this and try to find some answers on whether this exists and if not, we will try to find links to important resources that affect the work of this group.
Andy: A page on the W3C website that everyone could favorite that would list all of the groups.
Consolidate feedback from homework on patterns in Objectives 1, 2, and 5 in the Content Usable Pattern Feedback Document: https://docs.google.com/spreadsheets/d/1ARdgFWjFQb2vOEDQkHYu24ociCeRMDF9xQhaMQgW1MA/edit?usp=sharing
Andy and Philipp: We need to come up with different feedback on the examples and stop pointing out older people so often - this contributes to ageism.
Andy and Philipp: There is some confusion for people who are not native English speakers when longer sentences are used.
Andy and Philipp: There seems to be a disregard for screen reader users - there is a lot of use of "click here"
Philipp: the recommendation of using emojis is not helpful for screen readers - the description of these can be really long, so when you put them at the beginning of a line, it adds a lot of verbosity. A lot of younger designers often use emojis as bullets.
Philipp: Directionality - we need to give up on directionality because of vertical languages - some of the examples need to be redone with other scripts - there are also some problems with how they describe languages.
Andy: COGA uses terms that are not easy to translate or understand - like "move on" - you think that something is moving - we need to use the primary definition of words.
Andy's rewrites are through AI and Philipp's rewrites are more organic
Jan will copy over their rewrites into our consolidated spreadsheet.
Andy: Some of the bullets had commas behind them - it makes it hard to read.
Assign the following Homework: Review Patterns for Objectives 3 and 4 in the Content Usable Pattern Feedback Document - https://docs.google.com/spreadsheets/d/1ARdgFWjFQb2vOEDQkHYu24ociCeRMDF9xQhaMQgW1MA/edit?usp=sharing
4.2.1 - Don't use "move on" - needs to be reworded
4.2.2 - Need an alternative to "sign post" - consider how to not use "left-to-right" - make this more international - needs to be reworded
4.2.3 - Needs to be rewritten - missing commas makes the first sentence confusing; examples need to include non-Roman alphabet scripts; need to add "sensitivity review" and "greater diversity" to the drop down;
4.2.4 - Andy and Philipp both have suggested rewrites
4.2.5 - rewrites available from Andy and Philipp - replace "click" and don't perpetuate ageism - needs sensitivity review
4.2.6 - rewrites available from Andy and Philipp - questioning the use of "unambiguous" - suggest removing. Changed the person to ADHD to avoid ageism
4.2.7 - Philipp has a lot of feedback on icons - we need to include emojis because emojis are often used for bullets - Andy has rewrite suggestions
4.3.1 - This is another example of "move on" being used. Remove ageism and add directions; (John) we need to remember that we may need to point out how these can help aging communities- we could maybe word them differently, rather than eliminating it. (Philipp) we need to have additional examples so that people who are old are not the only
examples.
4.3.4 - Andy has rewrite examples from AI
4.3.6 - "friendly" is an ambiguous word - "capability" is hard to understand. Sentences should be shortened.
4.6.1 - Andy has an AI rewrite. Be inclusive of people with limited target language skills (target language is defined as the language that it is interpreted into) - native language is not an effective term because of how mobile people are - they may not be fluent in their "native" language because their "first" language might be different.
4.6.2 - Andy has a rewrite - still stumbled over the last bullet, which used techical language - "run the most used function" under "avoid"
• rrsagent, generate minutes