<?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: Accessibility and Usability</title>
	<atom:link href="http://nirak.net/2009/10/27/accessibility-and-usability/feed/" rel="self" type="application/rss+xml" />
	<link>http://nirak.net/2009/10/27/accessibility-and-usability/</link>
	<description>Karin Dalziel</description>
	<lastBuildDate>Wed, 10 Feb 2010 05:14:16 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Karin Dalziel</title>
		<link>http://nirak.net/2009/10/27/accessibility-and-usability/comment-page-1/#comment-128172</link>
		<dc:creator>Karin Dalziel</dc:creator>
		<pubDate>Tue, 03 Nov 2009 17:44:03 +0000</pubDate>
		<guid isPermaLink="false">http://nirak.net/?p=424#comment-128172</guid>
		<description>@Dr. Gunn Great Point! My talk was meant more for simpler websites, but data accessibility is important too. In addition to having an open API, I&#039;m a proponent of putting your raw data (XML, databases, whatever) out there whenever possible.</description>
		<content:encoded><![CDATA[<p>@Dr. Gunn Great Point! My talk was meant more for simpler websites, but data accessibility is important too. In addition to having an open <acronym title="Application Programming Interface">API</acronym>, I&#8217;m a proponent of putting your raw data (<acronym title="eXtensible Markup Language">XML</acronym>, databases, whatever) out there whenever possible.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dr. Gunn</title>
		<link>http://nirak.net/2009/10/27/accessibility-and-usability/comment-page-1/#comment-128171</link>
		<dc:creator>Dr. Gunn</dc:creator>
		<pubDate>Tue, 03 Nov 2009 17:32:13 +0000</pubDate>
		<guid isPermaLink="false">http://nirak.net/?p=424#comment-128171</guid>
		<description>Great article, Karin. One aspect of accessibility I think that&#039;s often overlooked is data accessibility.  It&#039;s important to make your website usable and accessible to everyone, but in this era of web services, it&#039;s also important to consider whether a user can get at the data any way they want, or can they only see the stuff you want to show them via the interface you provide.

Having an open API is a great way to build community. Given that 80+% of twitter usage is via third-party clients, it provides a great example of this.</description>
		<content:encoded><![CDATA[<p>Great article, Karin. One aspect of accessibility I think that&#8217;s often overlooked is data accessibility.  It&#8217;s important to make your website usable and accessible to everyone, but in this era of web services, it&#8217;s also important to consider whether a user can get at the data any way they want, or can they only see the stuff you want to show them via the interface you provide.</p>
<p>Having an open <acronym title="Application Programming Interface">API</acronym> is a great way to build community. Given that 80+% of twitter usage is via third-party clients, it provides a great example of this.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nirak.net &#187; Accessibility and Usability &#8211; Part 1: Code</title>
		<link>http://nirak.net/2009/10/27/accessibility-and-usability/comment-page-1/#comment-127479</link>
		<dc:creator>Nirak.net &#187; Accessibility and Usability &#8211; Part 1: Code</dc:creator>
		<pubDate>Tue, 27 Oct 2009 15:48:37 +0000</pubDate>
		<guid isPermaLink="false">http://nirak.net/?p=424#comment-127479</guid>
		<description>[...] is part of a series on accessibility and usability. See the contents page for [...]</description>
		<content:encoded><![CDATA[<p>[...] is part of a series on accessibility and usability. See the contents page for [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
