<?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>Good Usability &#187; quick tips</title>
	<atom:link href="http://www.goodusability.co.uk/tag/quick-tips/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.goodusability.co.uk</link>
	<description></description>
	<lastBuildDate>Fri, 20 Apr 2012 09:11:32 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=</generator>
		<item>
		<title>Short and simple sentences</title>
		<link>http://www.goodusability.co.uk/2009/01/05/short-and-simple-sentences/</link>
		<comments>http://www.goodusability.co.uk/2009/01/05/short-and-simple-sentences/#comments</comments>
		<pubDate>Mon, 05 Jan 2009 08:50:51 +0000</pubDate>
		<dc:creator>David Hamill</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[quick tips]]></category>
		<category><![CDATA[web writing]]></category>

		<guid isPermaLink="false">http://www.goodusability.co.uk/?p=392</guid>
		<description><![CDATA[When you&#8217;re writing for the web, try to keep your sentences under 20 words in length. Your content will be easier to read this way. This is because it&#8217;s easier to read a few short sentences than it is to read one big one. Write a long sentence first It&#8217;s often quicker and easier to [...]]]></description>
			<content:encoded><![CDATA[<p>When you&#8217;re <a href="http://www.goodusability.co.uk/2008/10/is-it-web-writing-or-just-good-writing/">writing for the web</a>, try to keep your sentences under 20 words in length. Your content will be easier to read this way. This is because it&#8217;s easier to read a few short sentences than it is to read one big one.</p>
<h3>Write a long sentence first</h3>
<p>It&#8217;s often quicker and easier to write the sentence as you normally would and then change it after you&#8217;ve finished. Look for commas, semi colons and instances of the word &#8220;which&#8221; as opportunities to begin a new sentence.</p>
<p>You will rarely need to use more than one or two commas in a sentence. Have a go at splitting your sentence in two if you find you&#8217;ve got more than two commas in it. You might need to reword it a little.</p>
<h3>It&#8217;s not always possible</h3>
<p>Sometimes your sentence will need to be longer than 20 words. If so that&#8217;s fine. As long as you&#8217;re trying to keep your sentences short then you&#8217;ll be making a big difference.</p>
<h3>Do this so as to not write badly</h3>
<p>When people try to sound intellectual, they often use the term &#8220;as to&#8221; when something like &#8220;of&#8221; would be better. Using &#8220;as to&#8221; often complicates the sentence unnecessarily. It&#8217;s not just an extra word that&#8217;s the problem. An extra word won&#8217;t make a massive difference. The problem is caused by the extra thought required to translate the sentence back into plain English. Here&#8217;s an example:</p>
<blockquote><p>The results should be clearly structured with a relevant title and also a brief description as to what is contained in the listing&#8230;</p></blockquote>
<p>Yes very clever, but the following sentence is easier to read:</p>
<blockquote><p>The results should be clearly structured with a relevant title and a brief description of what is contained in the listing&#8230;</p></blockquote>
<p>All I did was remove the word &#8220;also&#8221; and replaced &#8220;as to&#8221; for &#8220;of&#8221;. I haven&#8217;t dumbed this sentence down at all. I just made it easier to read and understand.</p>
<h3>Favour simple over short</h3>
<p>Don&#8217;t make your sentences complicated just so that you can lose a few words. A long simple sentence will often be easier to read than a shorter complex one.</p>
<h3>Did you find this useful?</h3>
<p>If so, you might like to read:</p>
<ul>
<li><a href="http://www.goodusability.co.uk/2008/10/trigger-words-versus-customer-carewords/">Trigger words versus Customer Carewords</a></li>
<li><a href="http://www.goodusability.co.uk/2008/10/sub-headers-are-navigation/">Sub-headers are navigation</a></li>
<li><a href="http://www.goodusability.co.uk/2008/10/is-it-web-writing-or-just-good-writing/">Is it web writing or just good writing?</a></li>
</ul>
]]></content:encoded>
			<wfw:commentRss>http://www.goodusability.co.uk/2009/01/05/short-and-simple-sentences/feed/</wfw:commentRss>
		<slash:comments>10</slash:comments>
		</item>
		<item>
		<title>Using a:focus in CSS &#8211; quick tip</title>
		<link>http://www.goodusability.co.uk/2008/12/22/using-afocus-in-css-quick-tip/</link>
		<comments>http://www.goodusability.co.uk/2008/12/22/using-afocus-in-css-quick-tip/#comments</comments>
		<pubDate>Mon, 22 Dec 2008 08:00:15 +0000</pubDate>
		<dc:creator>David Hamill</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[navigation]]></category>
		<category><![CDATA[quick tips]]></category>

		<guid isPermaLink="false">http://www.goodusability.co.uk/?p=380</guid>
		<description><![CDATA[In web design, we often automatically think of blind users when we talk about web accessibility. But a lot of disabled users are not blind. Some people will use a keyboard to navigate your site despite being able to see the screen. Unfortunately browsers aren&#8217;t that great at highlighting the link that is in focus. [...]]]></description>
			<content:encoded><![CDATA[<p>In web design, we often automatically think of blind users when we talk about web accessibility. But a lot of disabled users are not blind. Some people will use a keyboard to navigate your site despite being able to see the screen. Unfortunately browsers aren&#8217;t that great at highlighting the link that is in focus.</p>
<h3>Helping keyboard only users</h3>
<p>You can help your keyboard only users by applying a clear visual property for a:focus within your stylesheet. When your users tab through the links on your website, they will then be able to see which ones are in focus.</p>
<p>Tab through the links on this page with your keyboard to see what I mean. Here&#8217;s the CSS I use:</p>
<p><em>a:focus{ color:#fff; background: #C40064; }</em></p>
<h3>Form fields</h3>
<p>You can also use this effect on your form fields. Just don&#8217;t expect it to work in Internet Explorer<em>. </em>The Focus pseudo class only works on the &lt;a&gt; tag in Internet Explorer.</p>
<h3>What are quick tips?</h3>
<p>My <a href="/tag/quick-tips/">quick tips</a> are bits of advice Iâ€™ve given lots of times, but theyâ€™re not really worth writing a big article about.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.goodusability.co.uk/2008/12/22/using-afocus-in-css-quick-tip/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>Good site search &#8211; quick tips</title>
		<link>http://www.goodusability.co.uk/2008/12/09/good-site-search-quick-tips/</link>
		<comments>http://www.goodusability.co.uk/2008/12/09/good-site-search-quick-tips/#comments</comments>
		<pubDate>Tue, 09 Dec 2008 20:34:08 +0000</pubDate>
		<dc:creator>David Hamill</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[quick tips]]></category>
		<category><![CDATA[search]]></category>

		<guid isPermaLink="false">http://www.goodusability.co.uk/?p=332</guid>
		<description><![CDATA[There&#8217;s a few quick tips here but they&#8217;re all on site search so I&#8217;ve kept them together. Provide a box not a link If you want people to see your site search then don&#8217;t provide a &#8216;search&#8217; link on every page. Instead provide the search box itself. Your users are more likely to notice it, [...]]]></description>
			<content:encoded><![CDATA[<p>There&#8217;s a few quick tips here but they&#8217;re all on site search so I&#8217;ve kept them together.</p>
<h3>Provide a box not a link</h3>
<p>If you want people to see your site search then don&#8217;t provide a &#8216;search&#8217; link on every page. Instead provide the search box itself. Your users are more likely to notice it, so it will be used more.</p>
<h3>No search is better than a bad search</h3>
<p>If your search sucks, then lose it. Take it off the page. Some people will spend ages struggling with a bad search engine. If they can&#8217;t find it with search then they often think it doesn&#8217;t exist.</p>
<h3>Take the Google logo off</h3>
<p>If you have some sort of Google powered search then don&#8217;t put a Google logo on it. Some people will mistake it for a web search.</p>
<h3>What are quick tips?</h3>
<p>My <a href="http://www.goodusability.co.uk/tag/quick-tips/">quick tips</a> are bits of advice I&#8217;ve given lots of times, but they&#8217;re not really worth writing a big article about.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.goodusability.co.uk/2008/12/09/good-site-search-quick-tips/feed/</wfw:commentRss>
		<slash:comments>9</slash:comments>
		</item>
		<item>
		<title>Writing numbers &#8211; quick tip</title>
		<link>http://www.goodusability.co.uk/2008/12/08/writing-numbers/</link>
		<comments>http://www.goodusability.co.uk/2008/12/08/writing-numbers/#comments</comments>
		<pubDate>Mon, 08 Dec 2008 23:35:01 +0000</pubDate>
		<dc:creator>David Hamill</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[quick tips]]></category>
		<category><![CDATA[web writing]]></category>

		<guid isPermaLink="false">http://www.goodusability.co.uk/?p=328</guid>
		<description><![CDATA[When you include numbers on your website, use numerics rather than spelling out the word. It&#8217;s quicker for your user to digest. It also works better when the number is the main thing your user is looking for. Try it out for yourself. Go to the Wikipedia page on Tigers and find the approximate number [...]]]></description>
			<content:encoded><![CDATA[<p>When you include numbers on your website, use numerics rather than spelling out the word. It&#8217;s quicker for your user to digest. It also works better when the number is the main thing your user is looking for.</p>
<p>Try it out for yourself. Go to the <a href="http://en.wikipedia.org/wiki/Tiger">Wikipedia page on Tigers</a> and find the approximate number of cubs in a litter. It&#8217;s quite difficult to find because the page is big. But now try to find the average number of hunts a tiger makes before it tends to get a kill. It&#8217;s even harder because the figure is written as a word and you&#8217;re scanning the page for a number.</p>
<h3>Phone numbers</h3>
<p>You can improve the findability of phone numbers even further by making them bold.</p>
<h3>What are quick tips?</h3>
<p>My <a href="http://www.goodusability.co.uk/tag/quick-tips/">quick tips</a> are bits of advice I&#8217;ve given lots of times, but they&#8217;re not really worth writing a big article about.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.goodusability.co.uk/2008/12/08/writing-numbers/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>

