E-mail List Archives
Re: Linked Text Image Violating WCAG's 1.4.5?l
From: Patrick H. Lauke
Date: Aug 18, 2017 10:37AM
- Next message: pratik roy: "NVDA not reading fieldset grouping for checkboxes when..."
- Previous message: Peter Shikli: "Re: Linked Text Image Violating WCAG's 1.4.5?l"
- Next message in Thread: Guy Hickling: "Re: Linked Text Image Violating WCAG's 1.4.5?l"
- Previous message in Thread: Peter Shikli: "Re: Linked Text Image Violating WCAG's 1.4.5?l"
- View all messages in this Thread
On 18/08/2017 17:24, Peter Shikli wrote:
> Hi Ugi,
>
> Whereas I do agree that linked text images should be replaced by
> CSS-stylized text, the argument raging here is whether we suggest that
> or require it for a Level AA rating per WCAG 2.0? We're getting
> pushback from web designers, as one should expect, and we need to take a
> stand to suggest or to require.
>
> Their argument is that linked text images function just like
> type="image" buttons, which WCAG allows. The counterargument is that
> the syntax (tags) for buttons are different from images.
The same rationale would apply to type="image" buttons as well. As in:
those buttons aren't exempt from 1.4.5 either.
Images of text have many disadvantages - ranging from mild annoyance for
some to actual hard-to-overcome problems for others.
The question really is: can the same/very similar look and feel be
achieved using something other than images of text? This can range from
using HTML and CSS, to using SVG, adding web fonts, etc.
If the answer is no, a follow-up question is: is it absolutely essential
that the text be presented in a certain way? For instance, if the text
didn't have a pillow emboss effect with flames shooting up inside the
characters, which can only be done easily in Photoshop, would it still
serve the same function? Or, more realistically: if the text for the
navigation items wasn't in the official company typeface because it's
not available as a web font, would this contravene corporate identity
guidelines?
If the answer is again no, then it's a FAIL of 1.4.5.
That's pretty much the hardline interpretation here of the normative
aspect of this SC. Now, the understanding document for this
https://www.w3.org/TR/UNDERSTANDING-WCAG20/visual-audio-contrast-text-presentation.html
is a bit weaker (it talks of "should" and "encourage authors"), but the
understanding is informative/non-normative. Going by a strict reading of
the normative SC text only, it's a fairly clear pass/fail situation.
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
- Next message: pratik roy: "NVDA not reading fieldset grouping for checkboxes when..."
- Previous message: Peter Shikli: "Re: Linked Text Image Violating WCAG's 1.4.5?l"
- Next message in Thread: Guy Hickling: "Re: Linked Text Image Violating WCAG's 1.4.5?l"
- Previous message in Thread: Peter Shikli: "Re: Linked Text Image Violating WCAG's 1.4.5?l"
- View all messages in this Thread