<?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: Useful Tools for validating HTML, CSS and Accessibility</title>
	<atom:link href="http://www.ruelicke.net/2007/09/15/useful-tools-for-validating-html-css-and-accessibility/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.ruelicke.net/2007/09/15/useful-tools-for-validating-html-css-and-accessibility/</link>
	<description>...when coding passion, gaming addiction, Internet surfing syndrome and the real life collide...</description>
	<lastBuildDate>Tue, 12 Apr 2011 07:03:09 +0200</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: Marco</title>
		<link>http://www.ruelicke.net/2007/09/15/useful-tools-for-validating-html-css-and-accessibility/comment-page-1/#comment-77</link>
		<dc:creator>Marco</dc:creator>
		<pubDate>Mon, 17 Sep 2007 21:15:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.ruelicke.net/2007/09/useful-tools-for-validating-html-css-and-accessibility/#comment-77</guid>
		<description>goldfries - I believe it is also possible to get a standalone HTML Tidy, but I&#039;m not sure. Also, the HTML Validator can cause some confusion because it also checks frames (even if included via JavaScript, like GoogleAds!) so sometimes it doesn&#039;t validate although your actual page code is ok. That&#039;s what happened to me when I checked your page. It turned out that the malformed URL was the only invalid part of your page.
I apologize for my statement on this in my comment at Michael&#039;s Pro Blog Design.</description>
		<content:encoded><![CDATA[<p>goldfries &#8211; I believe it is also possible to get a standalone HTML Tidy, but I&#8217;m not sure. Also, the HTML Validator can cause some confusion because it also checks frames (even if included via JavaScript, like GoogleAds!) so sometimes it doesn&#8217;t validate although your actual page code is ok. That&#8217;s what happened to me when I checked your page. It turned out that the malformed URL was the only invalid part of your page.<br />
I apologize for my statement on this in my comment at Michael&#8217;s Pro Blog Design.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: goldfries</title>
		<link>http://www.ruelicke.net/2007/09/15/useful-tools-for-validating-html-css-and-accessibility/comment-page-1/#comment-76</link>
		<dc:creator>goldfries</dc:creator>
		<pubDate>Mon, 17 Sep 2007 20:15:14 +0000</pubDate>
		<guid isPermaLink="false">http://www.ruelicke.net/2007/09/useful-tools-for-validating-html-css-and-accessibility/#comment-76</guid>
		<description>Ahh, thank you.

I have Chris Pederick&#039;s extension on my FF for quite a while now. Marc Gueury&#039;s is new to me, I will check it out. :) It&#039;ll be great to have an off-line validator.

My connection to W3C server is pretty slow sometimes so this will definitely be helpful.</description>
		<content:encoded><![CDATA[<p>Ahh, thank you.</p>
<p>I have Chris Pederick&#8217;s extension on my FF for quite a while now. Marc Gueury&#8217;s is new to me, I will check it out. <img src='http://www.ruelicke.net/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' />  It&#8217;ll be great to have an off-line validator.</p>
<p>My connection to W3C server is pretty slow sometimes so this will definitely be helpful.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael from Pro Blog Design</title>
		<link>http://www.ruelicke.net/2007/09/15/useful-tools-for-validating-html-css-and-accessibility/comment-page-1/#comment-75</link>
		<dc:creator>Michael from Pro Blog Design</dc:creator>
		<pubDate>Mon, 17 Sep 2007 18:17:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.ruelicke.net/2007/09/useful-tools-for-validating-html-css-and-accessibility/#comment-75</guid>
		<description>Fair enough. The W3C one usually does take a few seconds to load (Though I love how the favicon is enough to tell you if you passed or failed! :D )</description>
		<content:encoded><![CDATA[<p>Fair enough. The W3C one usually does take a few seconds to load (Though I love how the favicon is enough to tell you if you passed or failed! <img src='http://www.ruelicke.net/wp-includes/images/smilies/icon_biggrin.gif' alt=':D' class='wp-smiley' />  )</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Marco</title>
		<link>http://www.ruelicke.net/2007/09/15/useful-tools-for-validating-html-css-and-accessibility/comment-page-1/#comment-74</link>
		<dc:creator>Marco</dc:creator>
		<pubDate>Sun, 16 Sep 2007 19:21:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.ruelicke.net/2007/09/useful-tools-for-validating-html-css-and-accessibility/#comment-74</guid>
		<description>Michael - I use the HTML Validator before using the W3C one because that way I can test minor changes without having to load the W3C validator.

Slevi - I don&#039;t use Browsershots often, that&#039;s why I didn&#039;t mention it here. If I got a page done, I use it every now and then though :)</description>
		<content:encoded><![CDATA[<p>Michael &#8211; I use the HTML Validator before using the W3C one because that way I can test minor changes without having to load the W3C validator.</p>
<p>Slevi &#8211; I don&#8217;t use Browsershots often, that&#8217;s why I didn&#8217;t mention it here. If I got a page done, I use it every now and then though <img src='http://www.ruelicke.net/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Slevi</title>
		<link>http://www.ruelicke.net/2007/09/15/useful-tools-for-validating-html-css-and-accessibility/comment-page-1/#comment-73</link>
		<dc:creator>Slevi</dc:creator>
		<pubDate>Sun, 16 Sep 2007 18:00:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.ruelicke.net/2007/09/useful-tools-for-validating-html-css-and-accessibility/#comment-73</guid>
		<description>Nice entry, another great thing just to check out in the end is &lt;a href=&quot;http://browsershots.org/&quot; rel=&quot;nofollow&quot;&gt;Browsershots&lt;/a&gt;, it&#039;s not really a code validator but it&#039;s a great way to have a visual confirmation as well on how it works on different systems.</description>
		<content:encoded><![CDATA[<p>Nice entry, another great thing just to check out in the end is <a href="http://browsershots.org/">Browsershots</a>, it&#8217;s not really a code validator but it&#8217;s a great way to have a visual confirmation as well on how it works on different systems.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael from Pro Blog Design</title>
		<link>http://www.ruelicke.net/2007/09/15/useful-tools-for-validating-html-css-and-accessibility/comment-page-1/#comment-72</link>
		<dc:creator>Michael from Pro Blog Design</dc:creator>
		<pubDate>Sun, 16 Sep 2007 12:28:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.ruelicke.net/2007/09/useful-tools-for-validating-html-css-and-accessibility/#comment-72</guid>
		<description>Good post Marco. I use the W3C validators and the Web Developer extension as well. I haven&#039;t tried out the other extension you mentioned, but someday... :D</description>
		<content:encoded><![CDATA[<p>Good post Marco. I use the W3C validators and the Web Developer extension as well. I haven&#8217;t tried out the other extension you mentioned, but someday&#8230; <img src='http://www.ruelicke.net/wp-includes/images/smilies/icon_biggrin.gif' alt=':D' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
</channel>
</rss>

