<?xml version="1.0" encoding="utf-8" ?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
	<title>Design&gt;Web Design&gt;Standards&gt;Usability</title>	<link>http://tc.eserver.org/dir/Design/Web-Design/Standards/Usability</link>
	<description>A listing of the most recently indexed works about Design and Web Design and Standards and Usability 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>Design&gt;Web Design&gt;Standards&gt;Usability</title>
		<link>http://tc.eserver.org/dir/Design/Web-Design/Standards/Usability</link>
	</image>
	<item>
		<title>Who Cares How Pretty Web Sites Are?</title>
		<link>http://tc.eserver.org/32951.html</link>
		<guid>http://tc.eserver.org/32951.html</guid>
		<description>A few weeks back, I wrote about why I think web standards are difficult to learn. I wrote that because I was spending 80% of my time getting my code into XHTML 1.0 and styling it with CSS so that it rendered consistently across 5 or 6 browsers. What was I doing the other 20% of the time? Creating content, of course. I was putting together what a huge percentage of my site visitors come for. When I thought about it in these terms (time spent), I felt like styling with CSS was a lot of work for comparatively little gain. After all, people will still be able to find the site, read the content, and click on the links, whether or not I’ve styled it.</description>
	</item>
	<item>
		<title>Change vs. Stability in Web Usability Guidelines</title>
		<link>http://tc.eserver.org/28951.html</link>
		<guid>http://tc.eserver.org/28951.html</guid>
		<description>A remarkable 80% of findings from the Web usability studies in the 1990s continue to hold today.</description>
	</item>
	<item>
		<title>Evolution Trumps Usability Guidelines</title>
		<link>http://tc.eserver.org/28095.html</link>
		<guid>http://tc.eserver.org/28095.html</guid>
		<description>&apos;Use a Search Box instead of a link to a Search page.&apos; This is one guideline from the plethora of recently created usability guidelines to help designers produce more usable web sites. It makes sense. After all, there are more than 42 million web sites on the Internet. It should be simple to study these sites and put together a list of &apos;do&apos;s&apos; and &apos;don&apos;ts&apos; that, when followed, will produce easy-to-use sites. But...</description>
	</item>
	<item>
		<title>W3Compliant Sites</title>
		<link>http://tc.eserver.org/24175.html</link>
		<guid>http://tc.eserver.org/24175.html</guid>
		<description>W3 Compliant Sites is a collection of web sites that were created by designers that conform with the W3C standards. It provides the opportunity for them to display their work and ideas in a community that shares common interests.</description>
	</item>
	<item>
		<title>Are Standards-Compliant Websites Better?</title>
		<link>http://tc.eserver.org/21052.html</link>
		<guid>http://tc.eserver.org/21052.html</guid>
		<description>The adhoc way in which much of the web was developed has created a dilemma for web designers: should websites comply with standards, ensuring accessibility, or break the rules and work with older browsers? At this moment, the answer is simple: Websites should work with older browsers.</description>
	</item>
	<atom:link href="http://tc.eserver.org/dir/Design/Web-Design/Standards/Usability.xml" rel="self" type="application/rss+xml"/>
</channel>
</rss>