<?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: WCAG 2.0 Release Candidate 5 of 5: Summary</title>
	<atom:link href="http://www.thepickards.co.uk/index.php/200805/wcag-20-release-candidate-5-of-5-summary/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.thepickards.co.uk/index.php/200805/wcag-20-release-candidate-5-of-5-summary/</link>
	<description>ranting and rambling to anyone willing to listen</description>
	<lastBuildDate>Sat, 11 Feb 2012 17: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: Steven Clark</title>
		<link>http://www.thepickards.co.uk/index.php/200805/wcag-20-release-candidate-5-of-5-summary/comment-page-1/#comment-31738</link>
		<dc:creator>Steven Clark</dc:creator>
		<pubDate>Sun, 08 Jun 2008 06:14:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.thepickards.co.uk/?p=605#comment-31738</guid>
		<description>Thanks for posting this series. Like you I was very critical in 2006 and basically just ignored WCAG 2.0 until it became a Release Candidate. It appears vastly improved.

While I can appreciate the technology agnostic approach, its a shame that validation and a lot of that specific HTML stuff from WCAG 1.0 had to go... but I see the point I guess.

I think an important thing on a personal level (not technology agnostic) its our job to create quality software. That&#039;s where semantic markup and validation come to the fore. Although these things aren&#039;t specifically required they do, I&#039;d suggest, mean the difference between quality software and crap. For example, although its not in WCAG its still bad practice to write obfuscated unmaintainable inefficient code... its just not a WCAG issue necessarily. So I&#039;ve reconciled that issue in my own head now.

I appreciate the time and effort you&#039;ve taken to write these five articles. Excellent work.</description>
		<content:encoded><![CDATA[<p>Thanks for posting this series. Like you I was very critical in 2006 and basically just ignored WCAG 2.0 until it became a Release Candidate. It appears vastly improved.</p>
<p>While I can appreciate the technology agnostic approach, its a shame that validation and a lot of that specific HTML stuff from WCAG 1.0 had to go&#8230; but I see the point I guess.</p>
<p>I think an important thing on a personal level (not technology agnostic) its our job to create quality software. That&#8217;s where semantic markup and validation come to the fore. Although these things aren&#8217;t specifically required they do, I&#8217;d suggest, mean the difference between quality software and crap. For example, although its not in WCAG its still bad practice to write obfuscated unmaintainable inefficient code&#8230; its just not a WCAG issue necessarily. So I&#8217;ve reconciled that issue in my own head now.</p>
<p>I appreciate the time and effort you&#8217;ve taken to write these five articles. Excellent work.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

