<?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: Working with content to increase accessibility</title>
	<atom:link href="http://www.standards-schmandards.com/2004/working-with-content-to-increase-accessibility/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.standards-schmandards.com/2004/working-with-content-to-increase-accessibility/</link>
	<description>A pragmatic approach to web standards and accessibility</description>
	<lastBuildDate>Mon, 06 Sep 2010 14:21:31 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: Rich</title>
		<link>http://www.standards-schmandards.com/2004/working-with-content-to-increase-accessibility/comment-page-1/#comment-133</link>
		<dc:creator>Rich</dc:creator>
		<pubDate>Mon, 09 May 2005 19:59:53 +0000</pubDate>
		<guid isPermaLink="false">http://localhost:8888/?p=4#comment-133</guid>
		<description>&lt;p&gt;Ah yes, and it really is all about content. And what happens when that content is inherently visual, or symbolic (mathematics or other domain-specific material such as chemical formuli)?&lt;/p&gt; &lt;p&gt;The point is that ultimately, we are trying to deliver content here. Yes, its important to be able to navigate the site structure efficiently in order to find the content we are looking for, but if that content is by its nature inaccessible, then what have we accomploshed?&lt;/p&gt;</description>
		<content:encoded><![CDATA[<p>Ah yes, and it really is all about content. And what happens when that content is inherently visual, or symbolic (mathematics or other domain-specific material such as chemical formuli)?</p>
<p>The point is that ultimately, we are trying to deliver content here. Yes, its important to be able to navigate the site structure efficiently in order to find the content we are looking for, but if that content is by its nature inaccessible, then what have we accomploshed?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David</title>
		<link>http://www.standards-schmandards.com/2004/working-with-content-to-increase-accessibility/comment-page-1/#comment-67</link>
		<dc:creator>David</dc:creator>
		<pubDate>Wed, 19 Jan 2005 16:30:10 +0000</pubDate>
		<guid isPermaLink="false">http://localhost:8888/?p=4#comment-67</guid>
		<description>&lt;p&gt;Hi,&lt;/p&gt; &lt;p&gt;I am not sure the standards advocate bashing is fair. No doubt there are purists out there, but most do not tend to say validation is end all.&lt;/p&gt; &lt;p&gt;Most do, from what I can see, say that validation and standards compliant are very important. But, as you have noted, semantics can be poor even in valid documents.&lt;/p&gt; &lt;p&gt;I think most standards evangelists do recognize that. My understanding from reading a number of major evangelists is that they&lt;/p&gt; &lt;p&gt;1) preach standards as the starting point;&lt;/p&gt; &lt;p&gt;2) emphasize semantically meaningful markup as critical for accessibility, and&lt;/p&gt; &lt;p&gt;3) additional accessibility considerations are needed on top of valid markup and good semantic tag choice (such as good content).&lt;/p&gt;</description>
		<content:encoded><![CDATA[<p>Hi,</p>
<p>I am not sure the standards advocate bashing is fair. No doubt there are purists out there, but most do not tend to say validation is end all.</p>
<p>Most do, from what I can see, say that validation and standards compliant are very important. But, as you have noted, semantics can be poor even in valid documents.</p>
<p>I think most standards evangelists do recognize that. My understanding from reading a number of major evangelists is that they</p>
<p>1) preach standards as the starting point;</p>
<p>2) emphasize semantically meaningful markup as critical for accessibility, and</p>
<p>3) additional accessibility considerations are needed on top of valid markup and good semantic tag choice (such as good content).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Amit Karmakar</title>
		<link>http://www.standards-schmandards.com/2004/working-with-content-to-increase-accessibility/comment-page-1/#comment-52</link>
		<dc:creator>Amit Karmakar</dc:creator>
		<pubDate>Mon, 03 Jan 2005 11:09:07 +0000</pubDate>
		<guid isPermaLink="false">http://localhost:8888/?p=4#comment-52</guid>
		<description>&lt;p&gt;So very true and a very nice post! There are stacks of people out there who think jumping on the xhtml band-wagon will have their site accessible totally. I like your scond point very much and it is the crux of everything really. Simple and clear! This is where a lot of them go wrong!&lt;/p&gt;</description>
		<content:encoded><![CDATA[<p>So very true and a very nice post! There are stacks of people out there who think jumping on the xhtml band-wagon will have their site accessible totally. I like your scond point very much and it is the crux of everything really. Simple and clear! This is where a lot of them go wrong!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
