<?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: Why Web Standards?</title>
	<atom:link href="http://bigsweaterdesign.com/2007/12/17/why-web-standards/feed/" rel="self" type="application/rss+xml" />
	<link>http://bigsweaterdesign.com/2007/12/17/why-web-standards/</link>
	<description>The Online Portfolio of Vincent Maglione</description>
	<pubDate>Tue, 06 Jan 2009 21:13:15 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Vincent</title>
		<link>http://bigsweaterdesign.com/2007/12/17/why-web-standards/comment-page-1/#comment-256</link>
		<dc:creator>Vincent</dc:creator>
		<pubDate>Tue, 08 Apr 2008 20:33:17 +0000</pubDate>
		<guid isPermaLink="false">http://bigsweaterdesign.com/2007/12/17/why-web-standards/#comment-256</guid>
		<description>Yep&#8212;the design should honor the content, like Bringhurst says. No question about that.

The whole "breaks our designs" argument from more traditional designers sort of makes me laugh a little bit. The forum post above was aimed at a print designer&#8212;a talented one at that&#8212;who had argued against the use of standards because it's easier and faster to use tables, and sites display more accurately when using tables. But the fact is, the web is a &lt;em&gt;completely&lt;/em&gt; different medium than more traditional design mediums. Accessibility doesn't break design; it just adds one more constraint through which we have to work. A great designer can work accessibility and standards into his or her site without sacrificing aesthetics, as we've seen time and time again. 

Interesting&#8212;I spotted that noupe.com article after seeing it in my Analytics account, but didn't get more than ten or fifteen hits from it. Then, yesterday, I almost got 200. They must've been dugg. </description>
		<content:encoded><![CDATA[<p>Yep&thinsp;&mdash;&thinsp;the design should honor the content, like Bringhurst says. No question about that.</p>
<p>The whole "breaks our designs" argument from more traditional designers sort of makes me laugh a little bit. The forum post above was aimed at a print designer&thinsp;&mdash;&thinsp;a talented one at that&thinsp;&mdash;&thinsp;who had argued against the use of standards because it's easier and faster to use tables, and sites display more accurately when using tables. But the fact is, the web is a <em>completely</em> different medium than more traditional design mediums. Accessibility doesn't break design; it just adds one more constraint through which we have to work. A great designer can work accessibility and standards into his or her site without sacrificing aesthetics, as we've seen time and time again. </p>
<p>Interesting&thinsp;&mdash;&thinsp;I spotted that noupe.com article after seeing it in my Analytics account, but didn't get more than ten or fifteen hits from it. Then, yesterday, I almost got 200. They must've been&nbsp;dugg.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dickson Fong</title>
		<link>http://bigsweaterdesign.com/2007/12/17/why-web-standards/comment-page-1/#comment-255</link>
		<dc:creator>Dickson Fong</dc:creator>
		<pubDate>Tue, 08 Apr 2008 01:28:30 +0000</pubDate>
		<guid isPermaLink="false">http://bigsweaterdesign.com/2007/12/17/why-web-standards/#comment-255</guid>
		<description>&lt;blockquote cite="Vincent"&gt;But in many instances, design matters far less than accessibility of information...&lt;/blockquote&gt;

I agree. No amount of good design will make up for poor accessibility, and—worse yet—crappy content. The accessibility features of the web have long been lamented by designers as the crutch of the medium, where many of our peers complain that the web "breaks our designs," making it no fun to work with. I think we need to recognize that these features are part of what makes the web so powerful. 

But I don't think any aspect of the final product should take precedence over another. 

Good code means nothing if the design is poor.

Good design is compromised if the media cannot be shared reliably because of poor code, development, or production.

Good content becomes diluted if the design doesn't honor the content.

&lt;blockquote cite="Vincent"&gt;... how'd you find my site?&lt;/blockquote&gt;

Found it &lt;a href="http://www.noupe.com/design/60-unusual-wp-blog-designs.html" rel="nofollow"&gt;here&lt;/a&gt;.</description>
		<content:encoded><![CDATA[<blockquote cite="Vincent"><p>But in many instances, design matters far less than accessibility of information...</p></blockquote>
<p>I agree. No amount of good design will make up for poor accessibility, and—worse yet—crappy content. The accessibility features of the web have long been lamented by designers as the crutch of the medium, where many of our peers complain that the web "breaks our designs," making it no fun to work with. I think we need to recognize that these features are part of what makes the web so powerful. </p>
<p>But I don't think any aspect of the final product should take precedence over another. </p>
<p>Good code means nothing if the design is poor.</p>
<p>Good design is compromised if the media cannot be shared reliably because of poor code, development, or production.</p>
<p>Good content becomes diluted if the design doesn't honor the content.</p>
<blockquote cite="Vincent"><p>... how'd you find my site?</p></blockquote>
<p>Found it&nbsp;<a href="http://www.noupe.com/design/60-unusual-wp-blog-designs.html" rel="nofollow">here</a>.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Vincent</title>
		<link>http://bigsweaterdesign.com/2007/12/17/why-web-standards/comment-page-1/#comment-254</link>
		<dc:creator>Vincent</dc:creator>
		<pubDate>Sun, 06 Apr 2008 21:52:05 +0000</pubDate>
		<guid isPermaLink="false">http://bigsweaterdesign.com/2007/12/17/why-web-standards/#comment-254</guid>
		<description>Dickson: 

Thanks for stopping by! And thanks for the compliments.

I agree that aesthetics are important on the web&#8212;otherwise, I wouldn't have a job. But in many instances, design matters far less than accessibility of information (for instance, cell phone users, or people accessing a site's content through an RSS reader). 

I'm honestly not sure if I have any readers, as I only update the site occasionally, but glad to know you found what I've written so far interesting! If you don't mind my asking, how'd you find my site?</description>
		<content:encoded><![CDATA[<p>Dickson: </p>
<p>Thanks for stopping by! And thanks for the compliments.</p>
<p>I agree that aesthetics are important on the web&thinsp;&mdash;&thinsp;otherwise, I wouldn't have a job. But in many instances, design matters far less than accessibility of information (for instance, cell phone users, or people accessing a site's content through an <span class="caps">RSS</span> reader). </p>
<p>I'm honestly not sure if I have any readers, as I only update the site occasionally, but glad to know you found what I've written so far interesting! If you don't mind my asking, how'd you find my&nbsp;site?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dickson Fong</title>
		<link>http://bigsweaterdesign.com/2007/12/17/why-web-standards/comment-page-1/#comment-253</link>
		<dc:creator>Dickson Fong</dc:creator>
		<pubDate>Sun, 06 Apr 2008 21:33:52 +0000</pubDate>
		<guid isPermaLink="false">http://bigsweaterdesign.com/2007/12/17/why-web-standards/#comment-253</guid>
		<description>Well said, Vincent. It's too bad that so many websites are still being structured with tables. Although there's a small learning curve to switching from tables to divs, I don't think laziness is an option when our job is to provide the best possible product to our clients. It's simply a matter of professional responsibility. It's also rather shortsighted considering that the time spent learning div layouts, proper CSS, and semantic code will pay you back in spades through reduced development costs in the future. 

&lt;blockquote cite="Vincent"&gt;... for many people using the Web, what a site looks like is the least important thing about the site&lt;/blockquote&gt;

True that content is the most important thing, but I wouldn't underestimate the value people put in the aesthetics of a website. I think it's a shame, but many people judge a book by its cover. There are many examples of websites that people love just because the site "looks cool," not because of quality content, readability, legibility, or any remnant of good graphic design.

Anyways, glad I found your website. Seems like you have some good reading. Adding you to my bookmarks/RSS.</description>
		<content:encoded><![CDATA[<p>Well said, Vincent. It's too bad that so many websites are still being structured with tables. Although there's a small learning curve to switching from tables to divs, I don't think laziness is an option when our job is to provide the best possible product to our clients. It's simply a matter of professional responsibility. It's also rather shortsighted considering that the time spent learning div layouts, proper <span class="caps">CSS</span>, and semantic code will pay you back in spades through reduced development costs in the future. </p>
<blockquote cite="Vincent"><p>... for many people using the Web, what a site looks like is the least important thing about the site</p></blockquote>
<p>True that content is the most important thing, but I wouldn't underestimate the value people put in the aesthetics of a website. I think it's a shame, but many people judge a book by its cover. There are many examples of websites that people love just because the site "looks cool," not because of quality content, readability, legibility, or any remnant of good graphic design.</p>
<p>Anyways, glad I found your website. Seems like you have some good reading. Adding you to my&nbsp;bookmarks/<span class="caps">RSS</span>.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
