Comments on: Quiz 1.1.4: Image Replacement Techniques http://www.access-matters.com/2005/05/08/quiz-114-image-replacement-techniques/ Seeking Best Accessibility Practices Wed, 08 Sep 2010 13:45:55 +0000 http://wordpress.org/?v=2.0.4 by: Unique Numbers in CSS | Playworkplay Webstudio http://www.access-matters.com/2005/05/08/quiz-114-image-replacement-techniques/#comment-177291 Wed, 12 Aug 2009 10:29:59 +0000 http://www.access-matters.com/2005/05/08/quiz-114-image-replacement-techniques/#comment-177291 [...] The usage of em causes some slight problem with old Version of Safari, so whenever possible (actually I can’t think of a situation when this isn’t possible) [...] […] The usage of em causes some slight problem with old Version of Safari, so whenever possible (actually I can’t think of a situation when this isn’t possible) […]

]]> by: WEB 3.0 » Blog Archive » ¿Así que querías saber de CSS? http://www.access-matters.com/2005/05/08/quiz-114-image-replacement-techniques/#comment-174970 Sat, 18 Apr 2009 01:19:33 +0000 http://www.access-matters.com/2005/05/08/quiz-114-image-replacement-techniques/#comment-174970 [...] Quiz 1.1.4: Image Replacement Techniques - Bob Easton [...] […] Quiz 1.1.4: Image Replacement Techniques - Bob Easton […]

]]> by: Bob Easton http://www.access-matters.com/2005/05/08/quiz-114-image-replacement-techniques/#comment-174951 Sun, 22 Feb 2009 12:59:38 +0000 http://www.access-matters.com/2005/05/08/quiz-114-image-replacement-techniques/#comment-174951 Jack, Either you are being more pedantic than most web designers, or you missed the premise of the situation. You are correct in what the HTML designers intended. Text is text and images are images. Beyond that, many developers are not at all satisfied with the very limited range of fonts available for the web. In short, many developers think that headings (using h1 through h6 and the fewer than a dozen font faces) are just plain ugly. That was why Todd Fahner developed the "image replacement" method. It is a method that allows the actual h1 through h6 heading code and original text to be retained, but to have that material replaced by a more attractive image of the text. This opens the possibility to literally thousands of font faces for text for headings. Using these methods, we can have heading text that is very attractive and have the original text too. The end result is a heading that is BOTH text and image. The question here, in this test case, is whether the various image replacement techniques are accessible. Can the underlying text still be found and announced by a screen reader? Jack,
Either you are being more pedantic than most web designers, or you missed the premise of the situation. You are correct in what the HTML designers intended. Text is text and images are images. Beyond that, many developers are not at all satisfied with the very limited range of fonts available for the web. In short, many developers think that headings (using h1 through h6 and the fewer than a dozen font faces) are just plain ugly.

That was why Todd Fahner developed the “image replacement” method. It is a method that allows the actual h1 through h6 heading code and original text to be retained, but to have that material replaced by a more attractive image of the text. This opens the possibility to literally thousands of font faces for text for headings. Using these methods, we can have heading text that is very attractive and have the original text too. The end result is a heading that is BOTH text and image.

The question here, in this test case, is whether the various image replacement techniques are accessible. Can the underlying text still be found and announced by a screen reader?

]]> by: Jack Zarnett http://www.access-matters.com/2005/05/08/quiz-114-image-replacement-techniques/#comment-174950 Sat, 21 Feb 2009 22:54:39 +0000 http://www.access-matters.com/2005/05/08/quiz-114-image-replacement-techniques/#comment-174950 An image cannot be a heading, and a heading cannot be an image. Period. There’s a reason that images are not allowed inside elements. Because headings are text, and images are images. Images can represent text, but they cannot BE text, and elements can only contain text — philosophically if not technologically. An image cannot be a heading, and a heading cannot be an image. Period. There’s a reason that images are not allowed inside elements. Because headings are text, and images are images. Images can represent text, but they cannot BE text, and elements can only contain text — philosophically if not technologically.

]]> by: çeviri http://www.access-matters.com/2005/05/08/quiz-114-image-replacement-techniques/#comment-47427 Sun, 08 Jul 2007 20:26:10 +0000 http://www.access-matters.com/2005/05/08/quiz-114-image-replacement-techniques/#comment-47427 Using Jaws 5 on IE6, all worked fine. Using Jaws 5 on IE6, all worked fine.

]]> by: Chris Ash, syd - Aust http://www.access-matters.com/2005/05/08/quiz-114-image-replacement-techniques/#comment-6097 Mon, 04 Sep 2006 02:46:23 +0000 http://www.access-matters.com/2005/05/08/quiz-114-image-replacement-techniques/#comment-6097 which i just noticed does not work on ur exampel page. You have obviously implemented in wrongly which i just noticed does not work on ur exampel page.
You have obviously implemented in wrongly

]]> by: Chris Ash, syd - Aust http://www.access-matters.com/2005/05/08/quiz-114-image-replacement-techniques/#comment-6086 Mon, 04 Sep 2006 01:53:11 +0000 http://www.access-matters.com/2005/05/08/quiz-114-image-replacement-techniques/#comment-6086 All these other Typography methods fail to do what SIFr does so well. Which is that SIRf swf's can be highlighted with ur cursor and copied as Text into a text document. How can you highlight an image hey? All these other Typography methods fail to do what SIFr does so well.

Which is that SIRf swf’s can be highlighted with ur cursor and copied as Text into a text document.

How can you highlight an image hey?

]]> by: Bob Easton http://www.access-matters.com/2005/05/08/quiz-114-image-replacement-techniques/#comment-1520 Sat, 06 May 2006 19:54:14 +0000 http://www.access-matters.com/2005/05/08/quiz-114-image-replacement-techniques/#comment-1520 David, As far as we know, no search engine yet parses CSS. So, there's no current penalty for these techniques. I'm also confident that when someone like Google does start taking CSS into account, if they go that far, they will consider how it combines with the HTML. These combinations will rank very low on their "spam probability" scale. David,
As far as we know, no search engine yet parses CSS. So, there’s no current penalty for these techniques. I’m also confident that when someone like Google does start taking CSS into account, if they go that far, they will consider how it combines with the HTML. These combinations will rank very low on their “spam probability” scale.

]]> by: David http://www.access-matters.com/2005/05/08/quiz-114-image-replacement-techniques/#comment-1511 Fri, 05 May 2006 02:44:46 +0000 http://www.access-matters.com/2005/05/08/quiz-114-image-replacement-techniques/#comment-1511 Can any of these image replacement techniques (negative indents, etc.) potentially be viewed as keyword spamming, resulting in a site being penalized or even dropped by search engines? Can any of these image replacement techniques (negative indents, etc.) potentially be viewed as keyword spamming, resulting in a site being penalized or even dropped by search engines?

]]> by: Thierry Koblentz http://www.access-matters.com/2005/05/08/quiz-114-image-replacement-techniques/#comment-591 Thu, 08 Sep 2005 05:21:06 +0000 http://www.access-matters.com/2005/05/08/quiz-114-image-replacement-techniques/#comment-591 Stephen, I don't really agree about losing separation of style from content. With method [1], it is easy to set the <code>src</code> value of the image elements through SS-Scripting, so the content layer is not bound to a particular set of images. Actually, this has some advantages over CSS or Javascript solutions since it <em>does not</em> rely on the user's settings. Regarding scaling, I agree that it is somehow limited, but my point was just to show how versatile this method was. Stephen,
I don’t really agree about losing separation of style from content.
With method [1], it is easy to set the src value of the image elements through SS-Scripting, so the content layer is not bound to a particular set of images.
Actually, this has some advantages over CSS or Javascript solutions since it does not rely on the user’s settings.

Regarding scaling, I agree that it is somehow limited, but my point was just to show how versatile this method was.

]]>