<?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: Accessibility and Usability issues with AJAX</title>
	<atom:link href="http://www.joedolson.com/articles/2007/10/accessibility-and-usability-issues-with-ajax/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.joedolson.com/articles/2007/10/accessibility-and-usability-issues-with-ajax/</link>
	<description>Tips and Commentary on Web Accessibility, Usability, and Search Marketing best practices.</description>
	<lastBuildDate>Tue, 07 Feb 2012 10:51:13 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=</generator>
<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
	<item>
		<title>By: Joe Dolson</title>
		<link>http://www.joedolson.com/articles/2007/10/accessibility-and-usability-issues-with-ajax/comment-page-1/#comment-22525</link>
		<dc:creator>Joe Dolson</dc:creator>
		<pubDate>Wed, 17 Oct 2007 15:36:34 +0000</pubDate>
		<guid isPermaLink="false">http://www.joedolson.com/articles/2007/10/accessibility-and-usability-issues-with-ajax/#comment-22525</guid>
		<description>Thanks, Christopher. 

Personally, I consider it to be a shift beyond accessibility; the alternate version needs to be available just to make the interface seriously &lt;em&gt;usable&lt;/em&gt;. Granted, that may be an extreme interpretation... :)</description>
		<content:encoded><![CDATA[<p>Thanks,&nbsp;Christopher. </p>
<p>Personally, I consider it to be a shift beyond accessibility; the alternate version needs to be available just to make the interface seriously <em>usable</em>. Granted, that may be an extreme interpretation&#8230; <img src='http://www.joedolson.com/articles/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Christopher Phillips</title>
		<link>http://www.joedolson.com/articles/2007/10/accessibility-and-usability-issues-with-ajax/comment-page-1/#comment-22507</link>
		<dc:creator>Christopher Phillips</dc:creator>
		<pubDate>Wed, 17 Oct 2007 04:26:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.joedolson.com/articles/2007/10/accessibility-and-usability-issues-with-ajax/#comment-22507</guid>
		<description>Thank you for a very reasonable overview. I appreciated the examples of how different groups might be affected. It is interesting as Mike notes, how Web 2.0 ajaxian interfaces may actually require a step backward in forcing the addition of an accessible version of a page.</description>
		<content:encoded><![CDATA[<p>Thank you for a very reasonable overview. I appreciated the examples of how different groups might be affected. It is interesting as Mike notes, how Web 2.0 ajaxian interfaces may actually require a step backward in forcing the addition of an accessible version of a&nbsp;page.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joe Dolson</title>
		<link>http://www.joedolson.com/articles/2007/10/accessibility-and-usability-issues-with-ajax/comment-page-1/#comment-22475</link>
		<dc:creator>Joe Dolson</dc:creator>
		<pubDate>Tue, 16 Oct 2007 05:20:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.joedolson.com/articles/2007/10/accessibility-and-usability-issues-with-ajax/#comment-22475</guid>
		<description>I like that...it&#039;s got a nice ring to it! ;)

It&#039;s really a pretty straightforward concept...it&#039;s just a matter of being alert to the issues associated with accessible interfaces, I think. Education, education, education...</description>
		<content:encoded><![CDATA[<p>I like that&#8230;it&#8217;s got a nice ring to it! <img src='http://www.joedolson.com/articles/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' /> </p>
<p>It&#8217;s really a pretty straightforward concept&#8230;it&#8217;s just a matter of being alert to the issues associated with accessible interfaces, I think. Education, education,&nbsp;education&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike Cherim</title>
		<link>http://www.joedolson.com/articles/2007/10/accessibility-and-usability-issues-with-ajax/comment-page-1/#comment-22473</link>
		<dc:creator>Mike Cherim</dc:creator>
		<pubDate>Tue, 16 Oct 2007 03:56:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.joedolson.com/articles/2007/10/accessibility-and-usability-issues-with-ajax/#comment-22473</guid>
		<description>You pretty much hit the nail on the head when you suggested an alternative or option has be offered (be it a special mode or a different content delivery method). A one-size fits-all solution is next to impossible, and putting all of the functionality (of something like Flickr) and accessibility on one page will likely ruin the site for both. What&#039;s need is big &quot;Accessibility Mode&quot; link to a sister interface drawing from the same database, but with a lot less inaccessible functionality.

In the words of the WCAG 1: When you can&#039;t &lt;a href=&quot;http://www.w3.org/TR/WAI-WEBCONTENT/#tech-dynamic-source&quot;&gt;6.2&lt;/a&gt;, then you better &lt;a href=&quot;http://www.w3.org/TR/WAI-WEBCONTENT/#tech-alt-pages&quot;&gt;11.4&lt;/a&gt;. ;-)</description>
		<content:encoded><![CDATA[<p>You pretty much hit the nail on the head when you suggested an alternative or option has be offered (be it a special mode or a different content delivery method). A one-size fits-all solution is next to impossible, and putting all of the functionality (of something like Flickr) and accessibility on one page will likely ruin the site for both. What&#8217;s need is big &#8220;Accessibility Mode&#8221; link to a sister interface drawing from the same database, but with a lot less inaccessible&nbsp;functionality.</p>
<p>In the words of the <abbr title="Web Content Accessibility Guidelines">WCAG</abbr> 1: When you can&#8217;t <a href="http://www.w3.org/TR/WAI-WEBCONTENT/#tech-dynamic-source">6.2</a>, then you better <a href="http://www.w3.org/TR/WAI-WEBCONTENT/#tech-alt-pages">11.4</a>. <img src='http://www.joedolson.com/articles/wp-includes/images/smilies/icon_wink.gif' alt=';-)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joe Dolson</title>
		<link>http://www.joedolson.com/articles/2007/10/accessibility-and-usability-issues-with-ajax/comment-page-1/#comment-22448</link>
		<dc:creator>Joe Dolson</dc:creator>
		<pubDate>Mon, 15 Oct 2007 16:41:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.joedolson.com/articles/2007/10/accessibility-and-usability-issues-with-ajax/#comment-22448</guid>
		<description>Honestly, that&#039;s just a fundamental principle which I chose to assume. Any Javascript development should be approached in that manner. That doesn&#039;t change the fact that the Javascript-based enhancements to the interface should be carefully planned to be as usable and accessible as possible. Simply making it usable when Javascript isn&#039;t available is insufficient, since there are many users who will have Javascript available --- but not in a manner which will allow them to use the feature.

(I&#039;m adding a note to the top of the article, however, to clarify this.)</description>
		<content:encoded><![CDATA[<p>Honestly, that&#8217;s just a fundamental principle which I chose to assume. Any Javascript development should be approached in that manner. That doesn&#8217;t change the fact that the Javascript-based enhancements to the interface should be carefully planned to be as usable and accessible as possible. Simply making it usable when Javascript isn&#8217;t available is insufficient, since there are many users who will have Javascript available&thinsp;&#8212;&thinsp;- but not in a manner which will allow them to use the&nbsp;feature.</p>
<p>(I&#8217;m adding a note to the top of the article, however, to clarify&nbsp;this.)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: marc mcneill</title>
		<link>http://www.joedolson.com/articles/2007/10/accessibility-and-usability-issues-with-ajax/comment-page-1/#comment-22447</link>
		<dc:creator>marc mcneill</dc:creator>
		<pubDate>Mon, 15 Oct 2007 16:31:22 +0000</pubDate>
		<guid isPermaLink="false">http://www.joedolson.com/articles/2007/10/accessibility-and-usability-issues-with-ajax/#comment-22447</guid>
		<description>Interesting article, but how about designing without the javascript goodness first, and layering on later as with progressive enhancement. 
http://en.wikipedia.org/wiki/Progressive_enhancement</description>
		<content:encoded><![CDATA[<p>Interesting article, but how about designing without the javascript goodness first, and layering on later as with progressive enhancement.<br />&nbsp;<a href="http://en.wikipedia.org/wiki/Progressive_enhancement" rel="nofollow">http://en.wikipedia.org/wiki/Progressive_enhancement</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>

