-
Notifications
You must be signed in to change notification settings - Fork 54
Microsoft Comments on Adapting Text #186
Comments
Authors who code flexible pages will have no problem with these changes. A
browser cannot fix an inflexible page.
|
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.
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.
There is an exception for that, probably added after you looked:
|
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. |
Hi @alexswli , Alex wrote:
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:
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, |
@alexswli The comments you raise have been addressed in the latest version: https://www.w3.org/TR/WCAG21/#adapting-text - closing this issue. |
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.
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.
The text was updated successfully, but these errors were encountered: