Skip to content
This repository has been archived by the owner on Jun 30, 2018. It is now read-only.

Adapting Text: font-family #389

Closed
r12a opened this issue Sep 21, 2017 · 3 comments
Closed

Adapting Text: font-family #389

r12a opened this issue Sep 21, 2017 · 3 comments

Comments

@r12a
Copy link

r12a commented Sep 21, 2017

Success Criterion 1.4.13 Adapting Text
https://www.w3.org/TR/WCAG21/#adapting-text

If the technologies being used allow the user agent to adapt style properties of text, then no loss of essential content or functionality occurs by adapting all of the following: ...
The Working Group seeks to include overriding text color, background color, and font-family

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).

@steverep
Copy link
Member

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).

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).

@mbgower
Copy link
Contributor

mbgower commented Sep 22, 2017

if a user-defined english font was applied to all the hindi text too

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.
Trying to find language that improves user experience, makes responsibilities clear and provides consistent testable results for failures is the challenge.
The text properties specified in the current language (line height, letter spacing, word spacing, space after paragraphs) are measurable, are believed to be achievable, and have been shown to have positive impact on certain user bases.

@awkawk
Copy link
Member

awkawk commented Nov 30, 2017

Thank you for your comment.

The WG decided to remove the font family bullet from the SC per Issue #153.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

5 participants