<?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"
	>
<channel>
	<title>Comments on: Usability readings</title>
	<atom:link href="http://wrecking.org/cbd/2005/11/12/usability-readings/feed/" rel="self" type="application/rss+xml" />
	<link>http://wrecking.org/cbd/2005/11/12/usability-readings/</link>
	<description>Software studies, technical communication, writing studies, web accessibility, and new media. Life with my girls.</description>
	<pubDate>Thu, 20 Nov 2008 15:40:28 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.3</generator>
		<item>
		<title>By: cbd &#187; Blog Archive &#187; Defining accessibility</title>
		<link>http://wrecking.org/cbd/2005/11/12/usability-readings/#comment-213</link>
		<dc:creator>cbd &#187; Blog Archive &#187; Defining accessibility</dc:creator>
		<pubDate>Sat, 24 Dec 2005 18:01:34 +0000</pubDate>
		<guid isPermaLink="false">http://wrecking.org/cbd/?p=85#comment-213</guid>
		<description>[...] As I&#8217;ve written before, I like complex definitions of usability, like classical definitions from Dumas and Redish, and more recent formulations, like Whitney Quisenbery&#8217;s &#8220;five dimensions.&#8221; Perhaps we need a similar &#8220;dimensional&#8221; definition for accessibility? [...]</description>
		<content:encoded><![CDATA[<p>[...] As I&#8217;ve written before, I like complex definitions of usability, like classical definitions from Dumas and Redish, and more recent formulations, like Whitney Quisenbery&#8217;s &#8220;five dimensions.&#8221; Perhaps we need a similar &#8220;dimensional&#8221; definition for accessibility? [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: cbd</title>
		<link>http://wrecking.org/cbd/2005/11/12/usability-readings/#comment-184</link>
		<dc:creator>cbd</dc:creator>
		<pubDate>Thu, 17 Nov 2005 18:45:17 +0000</pubDate>
		<guid isPermaLink="false">http://wrecking.org/cbd/?p=85#comment-184</guid>
		<description>You just shape the parts for your needs, like in the example. I'm not exactly sure what you mean by "high context," but say you're working on internal documentation which is used by folks familiar with a certain system. Then you could lower the importance of ease of use, and raise that of efficiency and effectiveness, and perhaps error tolerance depending on the specific application.

This takes a bit more work, but it's much more worth it, IMO.</description>
		<content:encoded><![CDATA[<p>You just shape the parts for your needs, like in the example. I&#8217;m not exactly sure what you mean by &#8220;high context,&#8221; but say you&#8217;re working on internal documentation which is used by folks familiar with a certain system. Then you could lower the importance of ease of use, and raise that of efficiency and effectiveness, and perhaps error tolerance depending on the specific application.</p>
<p>This takes a bit more work, but it&#8217;s much more worth it, IMO.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Virginia Agnew</title>
		<link>http://wrecking.org/cbd/2005/11/12/usability-readings/#comment-181</link>
		<dc:creator>Virginia Agnew</dc:creator>
		<pubDate>Tue, 15 Nov 2005 21:17:44 +0000</pubDate>
		<guid isPermaLink="false">http://wrecking.org/cbd/?p=85#comment-181</guid>
		<description>Error-tolerant? Yes . . . I read the Quisenbery piece and liked the examples regarding financial software --especially applicable when the user is the everyday person on the street.  What about writing for specific audiences --high-context audiences?

As a writer, even a small error is difficult in documentation.  You have to write what the user will see, which may not be correct.  Also, tech writers do not document bugs!  But we lack the power to squash them.  Alas!</description>
		<content:encoded><![CDATA[<p>Error-tolerant? Yes . . . I read the Quisenbery piece and liked the examples regarding financial software &#8211;especially applicable when the user is the everyday person on the street.  What about writing for specific audiences &#8211;high-context audiences?</p>
<p>As a writer, even a small error is difficult in documentation.  You have to write what the user will see, which may not be correct.  Also, tech writers do not document bugs!  But we lack the power to squash them.  Alas!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
