<?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: The shelf life of a skip link</title>
	<atom:link href="http://www.iheni.com/the-shelf-life-of-a-skip-link/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.iheni.com/the-shelf-life-of-a-skip-link/</link>
	<description></description>
	<lastBuildDate>Thu, 11 Mar 2010 06:11:44 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: iheni</title>
		<link>http://www.iheni.com/the-shelf-life-of-a-skip-link/comment-page-1/#comment-15410</link>
		<dc:creator>iheni</dc:creator>
		<pubDate>Wed, 12 Aug 2009 11:08:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.iheni.com/?p=1158#comment-15410</guid>
		<description>Paul, don&#039;t be dispirited, in fact the emphasis on that sentence is on the &quot;..you can start using HTML5 now&quot;.
Yes the spec is evolving and changing and yes they are yet to write all the test cases necessary but this doesn&#039;t mean that HTML5 can&#039;t be touched until all this work is 100% complete.
Many people are using HTML5 now (see http://html5gallery.com/) and are troubleshooting their way using it (see http://html5doctor.com/).

HTML5 is commonly referred to as &#039;paving the cowpathes&quot; and if we want to draw parallels to WCAG 2.0 I&#039;d say that much of what went into WCAG 2.0 was what responsible developers were already doing to make their sites accessible. 
So don;t feel you cant start working with it now, in fact now is a great time to get started so you can get familiar with what&#039;s happening and how to advance your own websites.</description>
		<content:encoded><![CDATA[<p>Paul, don&#8217;t be dispirited, in fact the emphasis on that sentence is on the &#8220;..you can start using HTML5 now&#8221;.<br />
Yes the spec is evolving and changing and yes they are yet to write all the test cases necessary but this doesn&#8217;t mean that HTML5 can&#8217;t be touched until all this work is 100% complete.<br />
Many people are using HTML5 now (see <a href="http://html5gallery.com/)" rel="nofollow">http://html5gallery.com/)</a> and are troubleshooting their way using it (see <a href="http://html5doctor.com/)" rel="nofollow">http://html5doctor.com/)</a>.</p>
<p>HTML5 is commonly referred to as &#8216;paving the cowpathes&#8221; and if we want to draw parallels to WCAG 2.0 I&#8217;d say that much of what went into WCAG 2.0 was what responsible developers were already doing to make their sites accessible.<br />
So don;t feel you cant start working with it now, in fact now is a great time to get started so you can get familiar with what&#8217;s happening and how to advance your own websites.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Paul</title>
		<link>http://www.iheni.com/the-shelf-life-of-a-skip-link/comment-page-1/#comment-15385</link>
		<dc:creator>Paul</dc:creator>
		<pubDate>Tue, 11 Aug 2009 14:13:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.iheni.com/?p=1158#comment-15385</guid>
		<description>Hi Heni

Excellent read, though a bit dispirited by this snippet:

&quot;That said, while the specification wont be finished until 2022 you can start using HTML5 now.&quot;
That must rival WCAG 2.0 for gestation periods...</description>
		<content:encoded><![CDATA[<p>Hi Heni</p>
<p>Excellent read, though a bit dispirited by this snippet:</p>
<p>&#8220;That said, while the specification wont be finished until 2022 you can start using HTML5 now.&#8221;<br />
That must rival WCAG 2.0 for gestation periods&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: iheni</title>
		<link>http://www.iheni.com/the-shelf-life-of-a-skip-link/comment-page-1/#comment-14121</link>
		<dc:creator>iheni</dc:creator>
		<pubDate>Mon, 22 Jun 2009 12:40:28 +0000</pubDate>
		<guid isPermaLink="false">http://www.iheni.com/?p=1158#comment-14121</guid>
		<description>Hi Grant, I&#039;m with you on the main content identifier too. It&#039;ll be interesting to see how HTML5 and it&#039;s development pans out and how it affect skip links. It will take a long time for them to become redundant (if at all) especially as they are becoming increasingly common on sites. That said I&#039;m looking forward to HTML itself having a solution to help page navigability without these additional hacks. It will hopefully mean that better accessibility even if the developer is less aware.

Let&#039;s hope anyway!</description>
		<content:encoded><![CDATA[<p>Hi Grant, I&#8217;m with you on the main content identifier too. It&#8217;ll be interesting to see how HTML5 and it&#8217;s development pans out and how it affect skip links. It will take a long time for them to become redundant (if at all) especially as they are becoming increasingly common on sites. That said I&#8217;m looking forward to HTML itself having a solution to help page navigability without these additional hacks. It will hopefully mean that better accessibility even if the developer is less aware.</p>
<p>Let&#8217;s hope anyway!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Grant broome</title>
		<link>http://www.iheni.com/the-shelf-life-of-a-skip-link/comment-page-1/#comment-14120</link>
		<dc:creator>Grant broome</dc:creator>
		<pubDate>Mon, 22 Jun 2009 12:31:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.iheni.com/?p=1158#comment-14120</guid>
		<description>Hi Heni, I Just wanted to chirp in and say I&#039;m with Bruce on the main content identifier. I&#039;m not up on HTML5, but it certainly seems to make sense to be able to identify the start of the main content it explicitly and seems a bit strange to me that this isn&#039;t already the case.

I think skip to content will be with us for a good while yet as there are many, many, things that need to happen before they become redundant.</description>
		<content:encoded><![CDATA[<p>Hi Heni, I Just wanted to chirp in and say I&#8217;m with Bruce on the main content identifier. I&#8217;m not up on HTML5, but it certainly seems to make sense to be able to identify the start of the main content it explicitly and seems a bit strange to me that this isn&#8217;t already the case.</p>
<p>I think skip to content will be with us for a good while yet as there are many, many, things that need to happen before they become redundant.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: iheni</title>
		<link>http://www.iheni.com/the-shelf-life-of-a-skip-link/comment-page-1/#comment-12841</link>
		<dc:creator>iheni</dc:creator>
		<pubDate>Thu, 07 May 2009 17:11:16 +0000</pubDate>
		<guid isPermaLink="false">http://www.iheni.com/?p=1158#comment-12841</guid>
		<description>So it looks like we&#039;re all thinking along similar lines which is interesting. This is really making me think about spec development (particularly HTML5) and how we can develop it so we can do away with as many of these hacks as possible. The less people have to learn about accessibility because it is reinforced in the spec the better. Nothing new there I guess...

Martin, thanks for pointing out your post on the XHTML Access module. I&#039;d not thought about this and will do some digging. Good post BTW.</description>
		<content:encoded><![CDATA[<p>So it looks like we&#8217;re all thinking along similar lines which is interesting. This is really making me think about spec development (particularly HTML5) and how we can develop it so we can do away with as many of these hacks as possible. The less people have to learn about accessibility because it is reinforced in the spec the better. Nothing new there I guess&#8230;</p>
<p>Martin, thanks for pointing out your post on the XHTML Access module. I&#8217;d not thought about this and will do some digging. Good post BTW.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
