<?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: Making compromises for accessibility</title>
	<atom:link href="http://www.joedolson.com/articles/2009/06/making-compromises-for-accessibility/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.joedolson.com/articles/2009/06/making-compromises-for-accessibility/</link>
	<description>Tips and Commentary on Web Accessibility, Usability, and Search Marketing best practices.</description>
	<lastBuildDate>Fri, 30 Jul 2010 16:56:29 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=abc</generator>
	<item>
		<title>By: cascade</title>
		<link>http://www.joedolson.com/articles/2009/06/making-compromises-for-accessibility/comment-page-1/#comment-32785</link>
		<dc:creator>cascade</dc:creator>
		<pubDate>Mon, 09 Nov 2009 12:46:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.joedolson.com/articles/?p=547#comment-32785</guid>
		<description>What are web accessibility trade-offs then?</description>
		<content:encoded><![CDATA[<p>What are web accessibility trade-offs&nbsp;then?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steve</title>
		<link>http://www.joedolson.com/articles/2009/06/making-compromises-for-accessibility/comment-page-1/#comment-31894</link>
		<dc:creator>Steve</dc:creator>
		<pubDate>Mon, 27 Jul 2009 11:29:52 +0000</pubDate>
		<guid isPermaLink="false">http://www.joedolson.com/articles/?p=547#comment-31894</guid>
		<description>Good creativity leads to a better web design..!</description>
		<content:encoded><![CDATA[<p>Good creativity leads to a better web&nbsp;design..!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jenny</title>
		<link>http://www.joedolson.com/articles/2009/06/making-compromises-for-accessibility/comment-page-1/#comment-31800</link>
		<dc:creator>Jenny</dc:creator>
		<pubDate>Mon, 06 Jul 2009 21:22:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.joedolson.com/articles/?p=547#comment-31800</guid>
		<description>In my opinion, designing a website that is accesible for everybody does not necessarily mean having a plain black and white straight site in the end. As somebody has already said, design is far much more than just the aesthetic part: it implies the way the information is laid out and hyerarchized, the colours you use, the typos you use and so on. A well designed website, therefore, will be error free, clear, user-friendly and will make you feel comfortable surfing it.</description>
		<content:encoded><![CDATA[<p>In my opinion, designing a website that is accesible for everybody does not necessarily mean having a plain black and white straight site in the end. As somebody has already said, design is far much more than just the aesthetic part: it implies the way the information is laid out and hyerarchized, the colours you use, the typos you use and so on. A well designed website, therefore, will be error free, clear, user-friendly and will make you feel comfortable surfing&nbsp;it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joe Dolson</title>
		<link>http://www.joedolson.com/articles/2009/06/making-compromises-for-accessibility/comment-page-1/#comment-31779</link>
		<dc:creator>Joe Dolson</dc:creator>
		<pubDate>Tue, 30 Jun 2009 21:05:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.joedolson.com/articles/?p=547#comment-31779</guid>
		<description>Thanks for your comments, Steve and Melanie! 

That&#039;s a classic quote from Mark Boulton -- understanding the sense that design is an all-encompassing element of functionality and appearance is crucial to working your way through a project. 

Best,
Joe</description>
		<content:encoded><![CDATA[<p>Thanks for your comments, Steve and&nbsp;Melanie! </p>
<p>That&#8217;s a classic quote from Mark Boulton&thinsp;&#8212;&thinsp;understanding the sense that design is an all-encompassing element of functionality and appearance is crucial to working your way through a&nbsp;project. </p>
<p>Best,<br />&nbsp;Joe</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steve Grobschmidt</title>
		<link>http://www.joedolson.com/articles/2009/06/making-compromises-for-accessibility/comment-page-1/#comment-31778</link>
		<dc:creator>Steve Grobschmidt</dc:creator>
		<pubDate>Tue, 30 Jun 2009 14:39:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.joedolson.com/articles/?p=547#comment-31778</guid>
		<description>Great post -- I noticed that wording in the &quot;10 Things....&quot; article as well, when I first read it.

That quote from Mark Boulton does resonate. I&#039;ve encountered numerous people in my career who attribute design as pure aesthetics. The worst of those people calling what designers do &quot;eye candy&quot; or &quot;making it pretty&quot;.

But true web design encompasses so many things. I wouldn&#039;t call a person who simply makes beautiful PSDs a great designer, if they can&#039;t: produce semantically clean code; be mindful of presenting a strong user experience every step of the way; follow fundamental accessibility guidelines, etc

So, in effect, good design IS all about compromises, sacrifices, trade-offs, etc. The world&#039;s most beautiful, eye-catching PhotoShop rendering may make an awful web site.

But yet, there is no reason at all that a fully accessible web site can&#039;t be stunning and, yes, &quot;eye candy&quot;.</description>
		<content:encoded><![CDATA[<p>Great post&thinsp;&#8212;&thinsp;I noticed that wording in the &#8220;10 Things&#8230;.&#8221; article as well, when I first read&nbsp;it.</p>
<p>That quote from Mark Boulton does resonate. I&#8217;ve encountered numerous people in my career who attribute design as pure aesthetics. The worst of those people calling what designers do &#8220;eye candy&#8221; or &#8220;making it&nbsp;pretty&#8221;.</p>
<p>But true web design encompasses so many things. I wouldn&#8217;t call a person who simply makes beautiful PSDs a great designer, if they can&#8217;t: produce semantically clean code; be mindful of presenting a strong user experience every step of the way; follow fundamental accessibility guidelines,&nbsp;etc</p>
<p>So, in effect, good design IS all about compromises, sacrifices, trade-offs, etc. The world&#8217;s most beautiful, eye-catching PhotoShop rendering may make an awful web&nbsp;site.</p>
<p>But yet, there is no reason at all that a fully accessible web site can&#8217;t be stunning and, yes, &#8220;eye&nbsp;candy&#8221;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Melanie</title>
		<link>http://www.joedolson.com/articles/2009/06/making-compromises-for-accessibility/comment-page-1/#comment-31777</link>
		<dc:creator>Melanie</dc:creator>
		<pubDate>Tue, 30 Jun 2009 14:17:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.joedolson.com/articles/?p=547#comment-31777</guid>
		<description>I understand your point.  It is important for designers of &lt;strong&gt;all&lt;/strong&gt; environments--web, buildings, devices--to think more broadly in the planning stages and to consider usability from the perspective of a diverse user base.  It takes commitment, time and effort to think differently about the design process.  In all that we design, we need to think about usability as a part of the design, not an add-on.  If we do that, then we will not think of it as compromising, we will just think of it as &lt;strong&gt;good design&lt;/strong&gt;.  Boulton&#039;s quote expresses this well:

&quot;I think design covers so much more than the aesthetic. Design is fundamentally more. Design is usability. It is Information Architecture. It is Accessibility. This is all design.&quot;

— Mark Boulton</description>
		<content:encoded><![CDATA[<p>I understand your point.  It is important for designers of <strong>all</strong> environments&thinsp;&#8212;&thinsp;web, buildings, devices&thinsp;&#8212;&thinsp;to think more broadly in the planning stages and to consider usability from the perspective of a diverse user base.  It takes commitment, time and effort to think differently about the design process.  In all that we design, we need to think about usability as a part of the design, not an add-on.  If we do that, then we will not think of it as compromising, we will just think of it as <strong>good design</strong>.  Boulton&#8217;s quote expresses this&nbsp;well:</p>
<p><span class="dquo">&#8220;</span>I think design covers so much more than the aesthetic. Design is fundamentally more. Design is usability. It is Information Architecture. It is Accessibility. This is all&nbsp;design.&#8221;</p>
<p>— Mark&nbsp;Boulton</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joe Dolson</title>
		<link>http://www.joedolson.com/articles/2009/06/making-compromises-for-accessibility/comment-page-1/#comment-31742</link>
		<dc:creator>Joe Dolson</dc:creator>
		<pubDate>Thu, 25 Jun 2009 14:54:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.joedolson.com/articles/?p=547#comment-31742</guid>
		<description>I think it is a compromise, and that sacrifice is always involved, because I&#039;m trying to look at it from a broad base of practical perspectives. I know from experience working with designers that they definitely have considered the more limiting color palette to be a sacrifice; I may think of it as simply the nature of working with contrast, but to them it&#039;s an unfortunate sacrifice in design flexibility. 

&quot;Compromise&quot; can be a pretty flexible word - the difference in use between compromise and trade-off is extremely subtle, and I&#039;m not sure I&#039;d agree that compromise requires loss and trade-off doesn&#039;t</description>
		<content:encoded><![CDATA[<p>I think it is a compromise, and that sacrifice is always involved, because I&#8217;m trying to look at it from a broad base of practical perspectives. I know from experience working with designers that they definitely have considered the more limiting color palette to be a sacrifice; I may think of it as simply the nature of working with contrast, but to them it&#8217;s an unfortunate sacrifice in design&nbsp;flexibility. </p>
<p><span class="dquo">&#8220;</span>Compromise&#8221; can be a pretty flexible word - the difference in use between compromise and trade-off is extremely subtle, and I&#8217;m not sure I&#8217;d agree that compromise requires loss and trade-off&nbsp;doesn&#8217;t</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jared Smith</title>
		<link>http://www.joedolson.com/articles/2009/06/making-compromises-for-accessibility/comment-page-1/#comment-31735</link>
		<dc:creator>Jared Smith</dc:creator>
		<pubDate>Wed, 24 Jun 2009 17:17:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.joedolson.com/articles/?p=547#comment-31735</guid>
		<description>I don&#039;t know that I&#039;d call most of these issues compromises. I&#039;d call them trade-offs. You don&#039;t compromise your favorite design colors - you trade-off those colors you&#039;d like with colors that will not hurt accessibility. &#039;Compromise&#039; suggests that you only lose something. A trade-off means you give up something to gain something else. In this case, you give up some design ideas to gain better accessibility.

With that said, some of these trade-offs are pretty expensive. Visible &quot;skip&quot; links, for example, have a significant impact on design while providing only some users a benefit.</description>
		<content:encoded><![CDATA[<p>I don&#8217;t know that I&#8217;d call most of these issues compromises. I&#8217;d call them trade-offs. You don&#8217;t compromise your favorite design colors - you trade-off those colors you&#8217;d like with colors that will not hurt accessibility. &#8216;Compromise&#8217; suggests that you only lose something. A trade-off means you give up something to gain something else. In this case, you give up some design ideas to gain better&nbsp;accessibility.</p>
<p>With that said, some of these trade-offs are pretty expensive. Visible &#8220;skip&#8221; links, for example, have a significant impact on design while providing only some users a&nbsp;benefit.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
