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: Jan Eric Hellbusch <hellbusch@2bweb.de>
Date: Fri, 17 Aug 2012 21:10:51 +0200
To: <w3c-wai-ig@w3.org>
Message-ID: <000001cd7cac$04aedc00$0e0c9400$@2bweb.de>

> 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?

You will find some basic solutions here:

* Links:
* Buttons:

There is a lot to write about icons, CSS sprites and accessibility.
Unfortunately, I can only offer it in German:

The bottom line is that 

* yes, you can get your icons displayed in high contrast mode with CSS
* but even if you do, there are still considerations needed to be made for
screenreader usage.

If icons and other images are not purely presentational, then they belong in
HTML with alternate text. And if they are purely presentational, then there
are still some accessibility reasons to keep them in HTML.

As far as your question is concerned: You are referring to 1.1.1 and that is
about alternate text, not high contrast mode. If images require an alternate
text and are thus placed in HTML, then they will be displayed in high
contrast mode as well.


Jan Eric Hellbusch 
Tel.: +49 (231) 86436760 oder +49 (163) 3369925
Web: http://2bweb.de     Twitter: www.twitter.com/2bweb
Das Buch über barrierefreies Webdesign:
"Barrierefreiheit verstehen und umsetzen - Webstandards für ein zugängliches
und nutzbares Internet"
812 Seiten, Dpunkt Verlag (2011)
Received on Friday, 17 August 2012 19:11:16 UTC

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