Fwd: [w3c/wcag21] 1.4.11 Resize content (#207)

In case some missed this on github
---------- Forwarded message ----------
From: "jspellman" <notifications@github.com>
Date: Mar 30, 2017 6:27 PM
Subject: [w3c/wcag21] 1.4.11 Resize content (#207)
To: "w3c/wcag21" <wcag21@noreply.github.com>
Cc: "Subscribed" <subscribed@noreply.github.com>

There are a number of points that we think will make this SC clearer, many
of which have been discussed in the Github issue but we feel are still
important and haven't been addressed.

Change the word 'resized' in the SC to ‘zoomed’ and be explicit in the
description that resize means full page zoom and not text resize, assuming
that is the intent.

"fixed spacial layout" needs a definition, preferably with examples. While
we agree that the SC should not aim to be exhaustive in providing
exceptions, our experience is that it is exactly this lack of clarity
backed up with real world examples that generates much of the confusion and
debate around existing SC.

Include word-breaks in the examples for "fixed spacial layout" exceptions.
We recommend something to the effect that "Words that exceed the width of
the viewport must be hyphenated in user agents that support automatic
hyphenation".

Explicitly specify that a user agent that supports 400% zoom should be used
as part of the testing methodology. Optionally note that not all user
agents support 400% zoom.

[filed on behalf of engineers at The Paciello Group]

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<https://github.com/w3c/wcag21/issues/207>, or mute the thread
<https://github.com/notifications/unsubscribe-auth/AG_WL_i1G_ono1ANFM__-NcGyIZprJi1ks5rrDp6gaJpZM4MvC_N>
.