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

Microsoft Comments on Adapting Text #186

Closed
alliMSFT opened this issue Mar 30, 2017 · 5 comments
Closed

Microsoft Comments on Adapting Text #186

alliMSFT opened this issue Mar 30, 2017 · 5 comments
Assignees
Labels

Comments

@alliMSFT
Copy link

Implementable:

a. This SC is more suitable for the browsers than for content authors. As long as desktop browsers has the functionality, I think this is an unnecessary requirement for content authors.

b. Note that this does not work for mobile browsers today. But that is not the fault of content authors. Given that, it is better to not put the load on content authors.

  1. Clarity of Text:

a. The SC is about text as the title and SC suggest. But it is not scoped to text content as it is currently structured. As such, one can mistakenly think that it applies to images of text. Please scope this SC properly.

@WayneEDick
Copy link
Contributor

WayneEDick commented Mar 30, 2017 via email

@alastc
Copy link
Contributor

alastc commented Apr 3, 2017

a. This SC is more suitable for the browsers than for content authors. As long as desktop browsers has the functionality, I think this is an unnecessary requirement for content authors.

This is not the case, at least not to the extent needed for support. You can apply these settings via a browser (some in settings, some need an extension or bookmarklet), but there are various things authors can do to prevent those from taking effect in a meaningful way.

The aim is that authors use techniques that allow for adaptation, so whilst the test is to apply adaptations, the techniques are things for authors.

b. Note that this does not work for mobile browsers today. But that is not the fault of content authors. Given that, it is better to not put the load on content authors.

This can be applied in mobile browsers, it is more limited but it is possible for some sites using bookmarklets. Also, the techniques should align with things that help 'reader mode' in safari. (I assume there are equivalents on android.)

Also, should we deny people with low vision this possibility on desktop because mobile doesn't support it? (As well.) The techniques & failures will all be about the content, not the device used.

As such, one can mistakenly think that it applies to images of text.

There is an exception for that, probably added after you looked:

Captions and images of text are exempt.

@mraccess77
Copy link

It is my view that there are things the author can do to break this such as using fixed sized containers that hide overflowed content. So this goes beyond what the browser can overcome.

@lauracarlson
Copy link
Contributor

lauracarlson commented Jul 21, 2017

Hi @alexswli ,

Alex wrote:

Implementable:

a. This SC is more suitable for the browsers than for content authors. As long as desktop browsers has the functionality, I think this is an unnecessary requirement for content authors.

b. Note that this does not work for mobile browsers today. But that is not the fault of content authors. Given that, it is better to not put the load on content authors.

  1. Clarity of Text:

a. The SC is about text as the title and SC suggest. But it is not scoped to text content as it is currently structured. As such, one can mistakenly think that it applies to images of text. Please scope this SC properly.

Thank you for your comment.

The latest SC text, which the AG Working Group has agreed to accept into editors draft for public comment is:

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:

  1. line height (line spacing) to at least 1.5 times the font size
  2. spacing underneath paragraphs to at least 2 times the font size
  3. letter spacing (tracking) to at least 0.12 times the font size
  4. word spacing to at least 0.16 times the font size

Note: Examples of text that are typically not affected by style properties are open captions and images of text, which are not expected to adapt.

Editor's note: The Working Group seeks to include overriding text color, background color, and font-family as part of this SC, but is not yet able to identify a way to do so that is sufficiently testable.

It has a scoping clause in place and explains that images of text are not expected to adapt. Does does this text alleviate your concerns?

Thanks again,
Laura

@awkawk
Copy link
Member

awkawk commented Sep 15, 2017

@alexswli The comments you raise have been addressed in the latest version: https://www.w3.org/TR/WCAG21/#adapting-text - closing this issue.

@awkawk awkawk closed this as completed Sep 15, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

7 participants