<?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: Misunderstanding Accessible Design</title>
	<atom:link href="http://www.joedolson.com/articles/2006/08/misunderstanding-accessible-design/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.joedolson.com/articles/2006/08/misunderstanding-accessible-design/</link>
	<description>Tips and Commentary on Web Accessibility, Usability, and Search Marketing best practices.</description>
	<pubDate>Fri, 21 Nov 2008 12:18:02 +0000</pubDate>
	<generator>http://wordpress.org/?v=abc</generator>
		<item>
		<title>By: Joe Dolson</title>
		<link>http://www.joedolson.com/articles/2006/08/misunderstanding-accessible-design/#comment-23236</link>
		<dc:creator>Joe Dolson</dc:creator>
		<pubDate>Wed, 07 Nov 2007 16:36:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.joedolson.com/articles/2006/08/misunderstanding-accessible-design/#comment-23236</guid>
		<description>Thanks, Marc. In fact, there are bookmarking icons; but they aren't made obvious. If you visit the link "Social bookmark this page," you'll have a whole array of options for social bookmarking.</description>
		<content:encoded><![CDATA[<p>Thanks, Marc. In fact, there are bookmarking icons; but they aren&#8217;t made obvious. If you visit the link &#8220;Social bookmark this page,&#8221; you&#8217;ll have a whole array of options for social&nbsp;bookmarking.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Marc Klein</title>
		<link>http://www.joedolson.com/articles/2006/08/misunderstanding-accessible-design/#comment-23235</link>
		<dc:creator>Marc Klein</dc:creator>
		<pubDate>Wed, 07 Nov 2007 04:02:34 +0000</pubDate>
		<guid isPermaLink="false">http://www.joedolson.com/articles/2006/08/misunderstanding-accessible-design/#comment-23235</guid>
		<description>Some really good info on this blog. And I fully agree with the author regards accessibilty,  CSS or XHTML. Should consider adding a bookmarking icon to this blog.</description>
		<content:encoded><![CDATA[<p>Some really good info on this blog. And I fully agree with the author regards accessibilty,  <acronym title="Cascading Style Sheets">CSS</acronym> or <acronym title="eXtensible HyperText Markup Language - HTML reformulated as XML">XHTML</acronym>. Should consider adding a bookmarking icon to this&nbsp;blog.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Web template</title>
		<link>http://www.joedolson.com/articles/2006/08/misunderstanding-accessible-design/#comment-449</link>
		<dc:creator>Web template</dc:creator>
		<pubDate>Fri, 01 Sep 2006 21:49:17 +0000</pubDate>
		<guid isPermaLink="false">http://www.joedolson.com/articles/2006/08/misunderstanding-accessible-design/#comment-449</guid>
		<description>I enjoy your articles. I will visit your blog again.

Robert</description>
		<content:encoded><![CDATA[<p>I enjoy your articles. I will visit your blog again.&nbsp;Robert</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joe Dolson</title>
		<link>http://www.joedolson.com/articles/2006/08/misunderstanding-accessible-design/#comment-332</link>
		<dc:creator>Joe Dolson</dc:creator>
		<pubDate>Mon, 21 Aug 2006 14:54:19 +0000</pubDate>
		<guid isPermaLink="false">http://www.joedolson.com/articles/2006/08/misunderstanding-accessible-design/#comment-332</guid>
		<description>Yeah, that's why I didn't go and title my post the same way!  I think that Mike Stenhouse was speaking tongue-in-cheek when he wrote that post title, however. Controversy breeds attention, after all.</description>
		<content:encoded><![CDATA[<p>Yeah, that&#8217;s why I didn&#8217;t go and title my post the same way!  I think that Mike Stenhouse was speaking tongue-in-cheek when he wrote that post title, however. Controversy breeds attention, after&nbsp;all.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike Cherim</title>
		<link>http://www.joedolson.com/articles/2006/08/misunderstanding-accessible-design/#comment-331</link>
		<dc:creator>Mike Cherim</dc:creator>
		<pubDate>Mon, 21 Aug 2006 13:22:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.joedolson.com/articles/2006/08/misunderstanding-accessible-design/#comment-331</guid>
		<description>I guess I have to agree. CSS is nothing more than a means of making an accessible X/HTML website look pretty. That's it. A few divs may be added (which are generic containers so it's all good), and maybe a few spans, which have zero meaning, even the white space between two words has more meaning than the lowly span. 

I wouldn't say CSS is worthless though in that it is a means of preventing developers from creating barriers to access by embedding presentational data into an otherwise accessible site. Some methods of styling and laying out a site, as you know, can destroy its accessibility.

If not for CSS we'd be offering some really plain Jane site or laying them with tables. Hat's off to CSS.</description>
		<content:encoded><![CDATA[<p>I guess I have to agree. <acronym title="Cascading Style Sheets">CSS</acronym> is nothing more than a means of making an accessible X/HTML website look pretty. That&#8217;s it. A few divs may be added (which are generic containers so it&#8217;s all good), and maybe a few spans, which have zero meaning, even the white space between two words has more meaning than the lowly span. </p>
<p>I wouldn&#8217;t say <acronym title="Cascading Style Sheets">CSS</acronym> is worthless though in that it is a means of preventing developers from creating barriers to access by embedding presentational data into an otherwise accessible site. Some methods of styling and laying out a site, as you know, can destroy its accessibility.</p>
<p>If not for <acronym title="Cascading Style Sheets">CSS</acronym> we&#8217;d be offering some really plain Jane site or laying them with tables. Hat&#8217;s off to&nbsp;<acronym title="Cascading Style Sheets">CSS</acronym>.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joe Dolson</title>
		<link>http://www.joedolson.com/articles/2006/08/misunderstanding-accessible-design/#comment-269</link>
		<dc:creator>Joe Dolson</dc:creator>
		<pubDate>Wed, 16 Aug 2006 02:17:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.joedolson.com/articles/2006/08/misunderstanding-accessible-design/#comment-269</guid>
		<description>Thanks for your comments (and your commendation!) I noted that you disagreed with me on one point - which I just wanted to get to, really quickly.

&lt;blockquote&gt;
I would disagree with you in that there is no way to make good html work on current web browsers without implementing CSS to allow you to have content first, etc.
&lt;/blockquote&gt;

That's true.  However, I'm not talking about design; that's one of my points.  Design is the process of creating potential barriers to access.  Semantic and correct HTML will work &lt;em&gt;flawlessly&lt;/em&gt; on all modern browsers - but it won't look very interesting.  It's CSS which we'll use to add interest and color to the design, and also to make the content &lt;em&gt;appear&lt;/em&gt; to be in the right place, when it's actually been placed lower or higher in sequence. CSS only controls the visual aspects of the page.</description>
		<content:encoded><![CDATA[<p>Thanks for your comments (and your commendation!) I noted that you disagreed with me on one point - which I just wanted to get to, really quickly.</p>
<blockquote><p>
I would disagree with you in that there is no way to make good <acronym title="HyperText Markup Language">HTML</acronym> work on current web browsers without implementing <acronym title="Cascading Style Sheets">CSS</acronym> to allow you to have content first, etc.
</p></blockquote>
<p>That&#8217;s true.  However, I&#8217;m not talking about design; that&#8217;s one of my points.  Design is the process of creating potential barriers to access.  Semantic and correct <acronym title="HyperText Markup Language">HTML</acronym> will work <em>flawlessly</em> on all modern browsers - but it won&#8217;t look very interesting.  It&#8217;s <acronym title="Cascading Style Sheets">CSS</acronym> which we&#8217;ll use to add interest and color to the design, and also to make the content <em>appear</em> to be in the right place, when it&#8217;s actually been placed lower or higher in sequence. <acronym title="Cascading Style Sheets">CSS</acronym> only controls the visual aspects of the&nbsp;page.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rob</title>
		<link>http://www.joedolson.com/articles/2006/08/misunderstanding-accessible-design/#comment-267</link>
		<dc:creator>Rob</dc:creator>
		<pubDate>Wed, 16 Aug 2006 02:11:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.joedolson.com/articles/2006/08/misunderstanding-accessible-design/#comment-267</guid>
		<description>Great blog!  I've added a link to your blog on Blog of the Day under the category of Design.  To view the feature of your blog, please visit &lt;a href="http://blogoftheday.org/page/111928" rel="nofollow"&gt;http://blogoftheday.org/page/111928&lt;/a&gt;

Please note that my site uses semantic xhtml and CSS with content first and there are icons under the category headings for re-sizing the font to make it larger for sight impaired viewers.</description>
		<content:encoded><![CDATA[<p>Great blog!  I&#8217;ve added a link to your blog on Blog of the Day under the category of Design.  To view the feature of your blog, please visit <a href="http://blogoftheday.org/page/111928">http://blogoftheday.org/page/111928</a></p>
<p>Please note that my site uses semantic <acronym title="eXtensible HyperText Markup Language - HTML reformulated as XML">XHTML</acronym> and <acronym title="Cascading Style Sheets">CSS</acronym> with content first and there are icons under the category headings for re-sizing the font to make it larger for sight impaired&nbsp;viewers.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
