<?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: Self-Referential Links: Controversy Rumbles On</title>
	<atom:link href="http://www.thepickards.co.uk/index.php/200608/self-referential-links-controversy-rumbles-on/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.thepickards.co.uk/index.php/200608/self-referential-links-controversy-rumbles-on/</link>
	<description>ranting and rambling to anyone willing to listen</description>
	<lastBuildDate>Sun, 12 Feb 2012 00:51:26 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: garment daily business reports</title>
		<link>http://www.thepickards.co.uk/index.php/200608/self-referential-links-controversy-rumbles-on/comment-page-1/#comment-152526</link>
		<dc:creator>garment daily business reports</dc:creator>
		<pubDate>Thu, 28 Jul 2011 16:13:19 +0000</pubDate>
		<guid isPermaLink="false">http://www.thepickards.co.uk/index.php/200608/self-referential-links-controversy-rumbles-on/#comment-152526</guid>
		<description>&lt;strong&gt;Blogs ou should be reading...&lt;/strong&gt;

[...]Here is a Great Blog You Might Find Interesting that we Encourage You[...]…...</description>
		<content:encoded><![CDATA[<p><strong>Blogs ou should be reading&#8230;</strong></p>
<p>[...]Here is a Great Blog You Might Find Interesting that we Encourage You[...]…&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: AlastairC</title>
		<link>http://www.thepickards.co.uk/index.php/200608/self-referential-links-controversy-rumbles-on/comment-page-1/#comment-294</link>
		<dc:creator>AlastairC</dc:creator>
		<pubDate>Thu, 12 Oct 2006 13:46:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.thepickards.co.uk/index.php/200608/self-referential-links-controversy-rumbles-on/#comment-294</guid>
		<description>Hmm, lots of stuff to comment on there:

&quot;We donâ€™t believe that accessibility and usability are the same thing.&quot;

Without getting into semantics, I would suggest that accessibility is a particular niche of usability, which is fairly clear from the standard definition of usability. The main difference is that accessibility is mandated with legal requirements.

&quot;we want to be sure that issues that are recorded are due to the inaccessibility of the site and not because the tester doesnâ€™t know how to use their software properly.&quot; as any experienced facilitator will be able to do.

&quot;we choose to work regularly with a core team with a broad spectrum of disabilities.&quot; See:
http://alastairc.ac/2006/07/expert-usability-participants/

&quot;a method where the level of expertise of the user and his/her assistive technology is unknown.&quot; These aspects are known, checked and accounted for.

It is unlikely that you would notice self-referential links as an issue without observing typical users.

&quot;It is the styling of the link that is the important factor and there are many other more effective ways of offering strong indicators of the current page in the menu system.&quot; 
How would that styling be apparent to someone using a screen reader? Also, when using a screen magnifier and the link is not near any page information headings, as is often the case.

What better way is there to indicate that it is the current page than with styling &lt;strong&gt;and&lt;/strong&gt; structure?</description>
		<content:encoded><![CDATA[<p>Hmm, lots of stuff to comment on there:</p>
<p>&#8220;We donâ€™t believe that accessibility and usability are the same thing.&#8221;</p>
<p>Without getting into semantics, I would suggest that accessibility is a particular niche of usability, which is fairly clear from the standard definition of usability. The main difference is that accessibility is mandated with legal requirements.</p>
<p>&#8220;we want to be sure that issues that are recorded are due to the inaccessibility of the site and not because the tester doesnâ€™t know how to use their software properly.&#8221; as any experienced facilitator will be able to do.</p>
<p>&#8220;we choose to work regularly with a core team with a broad spectrum of disabilities.&#8221; See:<br />
<a href="http://alastairc.ac/2006/07/expert-usability-participants/" rel="nofollow">http://alastairc.ac/2006/07/expert-usability-participants/</a></p>
<p>&#8220;a method where the level of expertise of the user and his/her assistive technology is unknown.&#8221; These aspects are known, checked and accounted for.</p>
<p>It is unlikely that you would notice self-referential links as an issue without observing typical users.</p>
<p>&#8220;It is the styling of the link that is the important factor and there are many other more effective ways of offering strong indicators of the current page in the menu system.&#8221;<br />
How would that styling be apparent to someone using a screen reader? Also, when using a screen magnifier and the link is not near any page information headings, as is often the case.</p>
<p>What better way is there to indicate that it is the current page than with styling <strong>and</strong> structure?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Grant Broome</title>
		<link>http://www.thepickards.co.uk/index.php/200608/self-referential-links-controversy-rumbles-on/comment-page-1/#comment-62</link>
		<dc:creator>Grant Broome</dc:creator>
		<pubDate>Tue, 22 Aug 2006 09:19:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.thepickards.co.uk/index.php/200608/self-referential-links-controversy-rumbles-on/#comment-62</guid>
		<description>At Shaw Trust the testing method is quite different from that at Nomensa.
We don&#039;t believe that accessibilty and usability are the same thing.
To be able to accredit a website, we want to be sure that issues that are recorded are due to the innaccessibilty of the site and not because the tester doesn&#039;t know how to use their software properly. This is why we choose to work regularly with a core team with a broad spectrum of disabilities. We feel that this method has many advantages over a method where the level of expertise of the user and his/her assistive technology is unknown. 

From your comment I would summise that the issue you have observed is not because the page is self referential, but that it is not clear to the user which page they are currently on or that the link that they are trying to activate is the current page. I do not accept that the best way to indicate the current page is to remove the self-link. It is the styling of the link that is the important factor and there are many other more effective ways of offering strong indicators of the current page in the menu system.</description>
		<content:encoded><![CDATA[<p>At Shaw Trust the testing method is quite different from that at Nomensa.<br />
We don&#8217;t believe that accessibilty and usability are the same thing.<br />
To be able to accredit a website, we want to be sure that issues that are recorded are due to the innaccessibilty of the site and not because the tester doesn&#8217;t know how to use their software properly. This is why we choose to work regularly with a core team with a broad spectrum of disabilities. We feel that this method has many advantages over a method where the level of expertise of the user and his/her assistive technology is unknown. </p>
<p>From your comment I would summise that the issue you have observed is not because the page is self referential, but that it is not clear to the user which page they are currently on or that the link that they are trying to activate is the current page. I do not accept that the best way to indicate the current page is to remove the self-link. It is the styling of the link that is the important factor and there are many other more effective ways of offering strong indicators of the current page in the menu system.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: AlastairC</title>
		<link>http://www.thepickards.co.uk/index.php/200608/self-referential-links-controversy-rumbles-on/comment-page-1/#comment-61</link>
		<dc:creator>AlastairC</dc:creator>
		<pubDate>Mon, 21 Aug 2006 20:31:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.thepickards.co.uk/index.php/200608/self-referential-links-controversy-rumbles-on/#comment-61</guid>
		<description>Hi Jack,

Does the Shaw trust observe people during the sessions or are the results &lt;a href=&quot;http://alastairc.ac/2006/07/expert-usability-participants/&quot; rel=&quot;nofollow&quot;&gt;self reported&lt;/a&gt;?

I&#039;ve seen it cause problems (as I mentioned on accessify), where (non-disabled) people have repeatedly clicked the self-referential links, and it is worse for people using screen magnifiers.

Not linking to the current page is a navigational indicator in itself, and with styling, quite a strong &lt;strong&gt;and&lt;/strong&gt; functional indicator.</description>
		<content:encoded><![CDATA[<p>Hi Jack,</p>
<p>Does the Shaw trust observe people during the sessions or are the results <a href="http://alastairc.ac/2006/07/expert-usability-participants/" rel="nofollow">self reported</a>?</p>
<p>I&#8217;ve seen it cause problems (as I mentioned on accessify), where (non-disabled) people have repeatedly clicked the self-referential links, and it is worse for people using screen magnifiers.</p>
<p>Not linking to the current page is a navigational indicator in itself, and with styling, quite a strong <strong>and</strong> functional indicator.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

