-
Notifications
You must be signed in to change notification settings - Fork 55
Adapting Text: font-family #389
Comments
Yes, internationalization is one reason that font family is likely not to be included in the final version of this SC. However, the testability issue relates to being too wide or too narrow with the font to test, and the latter leads to internationalization concerns. Ultimately though, it is up to the user making the adaptations to be sensitive to language when selecting their fonts (e.g. by having separate selectors in a custom stylesheet). |
To elaborate on what @steverep is saying, if the SC makes it an author requirement not to interfere with a user's ability to override the author settings for text attributes, then the author can't be responsible if the user makes a 'poor' decision. If colour was included in this SC and a user chose white text on an almost white background, nothing will be viewable; but that is the user's choice, not the author's responsibility. |
Thank you for your comment. The WG decided to remove the font family bullet from the SC per Issue #153. |
Success Criterion 1.4.13 Adapting Text
https://www.w3.org/TR/WCAG21/#adapting-text
Font-family adaptations would need to be sensitive to language changes. A page containing text in both english and hindi would not necessarily become more readable if a user-defined english font was applied to all the hindi text too (and vice versa).
The text was updated successfully, but these errors were encountered: