WebAIM - Web Accessibility In Mind

E-mail List Archives

Thread: WCAG 1.4.12

for

Number of posts in this thread: 3 (In chronological order)

From: Jon Brundage
Date: Fri, Jun 14 2019 12:16PM
Subject: WCAG 1.4.12
No previous message | Next message →

Hi Group-

What is your interpretation of the text spacing requrement in WCAG 2.1 (1.4.12- Text spacing) Looking for clarity on how this SC is to be applied.

Does it mean that specific spacing and line height must be used? Or that the content must be readable when someone applies a custom style sheet with the specific
requirements:

a.. Line height (line spacing) to at least 1.5 times the font size;
b.. Spacing following paragraphs to at least 2 times the font size;
c.. Letter spacing (tracking) to at least 0.12 times the font size;
d.. Word spacing to at least 0.16 times the font size.
Jon

From: Jared Smith
Date: Fri, Jun 14 2019 1:08PM
Subject: Re: WCAG 1.4.12
← Previous message | Next message →

The wording leaves a bit to be desired, but the intent is that there's
no loss of content or functionality if the USER applies these settings
to your page. As an author, you don't need to set these (except for
testing) - you just need to ensure things don't fall apart if the end
user does so.

I have a primary concern with this success criterion. Web pages that
already have optimal paragraph, line, word, and letter spacing (and
text sizes) can be more difficult to pass this because really good
spacing becomes VERY large spacing. An easy (though ill-advised)
solution to this is to make the default spacing and text sizes much
smaller - thus making it more difficult for everyone to read, but
easier to avoid this WCAG failure.

Jared

From: Patrick H. Lauke
Date: Fri, Jun 14 2019 2:54PM
Subject: Re: WCAG 1.4.12
← Previous message | No next message

On 14/06/2019 20:08, Jared Smith wrote:
> The wording leaves a bit to be desired, but the intent is that there's
> no loss of content or functionality if the USER applies these settings
> to your page. As an author, you don't need to set these (except for
> testing) - you just need to ensure things don't fall apart if the end
> user does so.
>
> I have a primary concern with this success criterion. Web pages that
> already have optimal paragraph, line, word, and letter spacing (and
> text sizes) can be more difficult to pass this because really good
> spacing becomes VERY large spacing. An easy (though ill-advised)
> solution to this is to make the default spacing and text sizes much
> smaller - thus making it more difficult for everyone to read, but
> easier to avoid this WCAG failure.

Similar to the old-school "text resize" for just text size (rather than
allowing full-page zoom as a valid method), the way to satisfy this is
in general not to set widths/heights in absolute hard units, and to be
careful with absolutely positioned elements. Have things adapt to
however big content can get.

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