<?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"
	>
<channel>
	<title>Comments on: WCAG Samurai Errata for Web Content Accessibility Guidelines (WCAG) 1.0 released</title>
	<atom:link href="http://pipwerks.com/journal/2008/02/29/wcag-samurai-errata-for-web-content-accessibility-guidelines-wcag-10-released/feed/" rel="self" type="application/rss+xml" />
	<link>http://pipwerks.com/journal/2008/02/29/wcag-samurai-errata-for-web-content-accessibility-guidelines-wcag-10-released/</link>
	<description>Philip Hutchison's technology journal, dedicated to exploring web technologies for website and e-learning development.</description>
	<pubDate>Thu, 20 Nov 2008 09:19:36 +0000</pubDate>
	<generator>http://wordpress.org/?v=abc</generator>
		<item>
		<title>By: Philip</title>
		<link>http://pipwerks.com/journal/2008/02/29/wcag-samurai-errata-for-web-content-accessibility-guidelines-wcag-10-released/#comment-245</link>
		<dc:creator>Philip</dc:creator>
		<pubDate>Fri, 29 Feb 2008 16:31:50 +0000</pubDate>
		<guid isPermaLink="false">http://pipwerks.com/journal/2008/02/29/wcag-samurai-errata-for-web-content-accessibility-guidelines-wcag-10-released/#comment-245</guid>
		<description>Hi Joe

I totally understand... but I keep crossing my fingers that someday someone will have that "a-HA!" moment and make the problems go away.  :)

The biggest issue for e-learning developers is that we HAVE to use JavaScript (it's part of the SCORM specification), and must also use either frames, an iFrame or Flash; we can't do pure HTML or else we lose the ability to keep an open communication line with the learning management system.

As accessibility-aware developer (though I know I don't do as much as I should), this has always pained me.

BTW, thank you very much for all the work you've done (and fights you've fought). I appreciate it.</description>
		<content:encoded><![CDATA[<p>Hi Joe</p>
<p>I totally understand&#8230; but I keep crossing my fingers that someday someone will have that &#8220;a-HA!&#8221; moment and make the problems go away.  <img src='http://pipwerks.com/journal/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>The biggest issue for e-learning developers is that we HAVE to use JavaScript (it&#8217;s part of the SCORM specification), and must also use either frames, an iFrame or Flash; we can&#8217;t do pure HTML or else we lose the ability to keep an open communication line with the learning management system.</p>
<p>As accessibility-aware developer (though I know I don&#8217;t do as much as I should), this has always pained me.</p>
<p>BTW, thank you very much for all the work you&#8217;ve done (and fights you&#8217;ve fought). I appreciate it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joe Clark</title>
		<link>http://pipwerks.com/journal/2008/02/29/wcag-samurai-errata-for-web-content-accessibility-guidelines-wcag-10-released/#comment-244</link>
		<dc:creator>Joe Clark</dc:creator>
		<pubDate>Fri, 29 Feb 2008 14:30:13 +0000</pubDate>
		<guid isPermaLink="false">http://pipwerks.com/journal/2008/02/29/wcag-samurai-errata-for-web-content-accessibility-guidelines-wcag-10-released/#comment-244</guid>
		<description>Well, the problem with guidelines for Ajax is that JavaScript is a programming language with umpteen possible manifestations. There are various blog posts and entire books about responsible scripting.</description>
		<content:encoded><![CDATA[<p>Well, the problem with guidelines for Ajax is that JavaScript is a programming language with umpteen possible manifestations. There are various blog posts and entire books about responsible scripting.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
