<?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;Writing&gt;Usability</title>	<link>http://tc.eserver.org/dir/Design/Web-Design/Writing/Usability</link>
	<description>A listing of the most recently indexed works about Design and Web Design and Writing and Usability in the field of technical communication (and technical writing).</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;Writing&gt;Usability</title>
		<link>http://tc.eserver.org/dir/Design/Web-Design/Writing/Usability</link>
	</image>
	<item>
		<title>最初の2語：　流し読みのためのシグナル</title>
		<link>http://tc.eserver.org/34905.html</link>
		<guid>http://tc.eserver.org/34905.html</guid>
		<description>リンクの最初の11文字がどれだけ理解されるかをテストすれば、そのサイトがユーザのために書かれたかものかどうかがわかる。ユーザというのはリストの項目を全部読む、というよりは、流し読みをするものだからだ。</description>
	</item>
	<item>
		<title>Los Usuarios no Nos Leen</title>
		<link>http://tc.eserver.org/34686.html</link>
		<guid>http://tc.eserver.org/34686.html</guid>
		<description>Las normas básicas de como escribir un texto para web, vamos, lo que todo copywriter se sabe de carrerilla.</description>
	</item>
	<item>
		<title>First Two Words: A Signal for the Scanning Eye</title>
		<link>http://tc.eserver.org/34291.html</link>
		<guid>http://tc.eserver.org/34291.html</guid>
		<description>Testing how well people understand a link&apos;s first 11 characters shows whether sites write for users, who typically scan rather than read lists of items.</description>
	</item>
	<item>
		<title>About Us Information on Websites</title>
		<link>http://tc.eserver.org/33458.html</link>
		<guid>http://tc.eserver.org/33458.html</guid>
		<description>We found a 9% improvement in the usability of About Us information on websites over the past 5 years. But companies and organizations still can&apos;t explain what they do in one paragraph.</description>
	</item>
	<item>
		<title>Writing Style for Print vs. Web</title>
		<link>http://tc.eserver.org/31906.html</link>
		<guid>http://tc.eserver.org/31906.html</guid>
		<description>Linear vs. non-linear. Author-driven vs. reader-driven. Storytelling vs. ruthless pursuit of actionable content. Anecdotal examples vs. comprehensive data. Sentences vs. fragments.</description>
	</item>
	<item>
		<title>Long vs. Short Articles as Content Strategy</title>
		<link>http://tc.eserver.org/30194.html</link>
		<guid>http://tc.eserver.org/30194.html</guid>
		<description>Information foraging shows how to calculate your content strategy&apos;s costs and benefits. A mixed diet that combines brief overviews and comprehensive coverage is often best.</description>
	</item>
	<item>
		<title>Blah-Blah Text: Keep, Cut, or Kill?</title>
		<link>http://tc.eserver.org/29941.html</link>
		<guid>http://tc.eserver.org/29941.html</guid>
		<description>Introductory text on Web pages is usually too long, so users skip it. But short intros can increase usability by explaining the remaining content&apos;s purpose.</description>
	</item>
	<item>
		<title>&amp;#35211;&amp;#12388;&amp;#12369;&amp;#12390;&amp;#12418;&amp;#12425;&amp;#12358;&amp;#12383;&amp;#12417;&amp;#12395;&amp;#12399;&amp;#26132;&amp;#12394;&amp;#12364;&amp;#12425;&amp;#12398;&amp;#35328;&amp;#33865;&amp;#12434;&amp;#20351;&amp;#12362;&amp;#12358;</title>
		<link>http://tc.eserver.org/28379.html</link>
		<guid>http://tc.eserver.org/28379.html</guid>
		<description>&amp;#26908;&amp;#32034;&amp;#12434;&amp;#34892;&amp;#12358;&amp;#12392;&amp;#12365;&amp;#12289;&amp;#12518;&amp;#12540;&amp;#12470;&amp;#12398;&amp;#38957;&amp;#12395;&amp;#28014;&amp;#12363;&amp;#12406;&amp;#12398;&amp;#12399;&amp;#12289;&amp;#24931;&amp;#12428;&amp;#35242;&amp;#12375;&amp;#12435;&amp;#12384;&amp;#35328;&amp;#33865;&amp;#12384;&amp;#12290;&amp;#12418;&amp;#12375;&amp;#20351;&amp;#12356;&amp;#21476;&amp;#12373;&amp;#12428;&amp;#12383;&amp;#35328;&amp;#33865;&amp;#12424;&amp;#12426;&amp;#12418;&amp;#12289;&amp;#36896;&amp;#35486;&amp;#12420;&amp;#26032;&amp;#35486;&amp;#12434;&amp;#20351;&amp;#12387;&amp;#12390;&amp;#12356;&amp;#12427;&amp;#12394;&amp;#12425;&amp;#12400;&amp;#12289;&amp;#12518;&amp;#12540;&amp;#12470;&amp;#12399;&amp;#36020;&amp;#26041;&amp;#12398;&amp;#12469;&amp;#12452;&amp;#12488;&amp;#12434;&amp;#12415;&amp;#12388;&amp;#12369;&amp;#12427;&amp;#12371;&amp;#12392;&amp;#12399;&amp;#12394;&amp;#12356;&amp;#12290;</description>
	</item>
	<item>
		<title>Passing the Ten-Second Test</title>
		<link>http://tc.eserver.org/25364.html</link>
		<guid>http://tc.eserver.org/25364.html</guid>
		<description>When you make a web page easy to grasp, in the very first 10 seconds after a visitor arrives, you can both increase its credibility and improve its search engines ranking. Rachel shares precise methods for composing effective text for Web sites.</description>
	</item>
	<item>
		<title>&quot;About Us&quot; -- Presenting Information About an Organization on Its Website</title>
		<link>http://tc.eserver.org/20624.html</link>
		<guid>http://tc.eserver.org/20624.html</guid>
		<description>Study participants searched websites for background information ranging from company history to management biographies and contact details. Their success rate was 70%, leaving much room for usability improvements in the &apos;About Us&apos; designs.</description>
	</item>
	<item>
		<title>Just Say No to Dead Fragments</title>
		<link>http://tc.eserver.org/19018.html</link>
		<guid>http://tc.eserver.org/19018.html</guid>
		<description>A dead fragment of text is what&apos;s left after a usability expert has had his or her way with some perfectly good copy.&#xD;&#xD;The process works a little like this... First, take some great text that engages the reader on a number of levels. Here are a few words from Martin Luther King, Jr.:&#xD;&#xD;&apos;I have a dream that my four children will one day live in a nation where they will not be judged by the color of their skin but by the content of their character.&apos;&#xD;&#xD;Now cut that back to make it more &apos;usable&apos;:&#xD;&#xD;&apos;Have sons judged by character and not color.&apos;&#xD;&#xD;What are you left with? A brief, but dead, fragment. The substance of the communication remains, but the soul has been ripped out of it.</description>
	</item>
	<item>
		<title>Blurbs: How to Write Them for Web Pages</title>
		<link>http://tc.eserver.org/13048.html</link>
		<guid>http://tc.eserver.org/13048.html</guid>
		<description>On the web, a blurb is a line or short paragraph (20-50 words) that evaluates (or at least summarizes) what the reader will find at the other end of a link.  A good blurb should inform, not tease.  Usability testing will help you determine the best way to lay out your blurbs, but this document will help you write the content.</description>
	</item>
	<item>
		<title>Concise, Scannable, and Objective: How to Write for the Web</title>
		<link>http://tc.eserver.org/10531.html</link>
		<guid>http://tc.eserver.org/10531.html</guid>
		<description>Studies of how users read on the Web found that they do not actually read: instead, they scan the text. A study of five different writing styles found that a sample Web site scored 58% higher in measured usability when it was written concisely, 47% higher when the text was scannable, and 27% higher when it was written in an objective style instead of the promotional style used in the control condition and many current Web pages. Combining these three changes into a single site that was concise, scannable, and objective at the same time resulted in 124% higher measured usability.</description>
	</item>
	<item>
		<title>Guidelines for Authoring Comprehensible Web Pages and Evaluating Their Success</title>
		<link>http://tc.eserver.org/10410.html</link>
		<guid>http://tc.eserver.org/10410.html</guid>
		<description>The guidelines presented in this article should enable authors to create Web pages that their readers can understand. They should also enable evaluators to judge the comprehensibility of Web pages. The guidelines are explained and supported by an examination of relevant research and usability studies.</description>
	</item>
	<atom:link href="http://tc.eserver.org/dir/Design/Web-Design/Writing/Usability.xml" rel="self" type="application/rss+xml"/>
</channel>
</rss>