W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > July to September 2012

Re: F3: Failure of Success Criterion 1.1.1 due to using CSS

From: Benjamin Hawkes-Lewis <bhawkeslewis@googlemail.com>
Date: Fri, 17 Aug 2012 23:28:48 +0100
Message-ID: <CAEhSh3eo_xtRWv5pwo-PLijnNYrkp17MbU_xV6r1hZgMgZUndg@mail.gmail.com>
To: Neil King <Neil.King@visionaustralia.org>
Cc: "w3c-wai-ig@w3.org" <w3c-wai-ig@w3.org>
On Fri, Aug 17, 2012 at 3:26 AM, Neil King
<Neil.King@visionaustralia.org> wrote:
> Hi All
> We are finding more and more clients are struggling to overcome F3 of WCAG
> 2.0 (Failure of Success Criterion 1.1.1 due to using CSS to include images
> that convey important information). Essentially they are using CSS Sprites
> for buttons and other important images that are not visible in Windows High
> Contrast Mode.
> Does anyone know of an easy way around this for complex and large websites
> that are not planning a redesign? Steve provided some great insights in his
> article 'High Contrast Proof CSS Sprites' via the before: pseudo element
> (http://www.paciellogroup.com/blog/2010/01/high-contrast-proof-css-sprites/).
> Anyone have any advances on this or similar solutions they recommend?

Well, one thing to note is that after talk in various circles about
using media queries for this purpose, it looks like Microsoft have
introduced a vendor-specific media query for high contrast in Windows


Apparently this will make an appearance in IE 10:


Something like this has been discussed for inclusion in a future media
queries spec:


Benjamin Hawkes-Lewis
Received on Friday, 17 August 2012 22:29:37 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:36:41 UTC