<?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: Best Practices in Web Development: Part 4</title>
	<atom:link href="http://www.joedolson.com/articles/2008/09/best-practices-in-web-development-part-4/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.joedolson.com/articles/2008/09/best-practices-in-web-development-part-4/</link>
	<description>Tips and Commentary on Web Accessibility, Usability, and Search Marketing best practices.</description>
	<pubDate>Wed, 07 Jan 2009 10:23:55 +0000</pubDate>
	<generator>http://wordpress.org/?v=abc</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Gaming YouTube</title>
		<link>http://www.joedolson.com/articles/2008/09/best-practices-in-web-development-part-4/comment-page-1/#comment-28959</link>
		<dc:creator>Gaming YouTube</dc:creator>
		<pubDate>Tue, 04 Nov 2008 11:15:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.joedolson.com/articles/?p=278#comment-28959</guid>
		<description>I think all too often web designers are a little too narrow minded about the design of their site, and forget to take into account the user experience from the perspective from someone who has never been to your site before and knows nothing about it. Sometimes it's hard to get that perspective.</description>
		<content:encoded><![CDATA[<p>I think all too often web designers are a little too narrow minded about the design of their site, and forget to take into account the user experience from the perspective from someone who has never been to your site before and knows nothing about it. Sometimes it&#8217;s hard to get that&nbsp;perspective.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joe Dolson</title>
		<link>http://www.joedolson.com/articles/2008/09/best-practices-in-web-development-part-4/comment-page-1/#comment-26971</link>
		<dc:creator>Joe Dolson</dc:creator>
		<pubDate>Thu, 04 Sep 2008 18:10:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.joedolson.com/articles/?p=278#comment-26971</guid>
		<description>But I wouldn't view those as design elements - a paragraph is structural, indicating a break in the continuing flow of the text. You may be hoping for &lt;code&gt;em&lt;/code&gt; to generate italicized text, but you &lt;em&gt;haven't&lt;/em&gt; specified that you want italics: simply that you want emphasis. That, again, is a structural indication -- the use of italics to represent it is a separate issue.

These elements both have a function outside of the visual design representation: they provide information for other user-agents to help communicate the information more effectively. 

That's part of the illusion of design: people frequently believe that they're adding paragraph tags (or emphasis, etc.) in order to create a visually separated block of text, when actually the purpose of the element is to create a paragraph, regardless of the visual presentation of that text. It's still machine-readable as a paragraph even if the designer has (foolishly) chosen to collapse the margins and padding on all paragraphs. The visual designer has broken the paradigm of a paragraph for visual users, but screen readers will still gain the benefit.

Thanks for your comments, Jennifer!</description>
		<content:encoded><![CDATA[<p>But I wouldn&#8217;t view those as design elements - a paragraph is structural, indicating a break in the continuing flow of the text. You may be hoping for <code>em</code> to generate italicized text, but you <em>haven&#8217;t</em> specified that you want italics: simply that you want emphasis. That, again, is a structural indication&thinsp;&#8212;&thinsp;the use of italics to represent it is a separate issue.</p>
<p>These elements both have a function outside of the visual design representation: they provide information for other user-agents to help communicate the information more effectively. </p>
<p>That&#8217;s part of the illusion of design: people frequently believe that they&#8217;re adding paragraph tags (or emphasis, etc.) in order to create a visually separated block of text, when actually the purpose of the element is to create a paragraph, regardless of the visual presentation of that text. It&#8217;s still machine-readable as a paragraph even if the designer has (foolishly) chosen to collapse the margins and padding on all paragraphs. The visual designer has broken the paradigm of a paragraph for visual users, but screen readers will still gain the benefit.</p>
<p>Thanks for your comments,&nbsp;Jennifer!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jennifer Kyrnin</title>
		<link>http://www.joedolson.com/articles/2008/09/best-practices-in-web-development-part-4/comment-page-1/#comment-26958</link>
		<dc:creator>Jennifer Kyrnin</dc:creator>
		<pubDate>Thu, 04 Sep 2008 04:07:14 +0000</pubDate>
		<guid isPermaLink="false">http://www.joedolson.com/articles/?p=278#comment-26958</guid>
		<description>Great article. I'm still not convinced that it's 100% possible to separate content from design. Granted, you said "separate &lt;em&gt;structure&lt;/em&gt; from design", but I'm not convinced that's really possible either. I agree it's something good to strive for, but ultimately impossible. 

Why? Because whenever you try to get someone to post content sans design elements, they can't. For example, even here, I've added paragraph spaces (assuming they show up in the comment), em tags for emphasis which I'm hoping will show up as italics, and so on. 

When I worked as a CMS designer, I was always striving to find the "perfect" input form. This would be the form that was easy to use, but took all the design away from the writers. In one horrible iteration, we had an article form that was built one paragraph at a time. And my content authors would paste in entire Word docs into the first paragraph field. When we explained they had to do it paragraph by paragraph, they rebelled. So in that instance, we had created a fully separated content/design system. But the people involved wouldn't use it.</description>
		<content:encoded><![CDATA[<p>Great article. I&#8217;m still not convinced that it&#8217;s 100% possible to separate content from design. Granted, you said &#8220;separate <em>structure</em> from design&#8221;, but I&#8217;m not convinced that&#8217;s really possible either. I agree it&#8217;s something good to strive for, but ultimately impossible. </p>
<p>Why? Because whenever you try to get someone to post content sans design elements, they can&#8217;t. For example, even here, I&#8217;ve added paragraph spaces (assuming they show up in the comment), em tags for emphasis which I&#8217;m hoping will show up as italics, and so on. </p>
<p>When I worked as a <acronym title="Content Management System">CMS</acronym> designer, I was always striving to find the &#8220;perfect&#8221; input form. This would be the form that was easy to use, but took all the design away from the writers. In one horrible iteration, we had an article form that was built one paragraph at a time. And my content authors would paste in entire Word docs into the first paragraph field. When we explained they had to do it paragraph by paragraph, they rebelled. So in that instance, we had created a fully separated content/design system. But the people involved wouldn&#8217;t use&nbsp;it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joe Dolson</title>
		<link>http://www.joedolson.com/articles/2008/09/best-practices-in-web-development-part-4/comment-page-1/#comment-26949</link>
		<dc:creator>Joe Dolson</dc:creator>
		<pubDate>Wed, 03 Sep 2008 19:44:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.joedolson.com/articles/?p=278#comment-26949</guid>
		<description>Depends on what you mean by "pre-built systems." There's nothing inherently wrong with using a CMS, if that's what you mean - you simply need to be prepared to work on the output code and make sure that you're giving the end-user what you intend. 

The use of freely-available themes (such as with Wordpress) does lead to a lot of low-quality code -- but the greater concern is professionals who aren't paying close attention to what they send out.</description>
		<content:encoded><![CDATA[<p>Depends on what you mean by &#8220;pre-built systems.&#8221; There&#8217;s nothing inherently wrong with using a <acronym title="Content Management System">CMS</acronym>, if that&#8217;s what you mean - you simply need to be prepared to work on the output code and make sure that you&#8217;re giving the end-user what you intend. </p>
<p>The use of freely-available themes (such as with Wordpress) does lead to a lot of low-quality code&thinsp;&#8212;&thinsp;but the greater concern is professionals who aren&#8217;t paying close attention to what they send&nbsp;out.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: neil</title>
		<link>http://www.joedolson.com/articles/2008/09/best-practices-in-web-development-part-4/comment-page-1/#comment-26947</link>
		<dc:creator>neil</dc:creator>
		<pubDate>Wed, 03 Sep 2008 17:57:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.joedolson.com/articles/?p=278#comment-26947</guid>
		<description>when it comes to actually building the website i find a lot of people use pre built systems. this is poor quality in my opinion</description>
		<content:encoded><![CDATA[<p>when it comes to actually building the website i find a lot of people use pre built systems. this is poor quality in my&nbsp;opinion</p>
]]></content:encoded>
	</item>
</channel>
</rss>
