Re: [i18n-discuss] Text appearance, accessibility, and internationalization (#46)

[On 2025-01-23, @fantasai wrote:](https://github.com/w3c/i18n-discuss/issues/46#issuecomment-2611395964)
> I think you need to be clear that the idea is to accommodate user adjustments up to this amount, not that you're asking for these to be minimum default settings on a website. At first I read it the other way, and that seemed [very weird](https://www.software.hixie.ch/utilities/js/live-dom-viewer/?%3C!DOCTYPE%20html%3E%0A%3Cstyle%3E%20body%20%7B%20display%3A%20flex%3B%20%7D%20p%20%7B%20max-width%3A%2040em%3B%20padding%3A%200.5em%3B%20margin%3A%201em%3B%20border%3A%201px%20solid%20gray%3B%20%7D%3C%2Fstyle%3E%0A%3Cbody%3E%0A%3Cp%3EIn%20our%20discussions%20on%20Text%20Appearance%20and%20accessibility%2C%20much%20of%20the%20discussion%20relates%20to%20what%20recommendations%20and%20standards%20we%20should%20suggest%20to%20ensure%20readability%20and%20flexibility%20for%20text%20presentation.%20This%20includes%20text%20layout%20features%20like%20margins%2C%20line%20spacing%2C%20word%20spacing%2C%20justification%2C%20hyphenation%2C%20line%20breaks%2C%20capitalization%2C%20and%20so%20on.%20We%20realized%20during%20this%20discussion%20that%20we%20don%27t%20have%20enough%20information%20about%20how%20some%20of%20the%20properties%20mentioned%20may%20differ%20or%20have%20nuance%20in%20different%20languages%20or%20scripts.%20We%20did%20discuss%20how%20this%20particular%20area%20was%20not%20addressed%20fully%20in%20WCAG%202%2C%20and%20how%20we%20can%20make%20sure%20we%20avoid%20that%20in%20future.%0A%3Cp%20style%3D%22letter-spacing%3A%200.15em%3B%20word-spacing%3A%200.16em%22%3EIn%20our%20discussions%20on%20Text%20Appearance%20and%20accessibility%2C%20much%20of%20the%20discussion%20relates%20to%20what%20recommendations%20and%20standards%20we%20should%20suggest%20to%20ensure%20readability%20and%20flexibility%20for%20text%20presentation.%20This%20includes%20text%20layout%20features%20like%20margins%2C%20line%20spacing%2C%20word%20spacing%2C%20justification%2C%20hyphenation%2C%20line%20breaks%2C%20capitalization%2C%20and%20so%20on.%20We%20realized%20during%20this%20discussion%20that%20we%20don%27t%20have%20enough%20information%20about%20how%20some%20of%20the%20properties%20mentioned%20may%20differ%20or%20have%20nuance%20in%20different%20languages%20or%20scripts.%20We%20did%20discus.)!
> 
> [...]
> 
> Read as a “make these the default settings on your website” though... I think it wouldn't be fine even in English. :)

This is true for the example SC. However, we're looking into making both 'don't break within these bounds' and readable defaults criteria in WCAG 3. We're particularly looking for input on the defaults, as we know what's considered readable varies across languages, scripts, and cultures.


-- 
GitHub Notification of comment by u9000-Nine
Please view or discuss this issue at https://github.com/w3c/i18n-discuss/issues/46#issuecomment-2619399101 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Tuesday, 28 January 2025 15:54:32 UTC