<?xml version="1.0" encoding="utf-8" ?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
	<title>Smack the Mouse</title>	<link>http://tc.eserver.org/publisher/Smack_the_Mouse</link>
	<description>A listing of works published by Smack the Mouse 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>Smack the Mouse</title>
		<link>http://tc.eserver.org/dir/Smack_the_Mouse</link>
	</image>
	<item>
		<title>ABBR and ACRONYM are for User Agents, Not for End Users</title>
		<link>http://tc.eserver.org/27724.html</link>
		<guid>http://tc.eserver.org/27724.html</guid>
		<description>The WCAG (1.0) guideline 4, checkpoint 4.2, about ABBR and ACRONYM, has for a long time been too unclear to implement. The drafts for XHTML 2.0 and WCAG 2.0 seem to have solved most problems.</description>
	</item>
	<item>
		<title>Access Key, HTML Accesskey Generated by JavaScript</title>
		<link>http://tc.eserver.org/27725.html</link>
		<guid>http://tc.eserver.org/27725.html</guid>
		<description>One of the great advantages of using first letter of the link text as access key is that it can be generated by code. Conventional wisdom states that it should be done server-side. Bad that it is much easier with JavaScript.</description>
	</item>
	<item>
		<title>Don&apos;t CSS your XML</title>
		<link>http://tc.eserver.org/27716.html</link>
		<guid>http://tc.eserver.org/27716.html</guid>
		<description>CSS should not be used to present homemade XML as web pages. You end up with nothing but style. Neither man nor machine can understand the structure of your document. CSS should only be used for widely supported XML applications like XHTML.</description>
	</item>
	<item>
		<title>Don&apos;t Force New Windows on Users</title>
		<link>http://tc.eserver.org/27727.html</link>
		<guid>http://tc.eserver.org/27727.html</guid>
		<description>A web site should never force new windows on users. If it is necessary as exception to the rule, target=&quot;_blank&quot; is the method to use. JavaScript&apos;s window.open does not send information about the referrer in IE.</description>
	</item>
	<item>
		<title>ENTER and Event-Driven Programming</title>
		<link>http://tc.eserver.org/27729.html</link>
		<guid>http://tc.eserver.org/27729.html</guid>
		<description>The event driven programming model in ASP.NET made possible by HTML and WEB controls &apos;runat server&apos; is a great idea but not without problems. It is a usability disaster that the use of ENTER in forms no longer works as expected.</description>
	</item>
	<item>
		<title>The Logo Should Not Link to the Homepage</title>
		<link>http://tc.eserver.org/27715.html</link>
		<guid>http://tc.eserver.org/27715.html</guid>
		<description>It is a nice convention that a company logo also has a secondary role as a link back to the homepage. But a convention should be challenged if most users have not heard about it or don&apos;t use it, or if the concept is wrong.</description>
	</item>
	<item>
		<title>MAX-WIDTH and Flexible Layout with Short Lines</title>
		<link>http://tc.eserver.org/27726.html</link>
		<guid>http://tc.eserver.org/27726.html</guid>
		<description>It is now possible to make flexible layout with user-friendly short lines that adapt to screen resolution, to width of browser window, and to font-size chosen by the user. This could be a new beginning for more accessible and usable web pages.</description>
	</item>
	<item>
		<title>Use First Letter as AcessKey</title>
		<link>http://tc.eserver.org/27719.html</link>
		<guid>http://tc.eserver.org/27719.html</guid>
		<description>The traditional way of implementing the HTML accesskey attribute using unique letters does not work. I propose always to use the first letter of the link name as access key. The first letter can be generated by code. We badly need are more accessible Internet.</description>
	</item>
	<item>
		<title>Use Inverted Colors to Highlight Active Link</title>
		<link>http://tc.eserver.org/27718.html</link>
		<guid>http://tc.eserver.org/27718.html</guid>
		<description>It is often difficult to find the cursor when a web site is navigated using the keyboard. Where is the active link? With CSS the author of a web page can adjust how the active link is visualized. Inverted colors are the best way to highlight the active link.</description>
	</item>
	<item>
		<title>User-Friendly 404 Error Messages</title>
		<link>http://tc.eserver.org/27728.html</link>
		<guid>http://tc.eserver.org/27728.html</guid>
		<description>An error message should be designed to the website. A good error message could be conceived as so positive that the error is already forgotten or forgiven. The article is a guide to good error messages using the dreaded &quot;404 â€“ file not found&quot; as example.</description>
	</item>
	<item>
		<title>XHTML, HTTP accept-header and MIME-type application/xhtml+xml</title>
		<link>http://tc.eserver.org/27717.html</link>
		<guid>http://tc.eserver.org/27717.html</guid>
		<description>In 2005 it is high time to start serving XHTML as XML on a grand scale. Others have been doing it for years. I have been doing it since Christmas. Switching between XHTML as xml and text/html is easy using the HTTP accept header.</description>
	</item>
	<atom:link href="http://tc.eserver.org/publisher/Smack_the_Mouse.xml" rel="self" type="application/rss+xml"/>
</channel>
</rss>