<?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>Accessible Web Design &#187; Web Design</title>
	<atom:link href="http://accessibleweb.eu/category/web-design/feed/" rel="self" type="application/rss+xml" />
	<link>http://accessibleweb.eu</link>
	<description>design, build, test and consultancy</description>
	<lastBuildDate>Mon, 07 Nov 2011 14:09:48 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
		<item>
		<title>Attention to Detail</title>
		<link>http://accessibleweb.eu/2011/02/attention-to-detail/</link>
		<comments>http://accessibleweb.eu/2011/02/attention-to-detail/#comments</comments>
		<pubDate>Tue, 08 Feb 2011 11:09:27 +0000</pubDate>
		<dc:creator>Richard</dc:creator>
				<category><![CDATA[Web Design]]></category>

		<guid isPermaLink="false">http://accessibleweb.eu/?p=126</guid>
		<description><![CDATA[I&#8217;m not the worlds best speller (although I&#8217;m not too bad) and I don&#8217;t always get my commas right, but I like to think that I take some care over the presentation of information. I&#8217;m sure many people don&#8217;t notice spelling mistakes but they tend to shout out at me. Even when I am skimming [...]]]></description>
			<content:encoded><![CDATA[<div class="tweetmeme_button" style="float: right; margin-left: 10px;">
			<a href="http://api.tweetmeme.com/share?url=http%3A%2F%2Faccessibleweb.eu%2F2011%2F02%2Fattention-to-detail%2F"><br />
				<img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Faccessibleweb.eu%2F2011%2F02%2Fattention-to-detail%2F&amp;style=normal&amp;b=2" height="61" width="50" /><br />
			</a>
		</div>
<p>I&#8217;m not the worlds best speller (although I&#8217;m not too bad) and I don&#8217;t always get my commas right, but I like to think that I take some care over the presentation of information. I&#8217;m sure many people don&#8217;t notice spelling mistakes but they tend to shout out at me. Even when I am skimming a page I can get that sudden nagging feeling that something in the text isn&#8217;t quite right, and I have to read it through properly to find it (perhaps that could be a good way of attracting attention by introducing deliberete errors).</p>
<p>Examples of errors pop up all the time and often they are obviously typos (e.g. a missing letter in a word). Sometimes though a webpage has a few mistakes and I start to think that maybe there hasn&#8217;t been enough attention to detail put into the creation of the content.</p>
<p>I recently came across a business website that looked OK initially but then I started finding odd spelling errors, the occasional missing word, and lots of inappropriate Capitalisation of words. Now I know that this doesn&#8217;t really matter but it jars with me and in fact the business concerned was a funeral directors. Should a funeral director be able to spell correctly and use grammar properly? Absolutely, it doesn&#8217;t matter at all as far as the website goes, I could understand everything written there. What would matter though would be if they produced an order of service for a funeral that wasn&#8217;t 100% correct, or worse still made mistakes in some of the official paperwork that goes with the territory (for example moving a body from one country to another is an expensive and bureuacratic process and one mistake on a form could lead to expensive delays not to mention emotional anguish). Of course where they really fail now is that I am highly unlikely to mention them or recommend them to anyone arranging a funeral, and if their name comes up in conversation I am quite likely to mention that I probably wouldn&#8217;t use them myself, becuase of their lack of attention to detail.</p>
<p>No doubt I have made some mistakes in this post (but &#8220;Capitalisation&#8221; and &#8220;deliberete&#8221; were both deliberate), so I don&#8217;t mind being referred to as Mr Pot (calling Mr Kettle black).</p>
<p>What do you think? Am I being too picky or are these things still important in the 21st century?</p>
]]></content:encoded>
			<wfw:commentRss>http://accessibleweb.eu/2011/02/attention-to-detail/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Why Google Search is not as good as it should be</title>
		<link>http://accessibleweb.eu/2011/01/why-google-search-isnt-as-good-as-it-could-be/</link>
		<comments>http://accessibleweb.eu/2011/01/why-google-search-isnt-as-good-as-it-could-be/#comments</comments>
		<pubDate>Mon, 31 Jan 2011 14:14:27 +0000</pubDate>
		<dc:creator>Richard</dc:creator>
				<category><![CDATA[Web Design]]></category>

		<guid isPermaLink="false">http://accessibleweb.eu/?p=128</guid>
		<description><![CDATA[Just saying that could probably have me sent to the Tower of London for treason. However there are good reasons for thinking that search isn&#8217;t all it could be (and it doesn&#8217;t just apply to Google). Search engines tend to favour older information on the basis that it wouldn&#8217;t still be around if it wasn&#8217;t [...]]]></description>
			<content:encoded><![CDATA[<div class="tweetmeme_button" style="float: right; margin-left: 10px;">
			<a href="http://api.tweetmeme.com/share?url=http%3A%2F%2Faccessibleweb.eu%2F2011%2F01%2Fwhy-google-search-isnt-as-good-as-it-could-be%2F"><br />
				<img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Faccessibleweb.eu%2F2011%2F01%2Fwhy-google-search-isnt-as-good-as-it-could-be%2F&amp;style=normal&amp;b=2" height="61" width="50" /><br />
			</a>
		</div>
<p>Just saying that could probably have me sent to the Tower of London for treason. However there are good reasons for thinking that search isn&#8217;t all it could be (and it doesn&#8217;t just apply to Google).</p>
<p>Search engines tend to favour older information on the basis that it wouldn&#8217;t still be around if it wasn&#8217;t worthy. Fair enough, but that doesn&#8217;t take into account the vast swathes of abandoned information that is out of date.</p>
<p>Of more concern to me though is the problem diagnosis issue. If I want to find out why the PC no longer recognises the scanner in the printer for example, the first thing I do is a Google search. I tend to be quite specific with searches, particularly error messages and I usually get back some useful looking results. However my heart now sinks when I see that most of the results are from discussion forums. What often happens is that I click on one that looks closest to what I am trying to find, then trawl through several pages of discussion about the problem (which is often spot-on regarding my specific details) only to find two or three posts at the end saying something like &#8220;so has anyone found a solution to this problem yet&#8221;. There may be better search terms that I could use to improve my return but I haven&#8217;t found them yet, and I am wary of trying things like adding &#8220;solution&#8221; on the end because I don&#8217;t really think that is likely to improve things.</p>
<p>To say this is all Google&#8217;s fault is of course not entirely true. The real problem here is the lack of a semantic web which in theory would make finding solutions to particular problems much easier. However, the search engines claim to be improving the relevance of their results all the time (and of course the only reason they exist is to sell the sponsored listings for which they can command more money if search results are better).</p>
<p>What do you think? It there a better way of orgnaising/running forums that may help? Do you have some nifty search term tips that can filter out some of these circular journeys? </p>
<p>Please keep the conversation going with your comments here.</p>
]]></content:encoded>
			<wfw:commentRss>http://accessibleweb.eu/2011/01/why-google-search-isnt-as-good-as-it-could-be/feed/</wfw:commentRss>
		<slash:comments>5</slash:comments>
		</item>
		<item>
		<title>Hosting Uptime Guarantees &#8211; Are They Worth the Paper They Aren&#8217;t Printed on?</title>
		<link>http://accessibleweb.eu/2010/05/hosting-uptime-guarantees-are-they-worth-the-paper-they-arent-printed-on/</link>
		<comments>http://accessibleweb.eu/2010/05/hosting-uptime-guarantees-are-they-worth-the-paper-they-arent-printed-on/#comments</comments>
		<pubDate>Tue, 11 May 2010 13:27:15 +0000</pubDate>
		<dc:creator>Richard</dc:creator>
				<category><![CDATA[Web Design]]></category>
		<category><![CDATA[web hosting]]></category>

		<guid isPermaLink="false">http://accessibleweb.eu/?p=130</guid>
		<description><![CDATA[Hosting uptime 99.9% &#8211; sounds good? Certainly in theory a 99.9% uptime guarantee means you should expect no more than about 9 hours a year downtime (or about three quarters of an hour in a month). Unfortunately the picture is more complicated. Firstly it&#8217;s clear that no-one can offer a cast-iron guarantee that their service [...]]]></description>
			<content:encoded><![CDATA[<div class="tweetmeme_button" style="float: right; margin-left: 10px;">
			<a href="http://api.tweetmeme.com/share?url=http%3A%2F%2Faccessibleweb.eu%2F2010%2F05%2Fhosting-uptime-guarantees-are-they-worth-the-paper-they-arent-printed-on%2F"><br />
				<img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Faccessibleweb.eu%2F2010%2F05%2Fhosting-uptime-guarantees-are-they-worth-the-paper-they-arent-printed-on%2F&amp;style=normal&amp;b=2" height="61" width="50" /><br />
			</a>
		</div>
<p>Hosting uptime 99.9% &#8211; sounds good? Certainly in theory a 99.9% uptime guarantee means you should expect no more than about 9 hours a year downtime (or about three quarters of an hour in a month). Unfortunately the picture is more complicated. Firstly it&#8217;s clear that no-one can offer a cast-iron guarantee that their service will be available -  there will always be potential circumstances beyond their control. In reality the guarantee can at best mean financial compensation, and even then it is highly unlikely that compensation will be proportionate to the loss to your business.</p>
<p>When I asked a number of hosting providers about their guarantees they were very cagey, and usually referred to their 30 day money back guarantees or similar. Not a lot of use of course if you get a problem six months into a hosting contract. Even if they do offer compensation it is likely to be limited to a proportionate amount of the hosting cost, so if the service cost you £60 for a year the service could be down for a whole month and you may only be entitled to £5 back.  At best from a generous hosting company they may give you a full refund if they fail to meet their target (but does that mean they will carry on hosting the site for the remainder of the contract?). Of course this is at the basic end of the market where price competition is high. In the same way as Ryanair contests about compensation for air travellers when flights are cancelled, it may be unreasonable to expect large amounts of compensation for a service that only costs £5 a month.</p>
<p>Uptime means your website is available, yes? Well maybe it does and maybe it doesn&#8217;t. Some uptime guarantees are related to the hosting services network to the outside world rather than individual/shared web servers. Or the guarantee may be averaged across all their servers so if you happen to be hit hard you can only take comfort that others will have fared better.</p>
<p>As with most things in life you tend to get what you pay for, and higher rated uptime guarantees (e.g. 99.99%) are likely to cost you more for the hosting. Once hosting costs get into the hundreds of pounds a year range, it is worth tying down exactly what is meant by the guarantees and what happens if they are not met. A few questions to ask:</p>
<ol>
<li>Is there planned downtime for the servers (maintenance time), if so how much is this, when does it happen, and is that included in the uptime guarantee?</li>
<li>Does the hosting company automatically compensate you if they fail to meet the guarantee, or do you have to notice and report the problem (the latter seems to be more prevalent)?</li>
<li>If a guarantee is not met, what actions will be taken to reduce/minimise the chance of future occurrences. For example will planned maintence time be reduced (and what are the potential risks of that)?</li>
<li>Is there a cap on the amount of compensation that will be paid if a guarantee is not met?</li>
<li>If a full refund is the compensation, will the hosting contract be terminated?</li>
</ol>
<p>Perhaps the answer is some kind of insurance scheme that offers more flexibility in compensation. After all, a brochure website may be important to your business but is unlikely to lose as much money as a highly active e-commerce site, and yet the hosting costs/uptime guarantees could well be identical.</p>
<p>Share your views/experiences in the comments. I would love to hear of both negative and positive experiences with hosting companies, and also any suggestions you have for reducing the worry  of this aspect of running a business.</p>
]]></content:encoded>
			<wfw:commentRss>http://accessibleweb.eu/2010/05/hosting-uptime-guarantees-are-they-worth-the-paper-they-arent-printed-on/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Should Good Design be Unobtrusive?</title>
		<link>http://accessibleweb.eu/2009/12/should-good-design-be-unobtrusive/</link>
		<comments>http://accessibleweb.eu/2009/12/should-good-design-be-unobtrusive/#comments</comments>
		<pubDate>Wed, 02 Dec 2009 10:40:51 +0000</pubDate>
		<dc:creator>Richard</dc:creator>
				<category><![CDATA[Web Design]]></category>

		<guid isPermaLink="false">http://accessibleweb.eu/?p=87</guid>
		<description><![CDATA[The short answer is probably yes, good design should be unobtrusive. The longer answer is that it depends on a number of things. New ideas or significant variations on existing ideas tend to be fairly obtrusive as they are unfamiliar and make us stop and think. Examples My favourite example of this in the world [...]]]></description>
			<content:encoded><![CDATA[<div class="tweetmeme_button" style="float: right; margin-left: 10px;">
			<a href="http://api.tweetmeme.com/share?url=http%3A%2F%2Faccessibleweb.eu%2F2009%2F12%2Fshould-good-design-be-unobtrusive%2F"><br />
				<img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Faccessibleweb.eu%2F2009%2F12%2Fshould-good-design-be-unobtrusive%2F&amp;style=normal&amp;b=2" height="61" width="50" /><br />
			</a>
		</div>
<p>The short answer is probably yes, good design should be unobtrusive. The longer answer is that it depends on a number of things. New ideas or significant variations on existing ideas tend to be fairly obtrusive as they are unfamiliar and make us stop and think.</p>
<h3>Examples</h3>
<p>My favourite example of this in the world of web design is the tag cloud. The first time I saw a tag cloud it was a bit of an alien experience. I saw these different sized words and thought, well that&#8217;s interesting, is it art? Does it have a purpose? With a little bit of exploration I soon realised what it represented and how to use it, and it  became an obvious extension to more traditional forms of navigation including search. In some instances a tag cloud provides enough useful information just by itself, in terms of trending topics for example. It is very useful for a large site.</p>
<p>Breadcrumb navigation is another innovation that seems to have stuck. I heard about breadcrumb navigation before I saw it and I couldn&#8217;t quite get my head around it as described, but seeing it and using it makes it seem like common sense (although there are different ways of implementing breadcrumb navigation that can make a big difference to the user experience).</p>
<h3>Unobtrusive then?</h3>
<p>So when should design be unobtrusive? When it is an established  convention or &#8216;norm&#8217;. As mentioned in the previous post there are a number of examples of this  and if things don&#8217;t quite work the way we expect them to then it jars us and makes have to think about what we are doing. As an analogy consider driving, we mostly do it without having to think concsiously about everything, but an unfamilair road sign would make us have to quickly process the information around us and decide a) whether we need to take action as a result and b) what that action is.</p>
<p>It can be a bit of a dilemma; as designers we want to push the boundaries, and innovate, and yet with a usability or accessibility hat on, we also want to make the experience as intuitive and automatic as possible. After all, a website that looks and works in exactly the same way as most other websites isn&#8217;t going to win any design awards. On the other hand, a website with lots of innovations or a completely different navigation system may be the bees knees but will it give the return on investment it needs to?</p>
<h3>Please Comment</h3>
<p>What do you think? Share some of your examples of good innovative design by commenting here.</p>
]]></content:encoded>
			<wfw:commentRss>http://accessibleweb.eu/2009/12/should-good-design-be-unobtrusive/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Design by Community</title>
		<link>http://accessibleweb.eu/2009/11/design-by-community/</link>
		<comments>http://accessibleweb.eu/2009/11/design-by-community/#comments</comments>
		<pubDate>Fri, 20 Nov 2009 15:28:32 +0000</pubDate>
		<dc:creator>Richard</dc:creator>
				<category><![CDATA[Web Design]]></category>

		<guid isPermaLink="false">http://accessibleweb.eu/blog/?p=54</guid>
		<description><![CDATA[Design by Committee One of the often quoted rules of web design is that design by committee is a really bad idea. There are always a number of people involved in decisions around web design but problems arise when that number is more than a few. Projects stagnate through indecision, or web sites turn out [...]]]></description>
			<content:encoded><![CDATA[<div class="tweetmeme_button" style="float: right; margin-left: 10px;">
			<a href="http://api.tweetmeme.com/share?url=http%3A%2F%2Faccessibleweb.eu%2F2009%2F11%2Fdesign-by-community%2F"><br />
				<img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Faccessibleweb.eu%2F2009%2F11%2Fdesign-by-community%2F&amp;style=normal&amp;b=2" height="61" width="50" /><br />
			</a>
		</div>
<h3>Design by Committee</h3>
<p>One of the often quoted rules of web design is that design by committee is a really bad idea. There are always a number of people involved in decisions around web design but problems arise when that number is more than a few. Projects stagnate through indecision, or web sites turn out to be bland and uninteresting because of the need to please everyone. For example a large committee given a choice between white or black will often end up going for a compromise grey.</p>
<p>From a web designers perspective, the ideal situation is where they are given free reign to make all the decisions themselves, but meanwhile, back in the real world, the best that can be achieved is that there is one or two people apart from the designer who can make all the decisions.</p>
<p>With a larger group, decisions inevitably take longer (either the group has to meet all together which depends on shared available time, or members have to communicate in other ways e.g. email). Group members all have their own perspectives and agenda for what they want from a web design project. Often this manifests itself as a requirement for every department to have their fair share of the home page real estate and a jockeying for position within that page.<br />
<h3>From Committee to Community</h3>
<p>Design by community is a different approach, where the decisions are based on the needs and opinions of hundreds or thousands of individuals. Although that sounds like a recipe for disaster, in practice it means that the normal means of reaching decisions has to be replaced by other ways, for example polling or focus groups. The process has to be more democratic to work, although inevitably there will be some individuals or groups who dominate to some degree.</p>
<p>For many projects design by community isn&#8217;t a practical option but it&#8217;s certainly used for many web applications and systems e.g.</p>
<ul>
<li>content management systems</li>
<li>blogging platforms</li>
<li>social media applications</li>
</ul>
<p>What is also true is that aspects of design by community pop up in most web projects. Why do I say this? Because designers use established good practice all the time. There is innovation happening, but good design is generally based on existing principles that in some cases have been around for years. For example, it is very common for websites to display a logo in the top left corner of the page and for this to link back to the home page. There is no rule that says this is how things must happen, but it has developed over time and become an unwritten standard. It has developed by designers innovating and then the community feeding back. In this example the feedback has been generally positive which is why it has become the norm, however there is still debate over certain aspects e.g. whether on the home page the logo should <em>not</em> be a link as it would be self-referencing.</p>
<p>Some innovations disappear almost as quickly as they arrive, because they get the thumbs down from the community. They are either to difficult to use or implement, or inaccessible, or perhaps just ahead of their time.</p>
<p>Although the pace of change on the Web seems very fast, in many ways it is slowed down by this community action, which is probably a good thing. Development of the web needs both innovation and sanity checks. Corporate culture is generally quite conservative and a web design brief from a large organisation may have a long list of requirements which are effectively design decisions e.g. logo in the top left, search box top right, horizontal navigation bar. Things do change over time though and even the largest organisations are now happy to consider using things like breadcrumb navigation or tag clouds which were both radical innovations when they first appeared.</p>
<h3>In Conclusion</h3>
<p>So the message is, don&#8217;t ignore the community; use it to your advantage in establishing what are good practices for web design, in particular regarding usability and accessibility. And don&#8217;t be afraid to suggest this sort of approach for establishing requirements for large web projects, especially if the alternative is a twenty person committee who meet once a quarter to make the decisions.</p>
]]></content:encoded>
			<wfw:commentRss>http://accessibleweb.eu/2009/11/design-by-community/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

