<?xml version="1.0" encoding="utf-8" ?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
	<title>Articles&gt;User Centered Design&gt;Accessibility</title>	<link>http://tc.eserver.org/dir/Articles/User-Centered-Design/Accessibility</link>
	<description>A listing of the most recently indexed works about Articles and User Centered Design and Accessibility 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>Articles&gt;User Centered Design&gt;Accessibility</title>
		<link>http://tc.eserver.org/dir/Articles/User-Centered-Design/Accessibility</link>
	</image>
	<item>
		<title>Usability Spotter #5: HP Laptop Touch Pads with Scroll Zones- Absence of Tactile Cue</title>
		<link>http://tc.eserver.org/34622.html</link>
		<guid>http://tc.eserver.org/34622.html</guid>
		<description>Summary&#xD;The issue with HP laptops that have a touch pad with a scroll zone contained it (as shown in image A) is that they do not provide a tactile cue for the user to help interpret what section of the touch pad the finger is positioned at. In the absence of a tactile cue, it is difficult for the user to determine whether the finger is on touch pad or the scroll zone without looking at it, resulting in the accidental scrolling on the screen when actually the user simply wants to move the cursor. The issue and multiple solutions are discussed ahead.</description>
	</item>
	<item>
		<title>Accessibility to the Face</title>
		<link>http://tc.eserver.org/34049.html</link>
		<guid>http://tc.eserver.org/34049.html</guid>
		<description>Empathy is what separates us from the rest of the animal kingdom. We have an ability to imagine things the way that others see them and how it makes them feel. We don’t even have to have a disability ourselves. Accessibility is NOT a checklist. Accessibility is about usability. Accessibility is a paradigm shift. Accessibility is a personal issue.</description>
	</item>
	<item>
		<title>Accessing Information: Not Everyone Does it the Same Way</title>
		<link>http://tc.eserver.org/33475.html</link>
		<guid>http://tc.eserver.org/33475.html</guid>
		<description>As some in our profession have come to realize, social media and use of the Web in general have changed (and are still changing) the way in which people access and use information.</description>
	</item>
	<item>
		<title>Accessibility in User-Centered Design</title>
		<link>http://tc.eserver.org/32991.html</link>
		<guid>http://tc.eserver.org/32991.html</guid>
		<description>A brief introduction, with linked resources, for those unfamiliar with accessibility and/or user-centred design.</description>
	</item>
	<item>
		<title>Accessibility Meets Usability: A Plea for a Paramount and Concurrent User-Centered Design Approach to Electronic and Information Technology Accessibility for All</title>
		<link>http://tc.eserver.org/19263.html</link>
		<guid>http://tc.eserver.org/19263.html</guid>
		<description>This paper identifies challenges for a user–centered design process with respect to infusing accessible design practices into electronic and information technology product development. Initially, it emphasizes that when&#xD;user–centered design is paramount and concurrent with&#xD;accessible design, electronic and information technology&#xD;can be accessible for all. Next, it provides an overview&#xD;of the Americans with Disabilities Act (ADA) Section&#xD;508. Last, it provides basic accessible design heuristics&#xD;that can be integrated into the design process. It&#xD;concludes with recommendations for a paramount and&#xD;concurrent user–centered design approach to product&#xD;development.</description>
	</item>
	<atom:link href="http://tc.eserver.org/dir/Articles/User-Centered-Design/Accessibility.xml" rel="self" type="application/rss+xml"/>
</channel>
</rss>