<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Pemaquid Crunch: Web Design notes from Portland, Maine &#187; Cappucino</title>
	<atom:link href="http://www.pemaquid.com/blog/category/cappucino/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.pemaquid.com/blog</link>
	<description>Tips on Web Design, Usability and Web Strategy from Portland, Maine</description>
	<lastBuildDate>Mon, 09 Jan 2012 22:35:38 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
		<item>
		<title>Don&#8217;t forget about accessibility</title>
		<link>http://www.pemaquid.com/blog/2009/03/05/accessibility-is-hard-work/</link>
		<comments>http://www.pemaquid.com/blog/2009/03/05/accessibility-is-hard-work/#comments</comments>
		<pubDate>Thu, 05 Mar 2009 11:15:50 +0000</pubDate>
		<dc:creator>Rob</dc:creator>
				<category><![CDATA[280 North]]></category>
		<category><![CDATA[Accessibility]]></category>
		<category><![CDATA[Ajax]]></category>
		<category><![CDATA[Atlas]]></category>
		<category><![CDATA[Cappucino]]></category>
		<category><![CDATA[Drew McClellan]]></category>
		<category><![CDATA[Interaction Design]]></category>
		<category><![CDATA[Interface Design]]></category>
		<category><![CDATA[Web 2.0]]></category>
		<category><![CDATA[Web apps]]></category>
		<category><![CDATA[apps]]></category>
		<category><![CDATA[frameworks]]></category>

		<guid isPermaLink="false">http://www.pemaquid.com/blog/accessibility-is-hard-work</guid>
		<description><![CDATA[When designing all these way-cool, bubblicious Web 2.0 apps, and when working with frameworks like jQuery, it&#8217;s easy to get caught up in the ajax-y goodness of it all and forget about accessibility requirements. One reason many Web sites don&#8217;t have a higher degree of accessibility built in is that accessible design is seen as [...]]]></description>
			<content:encoded><![CDATA[<p>When designing all these way-cool, bubblicious Web 2.0 apps, and when working with frameworks like <a href="http://jquery.com/">jQuery</a>, it&#8217;s easy to get caught up in the ajax-y goodness of it all and forget about accessibility requirements.</p>
<p>One reason many Web sites don&#8217;t have a higher degree of accessibility built in is that <a href="http://www.w3.org/WAI/intro/accessibility.php">accessible design</a> is seen as hard work.  It&#8217;s one more set of best practices to wrap one&#8217;s brain around.  </p>
<p>Often, for designers, it can seem to take the fun out of things (though it doesn&#8217;t have to be that way).</p>
<p><a href="http://allinthehead.com/retro/337/the-cost-of-accessibility">Drew McClellan has a recent blog post</a> on the subject that illustrates the point.  He talks about the Cappucino framework, developed by <a href="http://280north.com/">280 North</a> and billed as a way to build &#8220;desktop-caliber applications that run in a web browser&#8221;.  The 280 guys are even working on a drop-and-drop IDE, called <a href="http://280atlas.com/">Atlas</a>, for creating Cappucino apps.</p>
<p>I haven&#8217;t tried <a href="http://cappuccino.org/">Cappucino</a> first hand, but the word on the street is that this system is incredibly stunning, and the folks at 280 North should be congratulated for the accomplishment.  </p>
<p>Cappucino&#8217;s javascript-laden framework, however, still has a ways to go to address accessibility issues.  Hopefully, the 280 guys &#8211; and others developing similar systems &#8211; will take the time and do the hard work necessary to make sure their creations have a high degree of accessibility built in.</p>
<p>We can do it without losing the Coolness Factor.  Focus on simple elegance in your design, make it your business to understand best practices for accessible design, and you&#8217;ll be able to build sites that work with assistive devices and are also fun to use.</p>
<div class="tweetmeme_button" style="margin:0 20px 0 0;float:left;">
			<a href="http://api.tweetmeme.com/share?url=http%3A%2F%2Fwww.pemaquid.com%2Fblog%2F2009%2F03%2F05%2Faccessibility-is-hard-work%2F"><br />
				<img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fwww.pemaquid.com%2Fblog%2F2009%2F03%2F05%2Faccessibility-is-hard-work%2F&amp;source=pemaquid&amp;style=normal&amp;service=bit.ly&amp;b=2" height="61" width="50" /><br />
			</a>
		</div>

<div class="sociable">

<ul>
	<li class="sociablefirst"><a rel="nofollow" href="http://twitter.com/home?status=Don%27t%20forget%20about%20accessibility%20-%20http%3A%2F%2Fwww.pemaquid.com%2Fblog%2F2009%2F03%2F05%2Faccessibility-is-hard-work%2F" title="Twitter"><img src="http://www.pemaquid.com/blog/wp-content/plugins/sociable/images/twitter.png" title="Twitter" alt="Twitter" class="sociable-hovers" /></a></li>
	<li><a rel="nofollow" href="http://www.facebook.com/share.php?u=http%3A%2F%2Fwww.pemaquid.com%2Fblog%2F2009%2F03%2F05%2Faccessibility-is-hard-work%2F&amp;t=Don%27t%20forget%20about%20accessibility" title="Facebook"><img src="http://www.pemaquid.com/blog/wp-content/plugins/sociable/images/facebook.png" title="Facebook" alt="Facebook" class="sociable-hovers" /></a></li>
	<li><a rel="nofollow" href="http://digg.com/submit?phase=2&amp;url=http%3A%2F%2Fwww.pemaquid.com%2Fblog%2F2009%2F03%2F05%2Faccessibility-is-hard-work%2F&amp;title=Don%27t%20forget%20about%20accessibility&amp;bodytext=When%20designing%20all%20these%20way-cool%2C%20bubblicious%20Web%202.0%20apps%2C%20and%20when%20working%20with%20frameworks%20like%20jQuery%2C%20it%27s%20easy%20to%20get%20caught%20up%20in%20the%20ajax-y%20goodness%20of%20it%20all%20and%20forget%20about%20accessibility%20requirements.%0D%0A%0D%0AOne%20reason%20many%20Web%20sites%20don%27t%20hav" title="Digg"><img src="http://www.pemaquid.com/blog/wp-content/plugins/sociable/images/digg.png" title="Digg" alt="Digg" class="sociable-hovers" /></a></li>
	<li><a rel="nofollow" href="http://delicious.com/post?url=http%3A%2F%2Fwww.pemaquid.com%2Fblog%2F2009%2F03%2F05%2Faccessibility-is-hard-work%2F&amp;title=Don%27t%20forget%20about%20accessibility&amp;notes=When%20designing%20all%20these%20way-cool%2C%20bubblicious%20Web%202.0%20apps%2C%20and%20when%20working%20with%20frameworks%20like%20jQuery%2C%20it%27s%20easy%20to%20get%20caught%20up%20in%20the%20ajax-y%20goodness%20of%20it%20all%20and%20forget%20about%20accessibility%20requirements.%0D%0A%0D%0AOne%20reason%20many%20Web%20sites%20don%27t%20hav" title="del.icio.us"><img src="http://www.pemaquid.com/blog/wp-content/plugins/sociable/images/delicious.png" title="del.icio.us" alt="del.icio.us" class="sociable-hovers" /></a></li>
	<li><a rel="nofollow" href="http://www.google.com/bookmarks/mark?op=edit&amp;bkmk=http%3A%2F%2Fwww.pemaquid.com%2Fblog%2F2009%2F03%2F05%2Faccessibility-is-hard-work%2F&amp;title=Don%27t%20forget%20about%20accessibility&amp;annotation=When%20designing%20all%20these%20way-cool%2C%20bubblicious%20Web%202.0%20apps%2C%20and%20when%20working%20with%20frameworks%20like%20jQuery%2C%20it%27s%20easy%20to%20get%20caught%20up%20in%20the%20ajax-y%20goodness%20of%20it%20all%20and%20forget%20about%20accessibility%20requirements.%0D%0A%0D%0AOne%20reason%20many%20Web%20sites%20don%27t%20hav" title="Google Bookmarks"><img src="http://www.pemaquid.com/blog/wp-content/plugins/sociable/images/googlebookmark.png" title="Google Bookmarks" alt="Google Bookmarks" class="sociable-hovers" /></a></li>
	<li><a rel="nofollow" href="http://www.newsvine.com/_tools/seed&amp;save?u=http%3A%2F%2Fwww.pemaquid.com%2Fblog%2F2009%2F03%2F05%2Faccessibility-is-hard-work%2F&amp;h=Don%27t%20forget%20about%20accessibility" title="NewsVine"><img src="http://www.pemaquid.com/blog/wp-content/plugins/sociable/images/newsvine.png" title="NewsVine" alt="NewsVine" class="sociable-hovers" /></a></li>
	<li><a rel="nofollow" href="http://www.stumbleupon.com/submit?url=http%3A%2F%2Fwww.pemaquid.com%2Fblog%2F2009%2F03%2F05%2Faccessibility-is-hard-work%2F&amp;title=Don%27t%20forget%20about%20accessibility" title="StumbleUpon"><img src="http://www.pemaquid.com/blog/wp-content/plugins/sociable/images/stumbleupon.png" title="StumbleUpon" alt="StumbleUpon" class="sociable-hovers" /></a></li>
	<li><a rel="nofollow" href="http://technorati.com/faves?add=http%3A%2F%2Fwww.pemaquid.com%2Fblog%2F2009%2F03%2F05%2Faccessibility-is-hard-work%2F" title="Technorati"><img src="http://www.pemaquid.com/blog/wp-content/plugins/sociable/images/technorati.png" title="Technorati" alt="Technorati" class="sociable-hovers" /></a></li>
	<li><a rel="nofollow" href="http://www.tumblr.com/share?v=3&amp;u=http%3A%2F%2Fwww.pemaquid.com%2Fblog%2F2009%2F03%2F05%2Faccessibility-is-hard-work%2F&amp;t=Don%27t%20forget%20about%20accessibility&amp;s=When%20designing%20all%20these%20way-cool%2C%20bubblicious%20Web%202.0%20apps%2C%20and%20when%20working%20with%20frameworks%20like%20jQuery%2C%20it%27s%20easy%20to%20get%20caught%20up%20in%20the%20ajax-y%20goodness%20of%20it%20all%20and%20forget%20about%20accessibility%20requirements.%0D%0A%0D%0AOne%20reason%20many%20Web%20sites%20don%27t%20hav" title="Tumblr"><img src="http://www.pemaquid.com/blog/wp-content/plugins/sociable/images/tumblr.png" title="Tumblr" alt="Tumblr" class="sociable-hovers" /></a></li>
	<li class="sociablelast"><a rel="nofollow" href="http://www.printfriendly.com/print?url=http%3A%2F%2Fwww.pemaquid.com%2Fblog%2F2009%2F03%2F05%2Faccessibility-is-hard-work%2F&amp;partner=sociable" title="Print this article!"><img src="http://www.pemaquid.com/blog/wp-content/plugins/sociable/images/printfriendly.png" title="Print this article!" alt="Print this article!" class="sociable-hovers" /></a></li>
</ul>
</div>
]]></content:encoded>
			<wfw:commentRss>http://www.pemaquid.com/blog/2009/03/05/accessibility-is-hard-work/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

