<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.1" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Quiz 1.1.3: Adjacent duplicate links</title>
	<link>http://www.access-matters.com/2005/05/01/quiz-113-adjacent-duplicate-links/</link>
	<description>Seeking Best Accessibility Practices</description>
	<pubDate>Fri, 16 May 2008 05:32:09 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.1</generator>

	<item>
		<title>By: Jeroen Mulder</title>
		<link>http://www.access-matters.com/2005/05/01/quiz-113-adjacent-duplicate-links/#comment-377</link>
		<author>Jeroen Mulder</author>
		<pubDate>Sun, 01 May 2005 11:27:28 +0000</pubDate>
		<guid>http://www.access-matters.com/2005/05/01/quiz-113-adjacent-duplicate-links/#comment-377</guid>
					<description>I tend to lean towards C for things like this. The image is purely presentational and doesn't need to communicate a message at all, because of the existing text link. This way you are preventing redundant information while keeping the message short and clear. 

I am still not 100% sure about this though, but right now that's where I am standing. </description>
		<content:encoded><![CDATA[<p>I tend to lean towards C for things like this. The image is purely presentational and doesn&#8217;t need to communicate a message at all, because of the existing text link. This way you are preventing redundant information while keeping the message short and clear. </p>
<p>I am still not 100% sure about this though, but right now that&#8217;s where I am standing.</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Mike Cherim</title>
		<link>http://www.access-matters.com/2005/05/01/quiz-113-adjacent-duplicate-links/#comment-378</link>
		<author>Mike Cherim</author>
		<pubDate>Sun, 01 May 2005 13:30:59 +0000</pubDate>
		<guid>http://www.access-matters.com/2005/05/01/quiz-113-adjacent-duplicate-links/#comment-378</guid>
					<description>For me this really depends on the exact situation. I have one recent example where I had a linked image with text. I made the alt text read exactly the same as the image text and incorporated everything together. I tested it and was delighted with the results, sighted or not, it read exactly the same way.

Otherwise I tend to mirror in text the link before or after the image, but I try to do so in a natural way. 

Example:

&lt;em&gt;Browsing slow &#38; unsafe? Try &lt;a href="http://www.mozilla.org/products/firefox/" title="Get Firefox" rel="nofollow"&gt;Firefox&lt;/a&gt; and rediscover the web.&lt;/em&gt;
&lt;a href="http://www.mozilla.org/products/firefox/" rel="nofollow"&gt;
&lt;/a&gt;

My fear is that things can get redundant fast. The example above is pushing it due to the tool tip in the first link and the alt text in the second link. Perhaps since it's mirrored the best thing to do would be to nullify both. Like so.

&lt;em&gt;Browsing slow &#38; unsafe? &lt;a href="http://www.mozilla.org/products/firefox/" rel="nofollow"&gt;Get Firefox&lt;/a&gt; and rediscover the web.&lt;/em&gt;
&lt;a href="http://www.mozilla.org/products/firefox/" rel="nofollow"&gt;
&lt;/a&gt;
</description>
		<content:encoded><![CDATA[<p>For me this really depends on the exact situation. I have one recent example where I had a linked image with text. I made the alt text read exactly the same as the image text and incorporated everything together. I tested it and was delighted with the results, sighted or not, it read exactly the same way.</p>
<p>Otherwise I tend to mirror in text the link before or after the image, but I try to do so in a natural way. </p>
<p>Example:</p>
<p><em>Browsing slow &amp; unsafe? Try <a href="http://www.mozilla.org/products/firefox/" title="Get Firefox" rel="nofollow">Firefox</a> and rediscover the web.</em><br />
<a href="http://www.mozilla.org/products/firefox/" rel="nofollow"><br />
</a></p>
<p>My fear is that things can get redundant fast. The example above is pushing it due to the tool tip in the first link and the alt text in the second link. Perhaps since it&#8217;s mirrored the best thing to do would be to nullify both. Like so.</p>
<p><em>Browsing slow &amp; unsafe? <a href="http://www.mozilla.org/products/firefox/" rel="nofollow">Get Firefox</a> and rediscover the web.</em><br />
<a href="http://www.mozilla.org/products/firefox/" rel="nofollow"><br />
</a></p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Mike Cherim</title>
		<link>http://www.access-matters.com/2005/05/01/quiz-113-adjacent-duplicate-links/#comment-379</link>
		<author>Mike Cherim</author>
		<pubDate>Sun, 01 May 2005 13:34:26 +0000</pubDate>
		<guid>http://www.access-matters.com/2005/05/01/quiz-113-adjacent-duplicate-links/#comment-379</guid>
					<description>Hmm. Sorry. My reply above would make more sense if the Firefox icon images were posted but they didn't show up.

Answer D, anyway.</description>
		<content:encoded><![CDATA[<p>Hmm. Sorry. My reply above would make more sense if the Firefox icon images were posted but they didn&#8217;t show up.</p>
<p>Answer D, anyway.</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: patrick h. lauke</title>
		<link>http://www.access-matters.com/2005/05/01/quiz-113-adjacent-duplicate-links/#comment-380</link>
		<author>patrick h. lauke</author>
		<pubDate>Sun, 01 May 2005 15:50:06 +0000</pubDate>
		<guid>http://www.access-matters.com/2005/05/01/quiz-113-adjacent-duplicate-links/#comment-380</guid>
					<description>C, as the image is pure visual fluff. if for whatever reason it wasn't possible to use CSS, B.</description>
		<content:encoded><![CDATA[<p>C, as the image is pure visual fluff. if for whatever reason it wasn&#8217;t possible to use CSS, B.</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Roger Johansson</title>
		<link>http://www.access-matters.com/2005/05/01/quiz-113-adjacent-duplicate-links/#comment-381</link>
		<author>Roger Johansson</author>
		<pubDate>Sun, 01 May 2005 17:22:15 +0000</pubDate>
		<guid>http://www.access-matters.com/2005/05/01/quiz-113-adjacent-duplicate-links/#comment-381</guid>
					<description>No doubt it should be C.</description>
		<content:encoded><![CDATA[<p>No doubt it should be C.</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Anne</title>
		<link>http://www.access-matters.com/2005/05/01/quiz-113-adjacent-duplicate-links/#comment-382</link>
		<author>Anne</author>
		<pubDate>Sun, 01 May 2005 17:45:43 +0000</pubDate>
		<guid>http://www.access-matters.com/2005/05/01/quiz-113-adjacent-duplicate-links/#comment-382</guid>
					<description>B and C are equally accessible. B is a little easier to create I guess, but C is better from a markup point of view and probably from all other points of view too.</description>
		<content:encoded><![CDATA[<p>B and C are equally accessible. B is a little easier to create I guess, but C is better from a markup point of view and probably from all other points of view too.</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Shawn</title>
		<link>http://www.access-matters.com/2005/05/01/quiz-113-adjacent-duplicate-links/#comment-383</link>
		<author>Shawn</author>
		<pubDate>Sun, 01 May 2005 18:38:58 +0000</pubDate>
		<guid>http://www.access-matters.com/2005/05/01/quiz-113-adjacent-duplicate-links/#comment-383</guid>
					<description>Definitely C.

It makes for easier management down the road and also allows you more flexibility with smaller style rules and markup when using :hover, :visited, etc.</description>
		<content:encoded><![CDATA[<p>Definitely C.</p>
<p>It makes for easier management down the road and also allows you more flexibility with smaller style rules and markup when using :hover, :visited, etc.</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Philippe</title>
		<link>http://www.access-matters.com/2005/05/01/quiz-113-adjacent-duplicate-links/#comment-384</link>
		<author>Philippe</author>
		<pubDate>Mon, 02 May 2005 07:47:39 +0000</pubDate>
		<guid>http://www.access-matters.com/2005/05/01/quiz-113-adjacent-duplicate-links/#comment-384</guid>
					<description>C in case the image is purely ornamental (like icons). B if the image is part of the content (product-image + product-name link to product specific page).</description>
		<content:encoded><![CDATA[<p>C in case the image is purely ornamental (like icons). B if the image is part of the content (product-image + product-name link to product specific page).</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Jérôme Coupé</title>
		<link>http://www.access-matters.com/2005/05/01/quiz-113-adjacent-duplicate-links/#comment-385</link>
		<author>Jérôme Coupé</author>
		<pubDate>Mon, 02 May 2005 08:16:09 +0000</pubDate>
		<guid>http://www.access-matters.com/2005/05/01/quiz-113-adjacent-duplicate-links/#comment-385</guid>
					<description>C would be my answer in this case (image is purely visual in this case). If the image conveys info, then method B is the one I would use).</description>
		<content:encoded><![CDATA[<p>C would be my answer in this case (image is purely visual in this case). If the image conveys info, then method B is the one I would use).</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Jordan Moore</title>
		<link>http://www.access-matters.com/2005/05/01/quiz-113-adjacent-duplicate-links/#comment-386</link>
		<author>Jordan Moore</author>
		<pubDate>Mon, 02 May 2005 21:42:36 +0000</pubDate>
		<guid>http://www.access-matters.com/2005/05/01/quiz-113-adjacent-duplicate-links/#comment-386</guid>
					<description>If the image is purely presentational (conveys no additional information), method C should be used; however, in the case that the image conveys additional information, I'd have to go with method B.</description>
		<content:encoded><![CDATA[<p>If the image is purely presentational (conveys no additional information), method C should be used; however, in the case that the image conveys additional information, I&#8217;d have to go with method B.</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Ben</title>
		<link>http://www.access-matters.com/2005/05/01/quiz-113-adjacent-duplicate-links/#comment-387</link>
		<author>Ben</author>
		<pubDate>Tue, 03 May 2005 02:28:54 +0000</pubDate>
		<guid>http://www.access-matters.com/2005/05/01/quiz-113-adjacent-duplicate-links/#comment-387</guid>
					<description>C, personally; B if printing that icon were important.</description>
		<content:encoded><![CDATA[<p>C, personally; B if printing that icon were important.</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Bob Easton</title>
		<link>http://www.access-matters.com/2005/05/01/quiz-113-adjacent-duplicate-links/#comment-389</link>
		<author>Bob Easton</author>
		<pubDate>Sat, 07 May 2005 22:08:21 +0000</pubDate>
		<guid>http://www.access-matters.com/2005/05/01/quiz-113-adjacent-duplicate-links/#comment-389</guid>
					<description>Dimitri Glazkov writes in &lt;a href="http://glazkov.com/blog/archive/2005/04/18/430.aspx" rel="nofollow"&gt;"Graphics and Structural Markup: Keeping 'pretties' out of content"&lt;/a&gt; good Rules of Thumb for determining whether an image is content or presentational.  The image in this example is purely presentational and not crucial to the content.  It's not even important to print. Therefore, I'm voting C.</description>
		<content:encoded><![CDATA[<p>Dimitri Glazkov writes in <a href="http://glazkov.com/blog/archive/2005/04/18/430.aspx" rel="nofollow">&#8220;Graphics and Structural Markup: Keeping &#8216;pretties&#8217; out of content&#8221;</a> good Rules of Thumb for determining whether an image is content or presentational.  The image in this example is purely presentational and not crucial to the content.  It&#8217;s not even important to print. Therefore, I&#8217;m voting C.</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Bob Easton</title>
		<link>http://www.access-matters.com/2005/05/01/quiz-113-adjacent-duplicate-links/#comment-402</link>
		<author>Bob Easton</author>
		<pubDate>Mon, 09 May 2005 09:26:09 +0000</pubDate>
		<guid>http://www.access-matters.com/2005/05/01/quiz-113-adjacent-duplicate-links/#comment-402</guid>
					<description>IBM Home Page reader 3.04, in item reading mode, speaks all three examples exactly the same way, as a simple link "slide show."</description>
		<content:encoded><![CDATA[<p>IBM Home Page reader 3.04, in item reading mode, speaks all three examples exactly the same way, as a simple link &#8220;slide show.&#8221;</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Bob Easton</title>
		<link>http://www.access-matters.com/2005/05/01/quiz-113-adjacent-duplicate-links/#comment-403</link>
		<author>Bob Easton</author>
		<pubDate>Mon, 09 May 2005 10:38:39 +0000</pubDate>
		<guid>http://www.access-matters.com/2005/05/01/quiz-113-adjacent-duplicate-links/#comment-403</guid>
					<description>Jaws 6.01 with IE 6
For example A says "link graphic link slide show"
For examples B and C says "link slide show"</description>
		<content:encoded><![CDATA[<p>Jaws 6.01 with IE 6<br />
For example A says &#8220;link graphic link slide show&#8221;<br />
For examples B and C says &#8220;link slide show&#8221;</p>
]]></content:encoded>
				</item>
</channel>
</rss>
