<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Click Here? No thanks. I have a Better Idea &#8230;</title>
	<atom:link href="http://accessify.com/news/2007/09/click-here-no-thanks-i-have-a-better-idea/feed/" rel="self" type="application/rss+xml" />
	<link>http://accessify.com/news/2007/09/click-here-no-thanks-i-have-a-better-idea/</link>
	<description>Accessibility news: WCAG, WAI, PAS 78 ... and all manner of other weird acronyms and stuff</description>
	<lastBuildDate>Sun, 24 Jan 2010 22:14:20 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Is &#8216;Click Here&#8217; the Best Choice? - Cibolo Media Services</title>
		<link>http://accessify.com/news/2007/09/click-here-no-thanks-i-have-a-better-idea/comment-page-1/#comment-96188</link>
		<dc:creator>Is &#8216;Click Here&#8217; the Best Choice? - Cibolo Media Services</dc:creator>
		<pubDate>Fri, 15 May 2009 13:17:23 +0000</pubDate>
		<guid isPermaLink="false">http://accessify.com/news/2007/09/click-here-no-thanks-i-have-a-better-idea/#comment-96188</guid>
		<description>[...] company or with a client that won&#8217;t put &#8220;Click here&#8221; to rest? The article &#8220;Click here? No thanks!&#8221; offers a solution for developers to keep the links accessible even if visually &#8220;Click [...]</description>
		<content:encoded><![CDATA[<p>[...] company or with a client that won&#8217;t put &#8220;Click here&#8221; to rest? The article &#8220;Click here? No thanks!&#8221; offers a solution for developers to keep the links accessible even if visually &#8220;Click [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: RMM accessible web</title>
		<link>http://accessify.com/news/2007/09/click-here-no-thanks-i-have-a-better-idea/comment-page-1/#comment-62420</link>
		<dc:creator>RMM accessible web</dc:creator>
		<pubDate>Sat, 31 May 2008 12:55:11 +0000</pubDate>
		<guid isPermaLink="false">http://accessify.com/news/2007/09/click-here-no-thanks-i-have-a-better-idea/#comment-62420</guid>
		<description>I would try and avoid &quot;click here&quot; whenever possible but has certainly become something of a de facto standard so suggesting a way to keep it but still remain accessible is a great idea.</description>
		<content:encoded><![CDATA[<p>I would try and avoid &#8220;click here&#8221; whenever possible but has certainly become something of a de facto standard so suggesting a way to keep it but still remain accessible is a great idea.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kai</title>
		<link>http://accessify.com/news/2007/09/click-here-no-thanks-i-have-a-better-idea/comment-page-1/#comment-25297</link>
		<dc:creator>Kai</dc:creator>
		<pubDate>Thu, 04 Oct 2007 06:32:35 +0000</pubDate>
		<guid isPermaLink="false">http://accessify.com/news/2007/09/click-here-no-thanks-i-have-a-better-idea/#comment-25297</guid>
		<description>There should have been code in my previous statement...

[a ...]Click here [span class=offscreen]to view our beautifull product xyz[/span][/a]</description>
		<content:encoded><![CDATA[<p>There should have been code in my previous statement&#8230;</p>
<p>[a ...]Click here [span class=offscreen]to view our beautifull product xyz[/span][/a]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kai</title>
		<link>http://accessify.com/news/2007/09/click-here-no-thanks-i-have-a-better-idea/comment-page-1/#comment-25296</link>
		<dc:creator>Kai</dc:creator>
		<pubDate>Thu, 04 Oct 2007 06:30:53 +0000</pubDate>
		<guid isPermaLink="false">http://accessify.com/news/2007/09/click-here-no-thanks-i-have-a-better-idea/#comment-25296</guid>
		<description>Another way - if there is no room for long link phrases - would be:

&lt;a&gt;Click here to view our beautifull product xyz&lt;/a&gt;

So you have a visual short version wich expands in screenreaders nicely. Of course it is better to show the complety link to everybody...</description>
		<content:encoded><![CDATA[<p>Another way &#8211; if there is no room for long link phrases &#8211; would be:</p>
<p><a>Click here to view our beautifull product xyz</a></p>
<p>So you have a visual short version wich expands in screenreaders nicely. Of course it is better to show the complety link to everybody&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Click Here -- It's Not About SEO! :: Unintentionally Blank</title>
		<link>http://accessify.com/news/2007/09/click-here-no-thanks-i-have-a-better-idea/comment-page-1/#comment-24561</link>
		<dc:creator>Click Here -- It's Not About SEO! :: Unintentionally Blank</dc:creator>
		<pubDate>Mon, 24 Sep 2007 21:43:22 +0000</pubDate>
		<guid isPermaLink="false">http://accessify.com/news/2007/09/click-here-no-thanks-i-have-a-better-idea/#comment-24561</guid>
		<description>[...] out what it was about. Or you could just click the link to find out, Mike Cherim alluded to this in a comment on Ian Lloyd&#8217;s compromise solution on Accessify. Clicking to find out what a link is all [...]</description>
		<content:encoded><![CDATA[<p>[...] out what it was about. Or you could just click the link to find out, Mike Cherim alluded to this in a comment on Ian Lloyd&#8217;s compromise solution on Accessify. Clicking to find out what a link is all [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: James</title>
		<link>http://accessify.com/news/2007/09/click-here-no-thanks-i-have-a-better-idea/comment-page-1/#comment-24528</link>
		<dc:creator>James</dc:creator>
		<pubDate>Mon, 24 Sep 2007 13:05:30 +0000</pubDate>
		<guid isPermaLink="false">http://accessify.com/news/2007/09/click-here-no-thanks-i-have-a-better-idea/#comment-24528</guid>
		<description>As I understand it, search engines will penalise pages that hide text by setting its colour to be the same as the background.
This is because it was once used to try and trick search engines into bumping that page up the rankings.
It will also still take up physical space on the page. Avoiding this is usually the reason why &quot;More&quot; or &quot;Click here&quot; links are used.

Maybe absolutely positioning the text off the screen would be an alternative?

See also the thread on this topic on the forum: www.accessifyforum.com/viewtopic.php?t=9067</description>
		<content:encoded><![CDATA[<p>As I understand it, search engines will penalise pages that hide text by setting its colour to be the same as the background.<br />
This is because it was once used to try and trick search engines into bumping that page up the rankings.<br />
It will also still take up physical space on the page. Avoiding this is usually the reason why &#8220;More&#8221; or &#8220;Click here&#8221; links are used.</p>
<p>Maybe absolutely positioning the text off the screen would be an alternative?</p>
<p>See also the thread on this topic on the forum: <a href="http://www.accessifyforum.com/viewtopic.php?t=9067" rel="nofollow">http://www.accessifyforum.com/viewtopic.php?t=9067</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike Cherim</title>
		<link>http://accessify.com/news/2007/09/click-here-no-thanks-i-have-a-better-idea/comment-page-1/#comment-24320</link>
		<dc:creator>Mike Cherim</dc:creator>
		<pubDate>Fri, 21 Sep 2007 21:28:24 +0000</pubDate>
		<guid isPermaLink="false">http://accessify.com/news/2007/09/click-here-no-thanks-i-have-a-better-idea/#comment-24320</guid>
		<description>Click here has the greatest click-through rate because users don&#039;t know where the damn link leads and have to click it to find out! Not a good practice in my opinion, though I suppose there are instances where it&#039;s perfectly fine (on a page by itself preceeded by text that makes it clear, but even that is weak becuase not all users will access the descriptive text as we want them to).

Regarding the spatial location of webby parts, I don&#039;t mind using right, left, top, bottom, but one does have to consider that not all users will see it the same way. What I do in those rare instances when I do give a physical location like that is add to the statement, then using offset positioning I strip part of it away so it&#039;s not visible, but will still be accessible. I only define the class in the screen style sheet. All others get the text (I do provide handheld and print style sheets regularly so this is possible).

&lt;code&gt;&lt;p&gt;Use the menu to the right,&lt;span class=&quot;offset-screen&quot;&gt; or at the bottom of the page if you&#039;re using a browser that offers the page differently,&lt;/span&gt; to get around this site.&lt;/p&gt;&lt;/code&gt; 

I don&#039;t use something like this very much, but IMO it can be helpful, especially if you &lt;em&gt;really&lt;/em&gt; need to convey location to your core audience.</description>
		<content:encoded><![CDATA[<p>Click here has the greatest click-through rate because users don&#8217;t know where the damn link leads and have to click it to find out! Not a good practice in my opinion, though I suppose there are instances where it&#8217;s perfectly fine (on a page by itself preceeded by text that makes it clear, but even that is weak becuase not all users will access the descriptive text as we want them to).</p>
<p>Regarding the spatial location of webby parts, I don&#8217;t mind using right, left, top, bottom, but one does have to consider that not all users will see it the same way. What I do in those rare instances when I do give a physical location like that is add to the statement, then using offset positioning I strip part of it away so it&#8217;s not visible, but will still be accessible. I only define the class in the screen style sheet. All others get the text (I do provide handheld and print style sheets regularly so this is possible).</p>
<p><code>&lt;p&gt;Use the menu to the right,&lt;span class=&quot;offset-screen&quot;&gt; or at the bottom of the page if you're using a browser that offers the page differently,&lt;/span&gt; to get around this site.&lt;/p&gt;</code> </p>
<p>I don&#8217;t use something like this very much, but IMO it can be helpful, especially if you <em>really</em> need to convey location to your core audience.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Harold</title>
		<link>http://accessify.com/news/2007/09/click-here-no-thanks-i-have-a-better-idea/comment-page-1/#comment-24210</link>
		<dc:creator>Harold</dc:creator>
		<pubDate>Thu, 20 Sep 2007 11:37:47 +0000</pubDate>
		<guid isPermaLink="false">http://accessify.com/news/2007/09/click-here-no-thanks-i-have-a-better-idea/#comment-24210</guid>
		<description>Thanks for the responses to my &quot;click in the menu on the left&quot; query. I agree with patrick h. lauke that it&#039;s a sign of bad design, however the reality of the situation is that the layout (or code for that matter) of the site I spend a lot of time in is not under my control, it has zero semantic markup: headers are implemented with spans for example. I will look into the possibilities of adding redundant links instead.</description>
		<content:encoded><![CDATA[<p>Thanks for the responses to my &#8220;click in the menu on the left&#8221; query. I agree with patrick h. lauke that it&#8217;s a sign of bad design, however the reality of the situation is that the layout (or code for that matter) of the site I spend a lot of time in is not under my control, it has zero semantic markup: headers are implemented with spans for example. I will look into the possibilities of adding redundant links instead.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Carlos</title>
		<link>http://accessify.com/news/2007/09/click-here-no-thanks-i-have-a-better-idea/comment-page-1/#comment-24207</link>
		<dc:creator>Carlos</dc:creator>
		<pubDate>Thu, 20 Sep 2007 10:34:41 +0000</pubDate>
		<guid isPermaLink="false">http://accessify.com/news/2007/09/click-here-no-thanks-i-have-a-better-idea/#comment-24207</guid>
		<description>@john, I&#039;m afraid that this other alternative is even worse, as it suffer from the same problems as the first &quot;compromise solutions&quot; (see #5), and it additionally makes imposible for others than screen reader users to have an idea of what are they going to find if they follow the link.</description>
		<content:encoded><![CDATA[<p>@john, I&#8217;m afraid that this other alternative is even worse, as it suffer from the same problems as the first &#8220;compromise solutions&#8221; (see #5), and it additionally makes imposible for others than screen reader users to have an idea of what are they going to find if they follow the link.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John Faulds</title>
		<link>http://accessify.com/news/2007/09/click-here-no-thanks-i-have-a-better-idea/comment-page-1/#comment-24173</link>
		<dc:creator>John Faulds</dc:creator>
		<pubDate>Thu, 20 Sep 2007 01:01:09 +0000</pubDate>
		<guid isPermaLink="false">http://accessify.com/news/2007/09/click-here-no-thanks-i-have-a-better-idea/#comment-24173</guid>
		<description>Another alternative which has been written about before is to wrap the extra information that comes after &#039;click here&#039; (in this case &#039;to learn about widgets&#039;) in a span and move it offscreen; it&#039;s still read by AT users and SEs but doesn&#039;t show on screen.</description>
		<content:encoded><![CDATA[<p>Another alternative which has been written about before is to wrap the extra information that comes after &#8216;click here&#8217; (in this case &#8216;to learn about widgets&#8217;) in a span and move it offscreen; it&#8217;s still read by AT users and SEs but doesn&#8217;t show on screen.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
