<?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 for the art of web accessibility</title>
	<atom:link href="http://www.theaccessibility.com/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.theaccessibility.com</link>
	<description>making the web enjoyable for everybody</description>
	<lastBuildDate>Tue, 09 Mar 2010 06:13:29 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>Comment on Accessibility of Links by GrindSmart &#187; Blog Archive &#187; Best Resources and Practices for Web Accessibility</title>
		<link>http://www.theaccessibility.com/2010/03/link-accessibility/comment-page-1/#comment-3999</link>
		<dc:creator>GrindSmart &#187; Blog Archive &#187; Best Resources and Practices for Web Accessibility</dc:creator>
		<pubDate>Tue, 09 Mar 2010 06:13:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.theaccessibility.com/?p=411#comment-3999</guid>
		<description>[...] Accessibility of Links [...]</description>
		<content:encoded><![CDATA[<p>[...] Accessibility of Links [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Accessibility of Links by Joe Dolson</title>
		<link>http://www.theaccessibility.com/2010/03/link-accessibility/comment-page-1/#comment-3804</link>
		<dc:creator>Joe Dolson</dc:creator>
		<pubDate>Thu, 04 Mar 2010 16:27:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.theaccessibility.com/?p=411#comment-3804</guid>
		<description>This is an important thing to point out -- but I&#039;d also like to point out that having a color change only in :hover or :focus states is an equivalent problem; for keyboard navigability or for low vision, it&#039;s very valuable for links to change in some explicit way when they are focused on (removal of underline, etc.)

Thanks for your article!</description>
		<content:encoded><![CDATA[<p>This is an important thing to point out &#8212; but I&#8217;d also like to point out that having a color change only in :hover or :focus states is an equivalent problem; for keyboard navigability or for low vision, it&#8217;s very valuable for links to change in some explicit way when they are focused on (removal of underline, etc.)</p>
<p>Thanks for your article!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Accessibility of Links by Web Axe</title>
		<link>http://www.theaccessibility.com/2010/03/link-accessibility/comment-page-1/#comment-3708</link>
		<dc:creator>Web Axe</dc:creator>
		<pubDate>Tue, 02 Mar 2010 16:40:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.theaccessibility.com/?p=411#comment-3708</guid>
		<description>Glad you point this out in its own blog. I&#039;ve been complaining about this issue in my podcasts for a while now.</description>
		<content:encoded><![CDATA[<p>Glad you point this out in its own blog. I&#8217;ve been complaining about this issue in my podcasts for a while now.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Accessibility of Links by Douglas T</title>
		<link>http://www.theaccessibility.com/2010/03/link-accessibility/comment-page-1/#comment-3688</link>
		<dc:creator>Douglas T</dc:creator>
		<pubDate>Tue, 02 Mar 2010 05:26:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.theaccessibility.com/?p=411#comment-3688</guid>
		<description>Identifying anything by color alone causes a big problem with accessibility. It&#039;s a pet peeve of mine too.</description>
		<content:encoded><![CDATA[<p>Identifying anything by color alone causes a big problem with accessibility. It&#8217;s a pet peeve of mine too.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Skip Navigation by Steve</title>
		<link>http://www.theaccessibility.com/2009/05/skip-navigation/comment-page-1/#comment-3411</link>
		<dc:creator>Steve</dc:creator>
		<pubDate>Tue, 23 Feb 2010 03:48:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.theaccessibility.com/?p=183#comment-3411</guid>
		<description>Thanks for sharing the coding, Joe. Will keep that in reserve the next time I&#039;m doing a design that doesn&#039;t call for visible skip navigation.

And agreed about the issue still bearing discussion -- am very glad to see this post resurface thanks to you guys!</description>
		<content:encoded><![CDATA[<p>Thanks for sharing the coding, Joe. Will keep that in reserve the next time I&#8217;m doing a design that doesn&#8217;t call for visible skip navigation.</p>
<p>And agreed about the issue still bearing discussion &#8212; am very glad to see this post resurface thanks to you guys!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Skip Navigation by Joe Chidzik</title>
		<link>http://www.theaccessibility.com/2009/05/skip-navigation/comment-page-1/#comment-3380</link>
		<dc:creator>Joe Chidzik</dc:creator>
		<pubDate>Mon, 22 Feb 2010 10:50:54 +0000</pubDate>
		<guid isPermaLink="false">http://www.theaccessibility.com/?p=183#comment-3380</guid>
		<description>Hi Steve,

The way we have coded the skip links on our site (www.abilitynet.org.uk) is shown here on my handy wiki: http://www.wcag2wiki.com/index.php?title=WCAG2_2.4.1#Implementation

The skip link is positioned off screen, using a negative left margin of -600em. When the link receives the focus, the left margin is removed, the link becomes visible. 

I didn&#039;t realise this article was from last year when I submitted my previous response :-) It&#039;s an issue that still needs discussing though, so good it&#039;s being talked about</description>
		<content:encoded><![CDATA[<p>Hi Steve,</p>
<p>The way we have coded the skip links on our site (www.abilitynet.org.uk) is shown here on my handy wiki: <a href="http://www.wcag2wiki.com/index.php?title=WCAG2_2.4.1#Implementation" rel="nofollow">http://www.wcag2wiki.com/index.php?title=WCAG2_2.4.1#Implementation</a></p>
<p>The skip link is positioned off screen, using a negative left margin of -600em. When the link receives the focus, the left margin is removed, the link becomes visible. </p>
<p>I didn&#8217;t realise this article was from last year when I submitted my previous response <img src='http://www.theaccessibility.com/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' />  It&#8217;s an issue that still needs discussing though, so good it&#8217;s being talked about</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Skip Navigation by Joseph O'Connor</title>
		<link>http://www.theaccessibility.com/2009/05/skip-navigation/comment-page-1/#comment-3330</link>
		<dc:creator>Joseph O'Connor</dc:creator>
		<pubDate>Sun, 21 Feb 2010 03:06:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.theaccessibility.com/?p=183#comment-3330</guid>
		<description>Wrote code, it was omitted:

Should read:

also placed a direct link to portal login in div id=&quot;offleft&quot;</description>
		<content:encoded><![CDATA[<p>Wrote code, it was omitted:</p>
<p>Should read:</p>
<p>also placed a direct link to portal login in div id=&#8221;offleft&#8221;</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Skip Navigation by Joseph O'Connor</title>
		<link>http://www.theaccessibility.com/2009/05/skip-navigation/comment-page-1/#comment-3329</link>
		<dc:creator>Joseph O'Connor</dc:creator>
		<pubDate>Sun, 21 Feb 2010 03:04:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.theaccessibility.com/?p=183#comment-3329</guid>
		<description>Check out the Skip to Portal link on http://www.csun.edu - also placed a direct link to portal login in  These refinements were in response to diverse user comments during testing and first launch.</description>
		<content:encoded><![CDATA[<p>Check out the Skip to Portal link on <a href="http://www.csun.edu" rel="nofollow">http://www.csun.edu</a> &#8211; also placed a direct link to portal login in  These refinements were in response to diverse user comments during testing and first launch.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Skip Navigation by Steve</title>
		<link>http://www.theaccessibility.com/2009/05/skip-navigation/comment-page-1/#comment-3328</link>
		<dc:creator>Steve</dc:creator>
		<pubDate>Sun, 21 Feb 2010 02:27:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.theaccessibility.com/?p=183#comment-3328</guid>
		<description>Thanks to all of you for the great input. Glad to see an older - but always topical - post get some life.

Do any of you have a recommended means for doing the hidden version? I&#039;ve seen a few methods out there -- just wondering if any particular one remains the best all-around, both from a clean code and an accessible standpoint.</description>
		<content:encoded><![CDATA[<p>Thanks to all of you for the great input. Glad to see an older &#8211; but always topical &#8211; post get some life.</p>
<p>Do any of you have a recommended means for doing the hidden version? I&#8217;ve seen a few methods out there &#8212; just wondering if any particular one remains the best all-around, both from a clean code and an accessible standpoint.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Skip Navigation by Joe Chidzik</title>
		<link>http://www.theaccessibility.com/2009/05/skip-navigation/comment-page-1/#comment-3324</link>
		<dc:creator>Joe Chidzik</dc:creator>
		<pubDate>Sun, 21 Feb 2010 00:06:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.theaccessibility.com/?p=183#comment-3324</guid>
		<description>Only wanted to add to Patrick&#039;s great summing up above; in addition to using the :focus attribute to make the link visible, using the :active alongside :focus ensures that IE6\IE7 also work with this method (afaik they ignore the :focus attribute, or at least don&#039;t work with it correctly, but do work with the :active method). 

I agree that often designers are unkeen to clutter up pages with additional links, but using the method mentione, of hiding skip links, and only displaying then when they receive the focus, should make everyone happy. Keyboard users can see the link when it becomes visible, and designers have their clean homepage. 

@slger 
any more than 3 skip links is getting to be counter productive really; skip links are meant to save keypresses! And yes, better design can prevent needing these additional skip links :-)</description>
		<content:encoded><![CDATA[<p>Only wanted to add to Patrick&#8217;s great summing up above; in addition to using the :focus attribute to make the link visible, using the :active alongside :focus ensures that IE6\IE7 also work with this method (afaik they ignore the :focus attribute, or at least don&#8217;t work with it correctly, but do work with the :active method). </p>
<p>I agree that often designers are unkeen to clutter up pages with additional links, but using the method mentione, of hiding skip links, and only displaying then when they receive the focus, should make everyone happy. Keyboard users can see the link when it becomes visible, and designers have their clean homepage. </p>
<p>@slger<br />
any more than 3 skip links is getting to be counter productive really; skip links are meant to save keypresses! And yes, better design can prevent needing these additional skip links <img src='http://www.theaccessibility.com/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
</channel>
</rss>
