<?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>USiT &#187; accessibility</title>
	<atom:link href="http://www.usit.com.au/category/accessibility/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.usit.com.au</link>
	<description>User Standards and Innovative Technology @ News Digital Media</description>
	<lastBuildDate>Fri, 13 Aug 2010 04:09:30 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
		<item>
		<title>Weekly links</title>
		<link>http://www.usit.com.au/2009/12/02/weekly-links-3/</link>
		<comments>http://www.usit.com.au/2009/12/02/weekly-links-3/#comments</comments>
		<pubDate>Wed, 02 Dec 2009 01:10:15 +0000</pubDate>
		<dc:creator>USiT team</dc:creator>
				<category><![CDATA[Interesting link]]></category>
		<category><![CDATA[Links]]></category>
		<category><![CDATA[accessibility]]></category>
		<category><![CDATA[customer]]></category>
		<category><![CDATA[design]]></category>
		<category><![CDATA[design thinking]]></category>
		<category><![CDATA[experience]]></category>
		<category><![CDATA[google]]></category>
		<category><![CDATA[kindle]]></category>
		<category><![CDATA[principles]]></category>
		<category><![CDATA[research]]></category>
		<category><![CDATA[storyboards]]></category>
		<category><![CDATA[testing]]></category>
		<category><![CDATA[user experience]]></category>
		<category><![CDATA[ux]]></category>
		<category><![CDATA[wireframes]]></category>

		<guid isPermaLink="false">http://www.usit.com.au/?p=585</guid>
		<description><![CDATA[US universities reject &#8216;inaccessible&#8217; Kindle e-Book The E-Access Bulletin reports&#8230; Two American universities have rejected the market-leading Kindle DX electronic book reader as a textbook replacement due to its inaccessibility for blind students. Both Syracuse University in New York State and the University of Wisconsin-Madison have chosen not to use the Kindle &#8211; manufactured by [...]]]></description>
			<content:encoded><![CDATA[<h4>US universities reject &#8216;inaccessible&#8217; Kindle e-Book</h4>
<p>The <strong>E-Access Bulletin</strong> <a href="http://www.headstar.com/eablive/?p=357">reports</a>&#8230;</p>
<blockquote>
<p>Two American universities have rejected the market-leading Kindle DX electronic book reader as a textbook replacement due to its inaccessibility for blind students. Both Syracuse University in New York State and the University of Wisconsin-Madison have chosen not to use the Kindle &#8211; manufactured by Amazon.com &#8211; as a teaching-aid, after their own trials found it was not fully accessible.</p>
</blockquote>
<p>Interesting lessons for anyone else considering an e-reader device, and who wants to make it useful for as wide an audience as possible.<br /><em>(forwarded by Pat)</em></p>
<h4>Clients could make better use of research</h4>
<p><strong>Adweek</strong> recently published an <a href="http://www.adweek.com/aw/content_display/news/agency/e3id5f0c474545e07aad97d6ae09ba23daa">article</a> reporting&#8230;</p>
<blockquote>
<p>Consumer research is ingrained in the cultures of many large corporations but relatively few are maximizing its use, according to a new study from The Boston Consulting Group [...] In fact, based on a four-stage scale of research development that BCG used to evaluate the 40 global companies it surveyed, nearly 90 percent were in the first or second stage, where research is generally tactical and applied in limited contexts.</p>
</blockquote>
<p>This has generated quite a few comments, and criticism, although nobody seems to disagree with the basic sentiment of the report (that research could be more prevalent and better used). What do you think?<br /><em>(forwarded by Pat)</em></p>
<h4>Map of the design landscape</h4>
<p>Over on DesignAday, <strong>Jack Moffett</strong> shares a <a href="http://designaday.tumblr.com/post/263122023/map-of-the-design-landscape-in-full-resolution">timeline visualisation</a> of the major&mdash;mostly US&mdash;design disciplines created by one of his graduate students.<br /><em>(forwarded by Angus)</em></p>
<h4>IA tools: storyboards</h4>
<p><strong>Matt Hodgson</strong> shares his <a href="http://magia3e.wordpress.com/2009/11/30/ia-tools-storyboards/">thoughts on storyboards</a>&#8230;</p>
<blockquote>
<p>Storyboards are a great way to describe a user’s journey, their thoughts, feelings, attitudes, capabilities, behaviours and expectations, throughout a single scenario. They’re light-weight, easy to do, and as a visual tool can be used in workshops or just by a couple of members of the team. They also work perfectly on agile projects because they’re visual and, therefore, an instant placeholder for a conversation.</p>
</blockquote>
<p><em>(forwarded by Angus)</em></p>
<h4>So you wanna be a user experience designer</h4>
<p><strong>Whitney Hess</strong> shares her <a href="http://whitneyhess.com/blog/2009/11/23/so-you-wanna-be-a-user-experience-designer-step-2-guiding-principles/">five guiding principles</a> for working in UX&#8230;</p>
<blockquote>
<p>I have collected a set of guiding principles for user experience designers, to encourage behaviors that I believe are necessary to being a successful practitioner, as well as a set of guiding principles for experience design — which I think anyone who touches a product used by humans should strive to follow.</p>
</blockquote>
<p><em>(forwarded by Angus)</em></p>
<h4>Getting to the customer – why everything you think about User Centred Design is wrong</h4>
<p>On Black&amp;White, <strong>Thomas Petersen</strong> <a href="http://000fff.org/getting-to-the-customer-why-everything-you-think-about-user-centred-design-is-wrong/">discusses</a> solving the right problem at the right time&#8230;</p>
<blockquote>
<p>What you are solving in the wireframe phase is problems inherent in the wireframe phase, not problems with the product. What you are solving when testing the prototype is problems inherent in the prototype not in the final product. There is only one true test and that is the final product. Not until then will you start to receive valuable feedback in combination with quantitative feedback. You will get it where it matters.</p>
</blockquote>
<p>This is something we&#8217;ve talked about in our team on a number of occasions. It&#8217;s an important aspect of the UX design process to get sorted out.<br /><em>(forwarded by Angus)</em></p>
<h4>Google tests streamlining search options feature</h4>
<p>Over on Search Engine Land, <strong>Danny Sullivan</strong> tells us how <a href="http://searchengineland.com/google-streamlines-search-options-30143">Google is tackling its &#8220;UI jazz problem&#8221;</a>&#8230;</p>
<blockquote>
<p>“I don’t like jazz, because you never know what’s going to happen next,” Mayer said, continuing on to apply the musical style to Google’s search results. “I’ve been calling this problem ‘user interface jazz.’ This result looks this way, and that result looks that way [something much different], and it really does slow you down.”</p>
</blockquote>
<p><em>(forwarded by Angus)</em></p>
<h4>Some design principles from the Global Agenda Council on Design</h4>
<p><strong>Tim Brown</strong>, of renowned design and innovation consulting firm, IDEO, shares with us <a href="http://designthinking.ideo.com/?p=409">seven principles</a> as discussed at the recent World Economic Forum event in Dubai&#8230;</p>
<blockquote>
<p>Design is an agent of change that enables us to understand complex changes and problems, and to turn them into something useful. Tackling today&#8217;s global challenges will require radical thinking, creative solutions and collaborative action. Here is a set of principles identified by the Global Agenda Council on Design that could help your Council to develop ideas and strategies to address the complex problems facing us all.</p>
</blockquote>
<p><em>(forwarded by Angus)</em></p>
]]></content:encoded>
			<wfw:commentRss>http://www.usit.com.au/2009/12/02/weekly-links-3/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Affordance instead of accessibility</title>
		<link>http://www.usit.com.au/2009/05/14/affordance-instead-of-accessibility/</link>
		<comments>http://www.usit.com.au/2009/05/14/affordance-instead-of-accessibility/#comments</comments>
		<pubDate>Thu, 14 May 2009 03:08:48 +0000</pubDate>
		<dc:creator>Patrick Kennedy</dc:creator>
				<category><![CDATA[Interesting link]]></category>
		<category><![CDATA[accessibility]]></category>
		<category><![CDATA[affordances]]></category>
		<category><![CDATA[e-access]]></category>

		<guid isPermaLink="false">http://www.usit.com.au/?p=474</guid>
		<description><![CDATA[Bill Thompson talks about Unasking the Right Questions in the latest E-Access Bulletin: &#8230;we keep thinking about &#8216;accessibility&#8217; and &#8216;usability&#8217; as separate, almost orthogonal aspects of design. Unfortunately, this remains the dominant model, and it has now become a barrier to future progress because it encourages designers to think about creating tools and services for [...]]]></description>
			<content:encoded><![CDATA[<p>Bill Thompson talks about <a href="http://www.headstar.com/eablive/?p=287">Unasking the Right Questions</a> in the latest E-Access Bulletin</a>:</p>
<blockquote><p>
&#8230;we keep thinking about &#8216;accessibility&#8217; and &#8216;usability&#8217; as separate, almost orthogonal aspects of design. Unfortunately, this remains the dominant model, and it has now become a barrier to future progress because it encourages designers to think about creating tools and services for the &#8216;normal&#8217; population before considering accessibility [...] Instead of thinking about &#8216;access&#8217; at one end and &#8216;usability&#8217; at another, we should attempt to recast our debate in terms of what technology does for all of us, not just those whose have &#8216;special&#8217; requirements.
</p></blockquote>
<p>Fairly standard argument for properly integrating accessibility into design practices, but where I think the article gets more interesting is with this:</p>
<blockquote><p>
So how should we frame our debate if we move beyond what I think is a dangerous attempt to retain the distinction between &#8216;usability&#8217; and &#8216;accessibility&#8217;? I think it is time to explore the idea of affordance&#8217;, as it could offer us a way forward. [...] Bill Gaver [...] wrote: &#8220;Affordances go beyond value-free physical descriptions of the environment by expressing environmental attributes relative to humans. For example, the physical measure of height, which has no inherent meaning, can be recast in terms of the affordance of accessibility, which does. Because accessibility emerges from the relation between elevation and people&#8217;s physical characteristics, it is an objective fact about a situation.&#8221;</p>
<p>[...] If we start to frame the issues facing users whose capabilities deviate from the norm in terms of affordances rather than simply of accessibility, this might free us from the &#8216;modal totalitarianism&#8217; that infects so much design, whether in products like screens and keyboards or on-screen in websites, widgets and services.</p>
<p>Affordances matter equally to the &#8216;abled&#8217; as to the &#8216;disabled&#8217;, and so the same design methods can be used, and outcomes can be evaluated in a much broader way. This allows us to start to move away from the current model, in which we have &#8216;assistive&#8217; technologies to overcome &#8216;deficits&#8217; that make some users &#8216;abnormal&#8217;, to one in which we all have skills and abilities that vary along a large number of axes.
</p></blockquote>
<p>Has anybody used this approach to reframe their requirements in terms of affordances instead of accessibility?</p>
]]></content:encoded>
			<wfw:commentRss>http://www.usit.com.au/2009/05/14/affordance-instead-of-accessibility/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Accessible iPod Nano</title>
		<link>http://www.usit.com.au/2008/10/22/accessible-ipod-nano/</link>
		<comments>http://www.usit.com.au/2008/10/22/accessible-ipod-nano/#comments</comments>
		<pubDate>Wed, 22 Oct 2008 03:25:41 +0000</pubDate>
		<dc:creator>Patrick Kennedy</dc:creator>
				<category><![CDATA[accessibility]]></category>
		<category><![CDATA[blind users]]></category>
		<category><![CDATA[ipod]]></category>

		<guid isPermaLink="false">http://www.usit.com.au/?p=235</guid>
		<description><![CDATA[This snippet from the E-Access Bulletin shows accessibility is gaining some traction off the web&#8230; Nano Praise: Apple&#8217;s latest iPod Nano has been praised by the American Federation of the Blind for incorporating innovations that make the device accessible to blind users. The latest model of Apple&#8217;s popular portable music player features spoken menus to [...]]]></description>
			<content:encoded><![CDATA[<p>This snippet from the <a href="http://www.headstar.com/eab/">E-Access Bulletin</a> shows accessibility is gaining some traction off the web&#8230;</p>
<blockquote>
<p>Nano Praise: Apple&#8217;s latest iPod Nano has been praised by the American Federation of the Blind for incorporating innovations that make the device accessible to blind users. The latest model of Apple&#8217;s popular portable music player features spoken menus to allow listeners to hear track names and details, a variable contrast screen and the ability to resize text.</p>
</blockquote>
<p>(You can <a href="http://www.afb.org/Section.asp?DocumentID=4399">read the original article</a> on AFB.org)</p>
]]></content:encoded>
			<wfw:commentRss>http://www.usit.com.au/2008/10/22/accessible-ipod-nano/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
