<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>UsableWebb</title>
	<atom:link href="http://usablewebb.com/feed/" rel="self" type="application/rss+xml" />
	<link>http://usablewebb.com</link>
	<description>Usability examples and ideas for improving user experience on the web</description>
	<lastBuildDate>Thu, 18 Feb 2010 17:17:08 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Essential CSS troubleshooting tools</title>
		<link>http://usablewebb.com/2010/02/15/css-troubleshooting-tools/</link>
		<comments>http://usablewebb.com/2010/02/15/css-troubleshooting-tools/#comments</comments>
		<pubDate>Mon, 15 Feb 2010 20:58:44 +0000</pubDate>
		<dc:creator>garrett</dc:creator>
				<category><![CDATA[Tools]]></category>
		<category><![CDATA[css]]></category>
		<category><![CDATA[debug]]></category>
		<category><![CDATA[html]]></category>
		<category><![CDATA[issues]]></category>
		<category><![CDATA[troubleshooting]]></category>

		<guid isPermaLink="false">http://usablewebb.com/?p=25</guid>
		<description><![CDATA[Troubleshooting cascading style sheets (CSS) can be a tedious &#38; time-consuming task. Working with complex CSS written by another developer makes things even more challenging.  Here are my favorite tools for troubleshooting CSS. The best part about the tools is they&#8217;re absolutely free!
Browser tool bars &#38; extensions

Internet Explorer Developer Toolbar &#8211; add-on for Internet Explorer [...]]]></description>
			<content:encoded><![CDATA[<p>Troubleshooting cascading style sheets (CSS) can be a tedious &amp; time-consuming task. Working with complex CSS written by another developer makes things even more challenging.  Here are my favorite tools for troubleshooting CSS. The best part about the tools is they&#8217;re absolutely free!</p>
<h2>Browser tool bars &amp; extensions</h2>
<ul>
<li><a href="http://www.microsoft.com/downloads/details.aspx?FamilyId=E59C3964-672D-4511-BB3E-2D5E1DB91038&amp;displaylang=en">Internet Explorer Developer Toolbar</a> &#8211; add-on for Internet Explorer 6 and 7 that aids in design and debugging of web pages</li>
<li><a title="Firefox Web Developer extension" href="https://addons.mozilla.org/en-US/firefox/addon/60">Firefox Web Developer extension</a> &#8211; Wide a<span id="intellitxt">rray of development tools including WYSIWYG CSS editor<br />
</span></li>
<li><span id="intellitxt"><a title="Aardvark Firefox extension" href="http://karmatics.com/aardvark/">Aardvark Firefox extension</a> &#8211; Shows</span> structure of a page &amp; allows modifications using various keyboard shortcuts</li>
</ul>
<h2>Other tools</h2>
<ul>
<li><a title="XRAY bookmarklet" href="http://www.westciv.com/xray/">XRAY bookmarklet</a></li>
<li><a title="MRI bookmarklet" href="http://www.westciv.com/mri/">MRI bookmarklet</a></li>
</ul>
<p>What are your favorite tools troubleshooting and/or developing HTML and CSS?</p>
]]></content:encoded>
			<wfw:commentRss>http://usablewebb.com/2010/02/15/css-troubleshooting-tools/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Latest Facebook design &amp; ambiguous icons</title>
		<link>http://usablewebb.com/2010/02/09/facebook-ambiguous-icons/</link>
		<comments>http://usablewebb.com/2010/02/09/facebook-ambiguous-icons/#comments</comments>
		<pubDate>Tue, 09 Feb 2010 17:12:01 +0000</pubDate>
		<dc:creator>garrett</dc:creator>
				<category><![CDATA[Icons]]></category>
		<category><![CDATA[Usability]]></category>

		<guid isPermaLink="false">http://usablewebb.com/?p=86</guid>
		<description><![CDATA[
The latest Facebook design has one major issue, the ambiguity of the icons for Friend Requests, Mail and Notifications. 
Name the first thing you think of when you see each of the icons.
 Friend Requests &#8211; Friends, People? What about the requests you get from people who really aren&#8217;t your friends?

 Mail - Chat? Is [...]]]></description>
			<content:encoded><![CDATA[<p><img class="alignleft" style="padding: 6px;" src="http://farm5.static.flickr.com/4005/4343985206_64811a82c8_o.png" alt="Facebook's New Ambiguous Icons" width="77" height="31" /></p>
<p>The latest Facebook design has one major issue, the ambiguity of the icons for Friend Requests, Mail and Notifications. </p>
<p><strong>Name the first thing you think of when you see each of the icons.</strong></p>
<p><img class="alignleft" style="padding: 6px;" src="http://farm5.static.flickr.com/4065/4343262227_bfec3ecebf_o.png" alt="friend-request" width="50" height="62" /><strong> Friend Requests</strong> &#8211; Friends, People? What about the requests you get from people who really aren&#8217;t your friends?</p>
<p><br class="clear" /><br />
<img class="alignleft" style="padding: 6px;" src="http://farm5.static.flickr.com/4024/4343998792_4cf5f4cded_o.png" alt="mail" width="50" height="62" /> <strong>Mail </strong>- Chat? Is Facebook saying mail is the new chat? We&#8217;ve all had email for at least ten years. Why not use the conventional envelope icon?</p>
<p><br class="clear" /><br />
<img class="alignleft" style="padding: 6px;" src="http://farm5.static.flickr.com/4053/4343998818_e92e747916_o.png" alt="notifications" width="50" height="62" /> <strong>Notifications</strong> &#8211; The world? The World Wide Web? Earth?<br />
<br class="clear" /></p>
]]></content:encoded>
			<wfw:commentRss>http://usablewebb.com/2010/02/09/facebook-ambiguous-icons/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Windows Security Essentials misses primary goal of XP users</title>
		<link>http://usablewebb.com/2009/12/21/users-primary-goal-security-essentials/</link>
		<comments>http://usablewebb.com/2009/12/21/users-primary-goal-security-essentials/#comments</comments>
		<pubDate>Mon, 21 Dec 2009 16:55:30 +0000</pubDate>
		<dc:creator>garrett</dc:creator>
				<category><![CDATA[Usability]]></category>
		<category><![CDATA[goals]]></category>
		<category><![CDATA[managing]]></category>
		<category><![CDATA[tasks]]></category>

		<guid isPermaLink="false">http://usablewebb.com/?p=67</guid>
		<description><![CDATA[Windows Security Essentials
I recently discovered Windows Security Essentials and installed it on a new Windows 7 desktop. Satisfied with the product, I went back to the Web site, to see if Windows Security Essentials was compatible with Windows XP.

Was the team not focused enough on user tasks and goals? Or were they just focused on [...]]]></description>
			<content:encoded><![CDATA[<h2>Windows Security Essentials</h2>
<p>I recently discovered <a title="Windows Security Essentials site" href="http://www.microsoft.com/Security_Essentials/">Windows Security Essentials</a> and installed it on a new Windows 7 desktop. Satisfied with the product, I went back to the Web site, to see if Windows Security Essentials was compatible with Windows XP.</p>
<p><a title="Windows Security Essentials site - large" href="http://farm3.static.flickr.com/2560/4146915993_85561ea95a_o.png"><img src="http://farm3.static.flickr.com/2560/4146915993_5623736bbb.jpg" alt="Windows Security Essentials - XP compatible?" width="391" height="500" /></a></p>
<p>Was the team not focused enough on user tasks and goals? Or were they just focused on too narrow a set of users? In the scenario of Windows XP users, they missed the mark.</p>
<h2>Use of images on the page</h2>
<p>The images under the left navigation include Windows 7 and Windows  Vista. The images don&#8217;t tie into the design and look more like advertisements, than a part of the page. The huge image in the center of the page might make traditional marketing types feel warm and cozy, but how does it help users&#8217; accomplish their goals?</p>
<h2>Who are your users, what are their goals?</h2>
<p>Even if the team realized a user with Windows XP is not the primary audience for this page, they should link to a compatibility chart or provide enough information scent on the page to allow an XP user to achieve their goal.</p>
<h2>User experience questions not appropriately researched or analyzed</h2>
<ul>
<li>What are users&#8217; primary  &amp; secondary goals?
<ul>
<li>Is there enough information scent for users&#8217; secondary goals?</li>
</ul>
</li>
<li>Which features are of most importance?
<ul>
<li>How do you draw attention to them?</li>
</ul>
</li>
<li>Are images used effectively?
<ul>
<li>Do the images help achieve users&#8217; goals?</li>
<li>Are images decorative, content or navigational?</li>
</ul>
</li>
</ul>
]]></content:encoded>
			<wfw:commentRss>http://usablewebb.com/2009/12/21/users-primary-goal-security-essentials/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Writing for the web</title>
		<link>http://usablewebb.com/2009/10/13/writing-for-the-web/</link>
		<comments>http://usablewebb.com/2009/10/13/writing-for-the-web/#comments</comments>
		<pubDate>Tue, 13 Oct 2009 21:27:54 +0000</pubDate>
		<dc:creator>garrett</dc:creator>
				<category><![CDATA[Usability]]></category>
		<category><![CDATA[Writing]]></category>
		<category><![CDATA[clear]]></category>
		<category><![CDATA[concise]]></category>

		<guid isPermaLink="false">http://usablewebb.com/?p=52</guid>
		<description><![CDATA[Users come to your site to complete tasks
The web is a functional, task-oriented place. On the web, we want to find the information we’re looking for quickly. We go to the web to get answers to our questions or to complete specific tasks. Imagine the last time you went to your bank web site. Were [...]]]></description>
			<content:encoded><![CDATA[<h3>Users come to your site to complete tasks</h3>
<p>The web is a functional, task-oriented place. On the web, we want to find the information we’re looking for quickly. We go to the web to get answers to our questions or to complete specific tasks. Imagine the last time you went to your bank web site. Were you just browsing, or did you have a specific task in mind, such as finding your account balance, or looking at current interest rates?</p>
<h3>The web often lacks context</h3>
<p>We come to the web to do, and we already have the context when we get to the web site. Print lends itself to length and because print is delivered to the reader, it comes with lots of contextual language.<sup>1</sup> If a visitor comes to your site looking for something specific, and doesn’t find it, they will click the back button and move on to the next site.</p>
<h3>Understanding how users read on the web</h3>
<p>It&#8217;s easy to think writing for the web is similar to writing for print. A first instinct is to obtain the exact text from printed materials and copy and paste it to your web site. If you do this, you should realize users don&#8217;t read web pages word for word; they generally skim the contents looking for specific trigger words. To ensure success, web writers must understand how people use web sites and how they read on the web.</p>
<h3>Research &#8211; how users read on the web</h3>
<p>To prove these points, in the summer of 1997, three studies were conducted at the SunSoft usability laboratories in Menlo Park, CA. During the studies, eighty-one randomly selected users ranging from highly-technical to novice were asked to perform various tasks on a number of pre-selected web sites.</p>
<p>The first and second studies were exploratory and qualitative, aimed at generating insight into how users read web pages. The third study was a measurement study aimed at quantifying the potential benefits from some of the most promising writing styles identified in the first two studies.</p>
<h3>Conclusions from the studies</h3>
<p>The studies concluded that scan-able, concise writing styles made a positive difference in user performance and subjective satisfaction. The studies also showed that 79 percent don’t read web pages as they read print. Instead of reading from beginning to end, they scan the page, looking for words or phrases related to their desired task<sup>2</sup>.</p>
<h3>Writing clear and concise web content</h3>
<p>Web writers  must write clear and concise text using a variety of formatting options. Some of these options include:</p>
<ul>
<li>sticking to one idea per paragraph</li>
<li>writing and using concise sub-headings (which summarize paragraphs)</li>
<li>using numbered or bulleted lists</li>
</ul>
<p>It&#8217;s also a good idea to get rid of wordy sentences and try to cut the word count to half that of conventional writing. The web isn’t about communicating with long words, and overly descriptive sentences. The web is about communication with speed. Use simple words. For example, use “tried” instead of “attempted.”</p>
<h3>Real-life web writing examples</h3>
<p>Review the scenarios below. Remember, visitors come to a site to accomplish a task: such as, viewing their checking account balance, or logging in to their college web site to submit an assignment.</p>
<p>In this example, a family physician is trying to find health care reform information for his or her patients. This text was taken from the home page of American Academy of Family Physicians.</p>
<p style="padding-left: 30px;"><strong>Original Version:</strong><br />
With the health care reform debate entering its most critical period, patients across the country are asking their family physician for answers to questions such as &#8212; &#8220;Which health reform claims are true? Where can I find a bipartisan source for more information? Why are the reform proposals being reviewed by Congress important to me, your patient?&#8221; The AAFP has created a <a href="#">one-page information sheet</a> (1-page PDF) that physicians can download and share with their patients.</p>
<p style="padding-left: 30px;"><strong>Rewritten Version:</strong><br />
With health care reform entering a critical point, patients are looking for answers to health care reform questions. Give them answers with the <a href="#">health care reform patient handout</a> (1-pg PDF).</p>
<p><strong>Summary of changes:</strong> In this example, sentences were too wordy. The questions a patient might ask were removed. If a physician was seeking this information, he or she has likely encountered the questions already.</p>
<p>The next scenario is a customer of Poplar Bluff Federal Credit Union (PBFCU) who wants to learn more about online banking. This text was taken from the online banking page on the PBCFU web site.</p>
<p style="padding-left: 30px;"><strong>Original Version:</strong><br />
Internet Home Banking &#8211; The Credit Union Way<br />
Developed exclusively for FLEX Credit Unions, FLEXTeller is the latest in Internet Banking technology. Accessible through any web Browser, FLEXTeller provides you with real time connection and a secure site in which to view account information. Members may make transfers between accounts, view and download account history, view recent check clearings, view cleared checks and even apply for a loan, all on-line. FLEXTeller gives you access to your financial information 24 hours a day, 7 days a week.</p>
<p style="padding-left: 30px;"><strong>Rewritten Version:</strong><br />
Poplar Bluff Federal Credit Union uses the latest secure technology, so you can feel safe banking online. Using online banking you may:<br />
* Make transfers between accounts<br />
* View and download recent transaction info<br />
* View recent and cleared checks<br />
* Apply for a loan</p>
<p><strong>Summary of changes:</strong> In this example, much of text was omitted. Most visitors would have no idea what FLEXTeller is, and because the user is already on the site, there is no need to include, “Accessible through any web Browser.” The list of online banking tasks was split into a bulleted list to improve scan ability. Finally, most people realize the web is 24 hours a day, 7 days a week.</p>
<h3>Writing meaningful link names</h3>
<p>When linking to files or other web pages, use care not to make the link name, “click here.” Link names should describe what is being linked to and be worked into sentences naturally. Longer link names can be better if they provide relevant contextual information<sup>3</sup>. Descriptive link names also let the user scan the page to find information they seek, without reading entire sentences or paragraphs. If you’re linking to a document, such as a Word file or PDF, be sure to include the file type in parenthesis after the link name.</p>
<p style="padding-left: 30px;"><strong>Example link names:</strong><br />
<a href="#">Click here</a> for more information about XYZ.<br />
<a href="#">Click here</a> to see the earnings for your school.</p>
<p style="padding-left: 30px;"><strong>Descriptive link names:</strong><br />
<a href="#">Information about XYZ</a>.<br />
<a href="#">View earnings for your school</a>.</p>
<p>References</p>
<ol>
<li>McGovern, Gerry. &#8220;How web is different from print.&#8221; New Thinking 08 Dec 2008: web. 21 Sep 2009.</li>
<li>Morkes, John, and Nielsen, Jakob. &#8220;Concise, SCANNABLE, and Objective: How to Write for the web.&#8221; Useit.com: Jakob Nielsen&#8217;s website. 01 Jan 1997. Nielsen, Jakob, web. 21 Sep 2009.</li>
<li>Brinck, Tom, Darren Gergle, and Scott Wood. Usability for the web: designing web sites that work. Illustrated. San Francisco, CA: Morgan Kaufmann, 2002. Print.</li>
</ol>
]]></content:encoded>
			<wfw:commentRss>http://usablewebb.com/2009/10/13/writing-for-the-web/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>User Experience Search Engines</title>
		<link>http://usablewebb.com/2009/09/02/user-experience-search-engine/</link>
		<comments>http://usablewebb.com/2009/09/02/user-experience-search-engine/#comments</comments>
		<pubDate>Thu, 03 Sep 2009 00:23:50 +0000</pubDate>
		<dc:creator>garrett</dc:creator>
				<category><![CDATA[Usability]]></category>

		<guid isPermaLink="false">http://usablewebb.com/?p=32</guid>
		<description><![CDATA[I&#8217;ve set up a user interface design / user experience search engine (#1 below). Thanks to @cbehrlich for the heads up on her user experience search engine (#2 below).

User experience search engine #1: http://snipurl.com/uxsearch
User experience search engine #2: http://tinyurl.com/UI-UX-Search

The searches engines return results from trusted user experience and user interface design Web sites. If you [...]]]></description>
			<content:encoded><![CDATA[<p>I&#8217;ve set up a user interface design / user experience search engine (#1 below). Thanks to <a title="@cbehrlich" href="http://twitter.com/cbehrlich">@cbehrlich</a> for the heads up on her user experience search engine (#2 below).</p>
<ul>
<li><strong><a title="http://snipurl.com/uxsearch" href="http://www.google.com/cse/home?cx=001419898076427528680%3Aeocfus0gesw&amp;hl=en">User experience search engine #1</a>: </strong><a title="User Interface Design and User Experience Search" onclick="javascript:pageTracker._trackPageview('/outgoing/snipurl.com/uxsearch');" href="http://snipurl.com/uxsearch">http://snipurl.com/uxsearch</a></li>
<li><strong><a title="http://tinyurl.com/UI-UX-Search" href="http://tinyurl.com/UI-UX-Search">User experience search engine #2</a>: </strong><a title="UX Search Engine" href="http://tinyurl.com/UI-UX-Search">http://tinyurl.com/UI-UX-Search</a></li>
</ul>
<p>The searches engines return results from trusted user experience and user interface design Web sites. If you work in or write about user experience and you&#8217;d like to contribute, <a title="contact me" href="http://www.usablewebb.com/about/">contact me</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://usablewebb.com/2009/09/02/user-experience-search-engine/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Best practices for naming documents and files for web</title>
		<link>http://usablewebb.com/2009/09/02/best-practices-naming-documents-files-web/</link>
		<comments>http://usablewebb.com/2009/09/02/best-practices-naming-documents-files-web/#comments</comments>
		<pubDate>Thu, 03 Sep 2009 00:15:15 +0000</pubDate>
		<dc:creator>garrett</dc:creator>
				<category><![CDATA[Usability]]></category>

		<guid isPermaLink="false">http://usablewebb.com/?p=27</guid>
		<description><![CDATA[To ensure users don’t have trouble downloading files (Word, PowerPoint, Excel files or PDF’s), follow these guidelines when naming files to be uploaded and used on your Web site.
Remove spaces from file names
 (hyphens are okay to separate words)
Some web browsers may not recognize the spaces. Spaces can also cause links sent in e-mail to [...]]]></description>
			<content:encoded><![CDATA[<p>To ensure users don’t have trouble downloading files (Word, PowerPoint, Excel files or PDF’s), follow these guidelines when naming files to be uploaded and used on your Web site.</p>
<h3><strong>Remove spaces from file names</strong></h3>
<p><strong> </strong>(hyphens are okay to separate words)</p>
<p>Some web browsers may not recognize the spaces. Spaces can also cause links sent in e-mail to break.</p>
<ul>
<li><strong>Marketing Brochure.pdf </strong></li>
<li><em>should be changed to: </em></li>
<li><strong>MarketingBrochure.pdf</strong></li>
</ul>
<h3>Remove any non-alphanumeric characters</h3>
<p>(hyphens are okay to separate words)Non-alphanumeric characters cause problems in web browsers and e-mail programs.</p>
<ul>
<li><strong>New Brochure #1.pdf</strong></li>
<li><em>should be changed to:</em><strong> </strong></li>
<li><strong>NewBrochure1.pdf</strong></li>
</ul>
<h3>Simple is better</h3>
<p>Descriptive file names help users identify file contents (some users may stumble upon your file via search). However, overly descriptive file names create really long web addresses.</p>
<ul>
<li><strong>Letter From a Reader on March 15.pdf </strong></li>
<li><em>should be changed to: </em><strong> </strong></li>
<li><strong>LetterFromReader.pdf<br />
</strong></li>
</ul>
<h3>Be consistent and thoughtful</h3>
<p>(use dates only when relevant)</p>
<p>If you have a weekly or monthly PDF newsletter, be <strong>consistent </strong>and thoughtful when naming your files. Use dates in your file name<strong> only </strong>when they are relevant to the content.</p>
<p>Use the following date format in file names: YYYYMMDD.pdf.</p>
<ul>
<li><strong>CompanyNews030209.pdf </strong></li>
<li><em>should be changed to: </em><strong> </strong></li>
<li><strong>CompanyNews20090309.pdf</strong></li>
</ul>
<p>Following this date format will ensure your files are sorted chronologically in Google and other search results.</p>
]]></content:encoded>
			<wfw:commentRss>http://usablewebb.com/2009/09/02/best-practices-naming-documents-files-web/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Writing succinctly</title>
		<link>http://usablewebb.com/2008/12/02/writing-succinctly/</link>
		<comments>http://usablewebb.com/2008/12/02/writing-succinctly/#comments</comments>
		<pubDate>Tue, 02 Dec 2008 19:14:29 +0000</pubDate>
		<dc:creator>garrett</dc:creator>
				<category><![CDATA[Writing]]></category>
		<category><![CDATA[architecture]]></category>
		<category><![CDATA[information]]></category>
		<category><![CDATA[web]]></category>

		<guid isPermaLink="false">http://usablewebb.com/?p=18</guid>
		<description><![CDATA[Below is a paragraph I found on the home page of a popular medical association.
Before: As XYZ association keeps tabs on persistent issues with health plans that impede your ability to care for patients, a few have come to the forefront recently. In response, we&#8217;ve created new letter templates for our members that should simplify [...]]]></description>
			<content:encoded><![CDATA[<p>Below is a paragraph I found on the home page of a popular medical association.</p>
<p><em>Before: As XYZ association keeps tabs on persistent issues with health plans that impede your ability to care for patients, a few have come to the forefront recently. In response, we&#8217;ve created new <a href="#">letter templates</a> for our members that should simplify the process of communicating these issues to health plans. Among other things, the letters address fair payment for immunizations, group visits and mental health services. Easy to download from our Web site, these templates were designed to help you make your practice less about the process, and more about the patients.</em></p>
<hr />
<p>I&#8217;ve rewritten the paragraph (below) to be more web-friendly.</p>
<p><em>After: In response to your requests, we have created <a href="#">templates</a> to simplify communication to health plans regarding issues that impede your ability to care for patients. The <a href="#">templates</a> address fair payment for immunizations, group visits and mental health services.</em></p>
<p>More information:</p>
<ul>
<li><a title="Plain Language: Wordiness made spare" href="http://www.plainlanguage.gov/examples/before_after/wordiness.cfm">Plain Language: Wordiness Made Spare</a></li>
<li><a title="Seven Qualities of Highly Successful Web Writing" href="http://www.clickz.com/833861">The Seven Qualities of Highly Successful Web Writing</a></li>
</ul>
]]></content:encoded>
			<wfw:commentRss>http://usablewebb.com/2008/12/02/writing-succinctly/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Providing highly relevant user feedback</title>
		<link>http://usablewebb.com/2008/09/15/providing-highly-relevant-user-feedback/</link>
		<comments>http://usablewebb.com/2008/09/15/providing-highly-relevant-user-feedback/#comments</comments>
		<pubDate>Tue, 16 Sep 2008 00:55:05 +0000</pubDate>
		<dc:creator>garrett</dc:creator>
				<category><![CDATA[Usability]]></category>

		<guid isPermaLink="false">http://usablewebb.com/?p=14</guid>
		<description><![CDATA[Web site features and functionality continue to grow, making it important to carefully consider and display only the most relevant feedback to your users.
I came across this example when trying to find a service to update my status on various social networks. To help uncover the problem and the solution you must understand how your [...]]]></description>
			<content:encoded><![CDATA[<p>Web site features and functionality continue to grow, making it important to carefully consider and display only the most relevant feedback to your users.</p>
<p>I came across this example when trying to find a service to update my status on various social networks. To help uncover the problem and the solution you must understand how your application will be used.</p>
<p>This example discusses the default link or trimming behavior on HelloTxt.com and Ping.fm, popular web status update services. Link trimming is important because many micro-blogs, such as Twitter, Yammer and Facebook limit your post to about 140 characters.</p>
<p><img class="flickr-medium" style="border: 1px solid black;" src="http://farm4.static.flickr.com/3174/2836265453_5069b93b4f_o.png" border="1" alt="hellotxt.com post window" /><br />
HelloTxt.com provides no indication they will shorten links automatically when posted.</p>
<p><img class="flickr-medium" style="border: 1px solid black;" src="http://farm4.static.flickr.com/3173/2836265501_4701441ce8_o.jpg" border="1" alt="hellotxt.com post result on twitter" width="438" height="80" /></p>
<p>If you have shortened the link or you&#8217;re posting a short link, the hellotxt.com link (posted on Twitter above) may be longer than your original link.</p>
<p><img class="flickr-medium" style="border: 1px solid black;" src="http://farm4.static.flickr.com/3027/2836265529_73c52f1517_o.png" alt="ping.fm post window" /></p>
<p>Ping.fm provides relevant user feedback by indicating links will be automatically trimmed. You can disable Ping.fm link shortening by putting an asterisk in front of the desired link. </p>
]]></content:encoded>
			<wfw:commentRss>http://usablewebb.com/2008/09/15/providing-highly-relevant-user-feedback/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Periodically check your site for broken links</title>
		<link>http://usablewebb.com/2008/09/03/periodically-check-your-site-for-broken-links/</link>
		<comments>http://usablewebb.com/2008/09/03/periodically-check-your-site-for-broken-links/#comments</comments>
		<pubDate>Wed, 03 Sep 2008 14:48:16 +0000</pubDate>
		<dc:creator>garrett</dc:creator>
				<category><![CDATA[Quality]]></category>

		<guid isPermaLink="false">http://usablewebb.com/?p=13</guid>
		<description><![CDATA[Use tools such as Mozilla Firefox and the Link Evaluator extension to quickly check all links on a given page. Another way to check links is to use Firefox or Internet Explorer 7, and hold down Ctrl ( on Mac) on your keyboard as you click each link. The new links will open in tabs [...]]]></description>
			<content:encoded><![CDATA[<p>Use tools such as <a title="Mozilla Firefox web browser" href="http://www.getfirefox.com/">Mozilla Firefox</a> and the <a title="Link Evaluator extension for Firefox" href="http://snipurl.com/3mkj0">Link Evaluator extension</a> to quickly check all links on a given page. Another way to check links is to use Firefox or Internet Explorer 7, and hold down Ctrl (<img src="http://www.usablewebb.com/images/open-apple.gif" border="0" alt="Open Apple - cmd key" /> on Mac) on your keyboard as you click each link. The new links will open in tabs of the current browser window. Quickly flip through the tabs by pressing Ctrl-Tab (or <img src="http://www.usablewebb.com/images/open-apple.gif" border="0" alt="Open Apple - cmd key" /> Tab) on your keyboard, to close a tab press Ctrl-W (or <img src="http://www.usablewebb.com/images/open-apple.gif" border="0" alt="Open Apple - cmd key" /> W).</p>
]]></content:encoded>
			<wfw:commentRss>http://usablewebb.com/2008/09/03/periodically-check-your-site-for-broken-links/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Click here and other meaningless link text</title>
		<link>http://usablewebb.com/2008/06/16/click-here-meaningless-link-text/</link>
		<comments>http://usablewebb.com/2008/06/16/click-here-meaningless-link-text/#comments</comments>
		<pubDate>Tue, 17 Jun 2008 04:06:54 +0000</pubDate>
		<dc:creator>garrett</dc:creator>
				<category><![CDATA[Usability]]></category>

		<guid isPermaLink="false">http://usablewebb.com/?p=5</guid>
		<description><![CDATA[The urge to insert the phrase &#8220;click here&#8221; or &#8220;more&#8221; is somewhat common among content contributors when creating links on a page. Non-descriptive link text makes your site difficult to scan and causes accessibility and search engine optimization (SEO) issues. Replacing the phrase click here with a meaningful word or phrase (which makes sense out [...]]]></description>
			<content:encoded><![CDATA[<p>The urge to insert the phrase &#8220;click here&#8221; or &#8220;more&#8221; is somewhat common among content contributors when creating links on a page. Non-descriptive link text makes your site difficult to scan and causes accessibility and search engine optimization (SEO) issues. Replacing the phrase click here with a meaningful word or phrase (which makes sense out of context) will make your site more user-friendly.</p>
<p><strong>Example 1</strong><br />
Before: For the latest news, <a href="#">Click here</a>.<br />
After: Read the <a href="#">latest news on Medicare Bill (HR 6331)</a>.</p>
<p><strong>Example 2</strong><br />
Before: To download the registration form, <a href="#">click here</a>.<br />
After: Download the Spring Fling <a href="#">Registration Form</a> (PDF file).</p>
<p><strong>More Information</strong></p>
<ul>
<li><span style="font-weight: normal;"><a title="Trigger words - users love 'em!" href="http://www.webusability.co.uk/2008/triger-words-users-love-them"><em><span style="font-weight: normal;">Trigger words &#8211; users love &#8216;em!<br />
</span></em></a></span></li>
<li><em><a href="http://www.deyalexander.com/publications/clickhere.html"><span style="font-weight: normal;">Don&#8217;t &#8216;click here&#8217;: writing meaningful link text</span></a></em></li>
<li><em><a href="http://www.w3.org/QA/Tips/noClickHere"><span style="font-weight: normal;">Don&#8217;t say &#8220;click here&#8221; not everyone will be clicking</span></a></em></li>
</ul>
]]></content:encoded>
			<wfw:commentRss>http://usablewebb.com/2008/06/16/click-here-meaningless-link-text/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
