W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > April to June 2017

Re: Resize text: how to ensure success criteria WCAG 1.4.4

From: Mitchell Evan <mtchllvn@gmail.com>
Date: Wed, 24 May 2017 01:38:30 +0000
Message-ID: <CAK=xW6st3t3GNrT5kL7JMA40n_bs8NdETbWD7PKhiZj29rRuaQ@mail.gmail.com>
To: Herin Hentry <herinhentry@gmail.com>, "Patrick H. Lauke" <redux@splintered.co.uk>
Cc: WAI Interest Group <w3c-wai-ig@w3.org>
Kiran,

Gregg V's concise answer is correct, for this specific question: "What are
the requirements to pass WCAG 2.0 1.4.4?"

Additional factors are also important for a good user experience. Which of
these are the most important? That depends on your content, which users you
ask, what device and software they're using, and which accessibility expert
is most persuasive.

- Avoid horizontal scrolling

- Work well both with full zoom and with text-only enlargement (not just
one or the other)

- Make the content look good (not just avoiding "clipped, truncated or
obscured")

- Support enlargement beyond 200%

Mobile-responsive designs (RWD) often satisfy 1.4.4 and beyond, as long as
the design doesn't omit content at the smaller breakpoints.

Mitchell Evan

@mitchellrevan

On Wed, May 17, 2017, 6:01 PM Herin Hentry <herinhentry@gmail.com> wrote:

> Hi Kiran,
>
> WCAG explicitly says there are 2 failures related to this success
> criteria. We need to make sure these are not the barriers.
>
>
>    -
>
>    F69: Failure of Success Criterion 1.4.4 when resizing visually
>    rendered text up to 200 percent causes the text, image or controls to be
>    clipped, truncated or obscured
>    <http://www.w3.org/TR/2016/NOTE-WCAG20-TECHS-20161007/F69>
>    -
>
>    F80: Failure of Success Criterion 1.4.4 when text-based form controls
>    do not resize when visually rendered text is resized up to 200%
>    <http://www.w3.org/TR/2016/NOTE-WCAG20-TECHS-20161007/F80>
>
>
> Testing Resize Text with IE:
>
> 1)      From the IE Menu, select View > Text Size > Largest
>
> 2)      Check if all the text, input controls and containers have resized
>
> 3)      Make sure there is no major overlap and the display is not
> obscured
>
> 4)      Make sure there is no content trimming
>
>
>
> Testing Resize Text with Chrome
>
> Chrome browser > Settings > Show Advanced Settings > Web content
>
> Click on Customize fonts. This opens the Fonts Dialog. The standard font
> size is 16. As per WCAG, we need to increase the font size to 200% and make
> sure the functionality is not broken and the containers also resize. Change
> the Standard font to 32 (200% of 16). Check if the container resizes and
> the content is not trimmed.
>
>
> The issue with Ctrl ++ (zoom) is it adds horizontal scroll bars to the
> pages at 200%.
>
> As per WCAG 1.4.4 Resize Text : *The author's responsibility is to create
> Web content that does not prevent the user agent from scaling the content
> effectively.*
>
> *Thanks and Regards,*
>
> *Herin*
>
> On Thu, May 18, 2017 at 9:27 AM, Patrick H. Lauke <redux@splintered.co.uk>
> wrote:
>
>> On 17/05/2017 23:43, Userite wrote:
>> [...]
>>
>>> If you only check with one particular assistive tool for Zooming
>>>
>>
>> note that WCAG 2 explicitly says "text can be resized without assistive
>> technology", so only the zoom functionality built into the user agent can
>> be used to test this.
>>
>> P
>> --
>> Patrick H. Lauke
>>
>> www.splintered.co.uk | https://github.com/patrickhlauke
>> http://flickr.com/photos/redux/ | http://redux.deviantart.com
>> twitter: @patrick_h_lauke | skype: patrick_h_lauke
>>
>>
> --

Mitchell Evan
mtchllvn@gmail.com
+1 (510) 375-6104
Received on Wednesday, 24 May 2017 01:39:15 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 24 May 2017 01:39:17 UTC