<?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: Understand Web Content Accessibility Guidelines &amp; Section 508</title>
	<atom:link href="http://www.michaelgaigg.com/blog/2008/11/01/understand-web-content-accessibility-guidelines-section-508/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.michaelgaigg.com/blog/2008/11/01/understand-web-content-accessibility-guidelines-section-508/</link>
	<description>Web Design Guidelines and Tips</description>
	<lastBuildDate>Wed, 21 Jul 2010 16:07:23 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: Michael Gaigg</title>
		<link>http://www.michaelgaigg.com/blog/2008/11/01/understand-web-content-accessibility-guidelines-section-508/comment-page-1/#comment-684</link>
		<dc:creator>Michael Gaigg</dc:creator>
		<pubDate>Fri, 26 Feb 2010 15:57:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.michaelgaigg.com/blog/?p=97#comment-684</guid>
		<description>&lt;a href=&quot;#comment-679&quot; rel=&quot;nofollow&quot;&gt;@Debbie &lt;/a&gt; 
That&#039;s a good question which I hear a lot. The answer is absolutely not! There is no need to sacrifice aesthetics over accessibility. Now, I don&#039;t know what you mean by &#039;fancy&#039;, I assume fly-out-menus or similar, a) consider simplifying your menu structure, b) use structural markup, like unordered list, and c) style the whole menu structure using CSS.</description>
		<content:encoded><![CDATA[<p><a href="#comment-679" rel="nofollow">@Debbie </a><br />
That&#8217;s a good question which I hear a lot. The answer is absolutely not! There is no need to sacrifice aesthetics over accessibility. Now, I don&#8217;t know what you mean by &#8216;fancy&#8217;, I assume fly-out-menus or similar, a) consider simplifying your menu structure, b) use structural markup, like unordered list, and c) style the whole menu structure using CSS.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bebe Angelic</title>
		<link>http://www.michaelgaigg.com/blog/2008/11/01/understand-web-content-accessibility-guidelines-section-508/comment-page-1/#comment-683</link>
		<dc:creator>Bebe Angelic</dc:creator>
		<pubDate>Fri, 26 Feb 2010 08:27:16 +0000</pubDate>
		<guid isPermaLink="false">http://www.michaelgaigg.com/blog/?p=97#comment-683</guid>
		<description>Nice article..I tell my friend to read this and bookmark..</description>
		<content:encoded><![CDATA[<p>Nice article..I tell my friend to read this and bookmark..</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Teijin</title>
		<link>http://www.michaelgaigg.com/blog/2008/11/01/understand-web-content-accessibility-guidelines-section-508/comment-page-1/#comment-682</link>
		<dc:creator>Teijin</dc:creator>
		<pubDate>Fri, 26 Feb 2010 08:11:17 +0000</pubDate>
		<guid isPermaLink="false">http://www.michaelgaigg.com/blog/?p=97#comment-682</guid>
		<description>Nice article..I tell my friend to read this and bookmark..</description>
		<content:encoded><![CDATA[<p>Nice article..I tell my friend to read this and bookmark..</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Debbie</title>
		<link>http://www.michaelgaigg.com/blog/2008/11/01/understand-web-content-accessibility-guidelines-section-508/comment-page-1/#comment-679</link>
		<dc:creator>Debbie</dc:creator>
		<pubDate>Thu, 25 Feb 2010 20:52:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.michaelgaigg.com/blog/?p=97#comment-679</guid>
		<description>I&#039;m researching navigational options for a redesign. I am looking for advice. I&#039;m considering using fancy navigation which does not seem to be &quot;reader&quot; accessible.

Should the navigation be scraped for an accessible version
 - or - 
Could a site map serve as a text only or accessible link prior to fancy navigation for a &quot;reader&quot; (Jaws in my case) alternative?</description>
		<content:encoded><![CDATA[<p>I&#8217;m researching navigational options for a redesign. I am looking for advice. I&#8217;m considering using fancy navigation which does not seem to be &#8220;reader&#8221; accessible.</p>
<p>Should the navigation be scraped for an accessible version<br />
 &#8211; or &#8211;<br />
Could a site map serve as a text only or accessible link prior to fancy navigation for a &#8220;reader&#8221; (Jaws in my case) alternative?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
