<?xml version="1.0" encoding="utf-8" ?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
	<title>Quinn, Anthony</title>	<link>http://tc.eserver.org/authors/Quinn,_Anthony</link>
	<description>A bibliography of works by Quinn, Anthony in the field of technical communication.</description>
	<language>en-us</language>
	<copyright>Copyright (c) 2005-08 by the EServer. All rights reserved.</copyright>
	<managingEditor>tclib-editorial@eserver.org (TC Library Editorial Board)</managingEditor>
	<webMaster>webmaster@eserver.org (Geoffrey Sauer)</webMaster>
	<image>
		<url>http://tc.eserver.org/images/newlogo.gif</url>
		<title>Quinn, Anthony</title>
		<link>http://tc.eserver.org/dir/Quinn,_Anthony</link>
	</image>
	<item>
		<title>Why People Can&apos;t Use eLearning</title>
		<link>http://tc.eserver.org/19314.html</link>
		<guid>http://tc.eserver.org/19314.html</guid>
		<description>Unusable interfaces will cost eLearning companies billions of dollars in lost revenues because many people won’t be able to use their products.&#xD;&#xD;The US eLearning market has a projected value of $11.5 billion by 2003 while the European market is expected to be worth $4 billion by 2004. However, poor usability will contribute to disappointing results for many eLearning companies, for the following reasons.</description>
	</item>
	<item>
		<title>Designing Scalable Interfaces</title>
		<link>http://tc.eserver.org/19288.html</link>
		<guid>http://tc.eserver.org/19288.html</guid>
		<description>Scalable interface design ensures that interface development takes account of the need to change over time, providing solutions that are flexible and thus &apos;future-proof&apos; to some extent. Too often complex interface designs require a complete overhaul when even the smallest change is required in the functionality of the application or site in question. Building &apos;scalable&apos; interfaces in the first place will save time and cost in the long term - and make coping with upgrades easier for your customers.</description>
	</item>
	<item>
		<title>Effective Alt Text</title>
		<link>http://tc.eserver.org/19294.html</link>
		<guid>http://tc.eserver.org/19294.html</guid>
		<description>Good alt text can be a useful tool for enhancing the web interface. It provides supporting information, helping users gain an understanding of the structure web pages and an insight into the behaviour of key controls and interactive elements.&#xD;&#xD;&apos;ALT&apos; is a HTML tag. It adds a short line of text to an image, usually for descriptive purposes. If you are using a mouse and you &apos;hover” the pointer over an image on a web page, you will notice that a short line of text appears - this is the alt text. You should also see the alt text if you switch off the images on your browser - the images have been replaced by &apos;placeholders” and the same short line of text which appeared when you hovered the mouse over the image.</description>
	</item>
	<item>
		<title>Why &quot;Bobby Approved&quot; Does Not Always Mean Accessible</title>
		<link>http://tc.eserver.org/19039.html</link>
		<guid>http://tc.eserver.org/19039.html</guid>
		<description>Bobby is an online testing tool which has been developed to help developers assess web sites for accessibility. It is a free service provided by CAST (Centre for Applied Special Technology), a non-profit organisation which aims to expand opportunities for people with disabilities through computer technology. Bobby looks at the underlying HTML code that controls the presentation of a web page and analyses it against the W3C Web Accessibility Initiative (WAI) guidelines.&#xD;&#xD;Many organizations genuinely believe that if their site passes the Bobby test and displays the Bobby icon, it is &apos;accessible.&apos; In many ways, this is an understandable outlook. The &apos;Bobby Approved&apos; icon represents an achievable standard and a tangible, recognisable endorsement of efforts made towards web accessibility. However, it should be remembered that the Bobby test does not ensure true &apos;accessibility.&apos;</description>
	</item>
	<atom:link href="http://tc.eserver.org/authors/Quinn,_Anthony.xml" rel="self" type="application/rss+xml"/>
</channel>
</rss>