<?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>Kilroy James &#187; Technical</title>
	<atom:link href="http://www.kilroyjames.co.uk/category/technical/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.kilroyjames.co.uk</link>
	<description>Makers of fine websites since 1994</description>
	<lastBuildDate>Wed, 21 Jul 2010 08:53:02 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>XTH &#8211; the XHTML to HTML converter for wordpress</title>
		<link>http://www.kilroyjames.co.uk/2009/09/xth/</link>
		<comments>http://www.kilroyjames.co.uk/2009/09/xth/#comments</comments>
		<pubDate>Wed, 09 Sep 2009 13:04:36 +0000</pubDate>
		<dc:creator>John Kilroy</dc:creator>
				<category><![CDATA[Technical]]></category>
		<category><![CDATA[Web Standards]]></category>
		<category><![CDATA[Wordpress]]></category>

		<guid isPermaLink="false">http://www.kilroyjames.co.uk/?p=270</guid>
		<description><![CDATA[
Download XTH (v2.01) here

By popular demand here it is &#8211; version 2.01 of the original XHTML-to-HTML wordpress plugin. Now called XTH (bit catchier, no?), it is a complete rewrite of the original version and aims to fix the Javascript CDATA and RSS feed issues that the original suffered.
Caveats
OK, this version seems to successfully avoid parsing [...]]]></description>
			<content:encoded><![CDATA[<div class="download">
<h3><a href="http://www.kilroyjames.co.uk/wp-content/uploads/xth.zip">Download XTH (v2.01) here</a></h3>
</div>
<p>By popular demand here it is &#8211; version 2.01 of the <a href="http://www.kilroyjames.co.uk/2008/07/xhtml-to-html-wordpress-plugin/">original XHTML-to-HTML wordpress plugin</a>. Now called XTH (bit catchier, no?), it is a complete rewrite of the original version and aims to fix the Javascript CDATA and RSS feed issues that the original suffered.</p>
<h4>Caveats</h4>
<p>OK, this version seems to successfully avoid parsing inline Javascripts and external Javascript libraries. This is necessary because the XHTML closing sequence is a valid pattern in javascript regex, and removing it from those places would mess up those libraries.<br />
The downside to that is that it&#8217;s then up to you to make sure that any JS you use doesn&#8217;t output any XHTML, as XTH no longer &#8216;fixes&#8217; it for you.<br />
Same goes for any other external libs that you or your plugins load.
</p>
<p>
Note that XTH doesn&#8217;t address javascript URLs of the form &lt;a href=&#8221;javascript:foo()&#8221;&gt;. This is for efficiency &#8211; and also because I haven&#8217;t ever seen a regex used in that context, but who knows, someone might try it. I might add this as an option in a future
</p>
<h4>Don&#8217;t forget!</h4>
<p>A single XHTML closer anywhere in the output will fail HTML 4.01 validation Resulting in tag soup and defeating the object of the whole exercise. </p>
<p>XTH also avoids RSS feeds.</p>
<p>Problems, bugs and comments below please. This is a complete rewrite of the plugin so we&#8217;re back to square one with the list of problems and required tweaks.</p>
<p>Thanks to all those people who gave feedback and whose time and knowledge helped to make this new version possible.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.kilroyjames.co.uk/2009/09/xth/feed/</wfw:commentRss>
		<slash:comments>9</slash:comments>
		</item>
		<item>
		<title>Actinic ecommerce primer</title>
		<link>http://www.kilroyjames.co.uk/2008/05/actinic-ecommerce-primer/</link>
		<comments>http://www.kilroyjames.co.uk/2008/05/actinic-ecommerce-primer/#comments</comments>
		<pubDate>Thu, 15 May 2008 20:05:29 +0000</pubDate>
		<dc:creator>John Kilroy</dc:creator>
				<category><![CDATA[Ecommerce]]></category>
		<category><![CDATA[Technical]]></category>
		<category><![CDATA[Web Design]]></category>
		<category><![CDATA[actinic ecommerce]]></category>
		<category><![CDATA[ECM]]></category>
		<category><![CDATA[ecommerce provider]]></category>
		<category><![CDATA[ecommerce system]]></category>
		<category><![CDATA[ecommerce website]]></category>
		<category><![CDATA[secure order system]]></category>

		<guid isPermaLink="false">http://www.kilroyjames.co.uk/?p=57</guid>
		<description><![CDATA[Welcome to my attempt at a brief introduction to the Actinic ecommerce websites that we are currently recommending to small and medium-sized businesses.
Some of these points are covered in other articles, but I thought it would be good to collect them here for your convenience, and so I have a single article to point to [...]]]></description>
			<content:encoded><![CDATA[<p>Welcome to my attempt at a brief introduction to the Actinic ecommerce websites that we are currently recommending to small and medium-sized businesses.</p>
<p>Some of these points are covered in other articles, but I thought it would be good to collect them here for your convenience, and so I have a single article to point to when people ask me about Actinic (which is often enough now for me to take the time to write this article).</p>
<p>First off, this article isn&#8217;t a how-to or a manual, it is an overview of the main features offered by the Actinic ecommerce system, and some comparisons between it and other systems of the &#8220;home-made&#8221; variety.</p>
<p>Secondly, some nomenclature: I&#8217;ll refer to Actinic as, well, Actinic. However, when doing so I actually mean Actinic Business Client (there are a couple of other lesser versions you can consider if your needs are very simple). And I&#8217;ll refer, for historical reasons, to other systems built to order by companies around the country as &#8220;Bespoke&#8221;. Bespoke is actually something of a misnomer (referring as it does to high-end tailored clothes), your local ecommerce provider might refer to their particular offering as custom, bespoke, in-house, built-to-order, purpose built, or any other form of words that means basically &#8211; &#8220;we made it specially for you&#8221;. For my purposes they are all Bespoke.</p>
<h5>Overview of Actinic&#8217;s main features</h5>
<ul class="highlighted-list">
<li>flexibility:<br/>Actinic steals the socks off the competition when it comes to general purpose retailing features. It can deal with (almost) any retailing model except those with very specific requirements (see below), you can bundle products or split them into smaller products (components), product management is graphical and comprehensive, there are advanced features for setting up complicated types of products.
<p>This makes it perfect for selling groceries, musical instruments, records, wine, books, hardware and electrical items. It is not as suitable for selling, for example, curtains which often require complicated relationships between a product&#8217;s components: ie. a length of curtain might be sold by the metre, to a particular template, and with optional gathering, types of heading and pelmets (which also have their own styles and options). That sort of retail model might be better suited to a bespoke system.</p>
</li>
<li>marketing and sales features:<br/> Actinic comes with a lengthy list of marketing and promotion features that includes sophisticated discounting, related products, also bought, top products and new products. Products can be priced according to volume, quantity or any other metric you need to use. Discounts can be applied to customers with a particular sort of account, for instance, you can give your trade customers a VAT-free experience, your regular customers a 10% discount, or any customer a discount based on their order total. The flexibility is really impressive and is able to cope with pretty much all the most common forms of price marketing.</li>
<li>secure order system:<br/> Actinic downloads orders straight to your desktop and it interfaces with numerous payment providers (for instance Paypal or Worldpay). In fact Actinic is a desktop application, which has many benefits for you as a shopkeeper. The secure order processing though is a vital facility which again comes with a variety of options according to the type of order processing you want to do. Want to download your orders and swipe the card details yourself? No problem. Want your customers&#8217; details to be processed in real-time by your bank? No problem. The options don&#8217;t end there either, however the subject starts to get a bit technical so I&#8217;ll move on to&#8230;</li>
<li>reliability and pedigree:<br/> This is an overlooked but fundamental &#8220;feature&#8221; that ecommerce system vendors ought to take more seriously than they sometimes do. Your ecommerce shop is, in many cases, your livelihood. You can&#8217;t afford for it to be crashing or getting mixed up between whose order is for which customer, or sending orders off to the wrong address. Do not underestimate the number and gravity of the sorts of problems that you can find with an ecommerce application.
<p>Your system needs to be rock solid, <em>thoroughly</em> tested, and all the main facilities need to work properly 100% of the time. Aside from the potential inconvenience and headaches system bugs can cause, they can thoroughly damage your business&#8217;s reputation too. Unlike your friendly neighbourhood  bespoke systems, Actinic has eight years of solid, continuous development to call on. It is robust, secure and as near as damn it bug-free (it&#8217;s certainly free of category 1 bugs). It is also designed, built and supported by a large company with experience in EPOS and traditional secure retailing. And there are regular updates and patches to keep your site secure from hackers.</p>
</li>
<li>time to market:<br/> Most people, once they&#8217;ve taken the decision to start doing business online, want to just get on with it. They do not want to wait for several months for a bespoke system to go through the design, implementation and testing phases (which they absolutely require). And why should you have to wait around for someone to re-invent the wheel, particularly when they have little chance of improving on it? In the 3-4 months you wait for your bespoke system to roll out, your competitors could have stolen a march on you. Using Actinic, you can get a basic ecommerce business up and running in days. For more complicated sites it might take a few weeks from start to finish.</li>
<li>maintenance and development<br/>No system lasts forever. Needs, priorities and tastes change over time and your shop needs to change accordingly. If your competitors start offering new features you need to keep up. You will, anyway, want to change things about your shop as time goes by: as you gain experience as an online retailer, as you think up new ways to do things, or as you notice ways your current site could be improved. The engine that runs your ecommerce business needs to be able to cope with this natural evolution as much as possible. Actinic is updated regularly with relevant new features and the features in the current versions are more than enough for most businesses. Even if you want to upgrade your whole application this is not going to break the bank. On the contrary, bespoke engines are very expensive to develop and upgrade. This is mainly because it&#8217;s time consuming  to do that (as the system needs to be redesigned, rebuilt and retested), and unfortunately, as the sole customer, you usually have to bear the brunt of those development costs. </li>
<li>other Actinic features:
<ul>
<li>Stock monitoring. <br/>Actinic can monitor your stock levels and withdraw products from sale if they&#8217;ve run out. It can also continue to display them but with an out-of-stock message.</li>
<li>Office integration. <br/>Actinic can import and export data to Sage Line 50 and Quickbooks.</li>
<li>Growth potential. <br/>It is capable of dealing with high volume sites and product catalogues containing up to 20,000 products. You can be sure, if your hosting is up to the task, that Actinic won&#8217;t crumple under the weight of your success. </li>
<li>Go worldwide. <br/>Actinic also has excellent delivery and tax options, which can be configured independently for different regions and zones (UK, Europe, US, Rest of the World, for example). You can choose how delivery is calculated using a variety of measures that obviously includes weight or quantity, but which can also determine how much to charge for larger orders or where the customer opts for a slower or faster delivery service.</li>
</ul>
</li>
</ul>
<h5>The million dollar question</h5>
<p>In most cases cost is a deciding factor. Actinic is in my (humbly expert) opinion, the best value ecommerce system on the market &#8211; by a mile. Even a shop built using the top of the range Actinic Business client can start from as little as a thousand pounds, with prices increasing according to how much design customisation you want. This is a fraction (literally) of what a bespoke system would cost you for comparable features and power, and it would arrive soon after order bug-free and ready to rock &#8211; quite unlike your bespoke option which teeters out to first testing after a long gestation like a new born deer with wobbly legs.</p>
<h5>Free and easy</h5>
<p>There is a class of ecommerce system that I haven&#8217;t mentioned. Because I don&#8217;t think you should consider them. I&#8217;m talking about the &#8216;free&#8217; systems that most hosting companies bundle next to &#8216;Javascript Hit Counter&#8217; and the other free software that comes with your hosting control panel. Now these systems take longer to customise than Actinic, offer a pittance of features, and generally can&#8217;t be customised beyond the product catalogue (so your customers check out in something rather less than style). On top of all this, by the time you&#8217;ve paid a developer to customise it for you, I guarantee it will have cost you more or as much as an equivalently styled Actinic Catalogue site. These free systems aren&#8217;t free, and are the equivalent of shabby market retailing. If you really can&#8217;t afford to set up shop properly I advise you to forget it and trade on Ebay or Amazon instead.</p>
<h5>Truly Bespoke</h5>
<p>Ok, Actinic is not the last word in ecommerce. I started this article saying that it has limitations, and it does.  I don&#8217;t recommend it, or any pre-built system, for big ecommerce enterprises. Big retailers who have a lot to gain and lose need a relationship with their ecommerce provider that must by need go beyond that which Actinic is capable of providing. Sometimes they need to be able to request innovative and forward-looking features that pave the way for off-the-shelf packages to follow. They might need several development scenarios to choose from, comprehensive documentation or security systems in place, any of which will require a bespoke solution.</p>
<p>However, here I&#8217;m talking about Bespoke with a capital &#8216;B&#8217;, where the word fits it&#8217;s original meaning of a high-quality product designed specifically for a wealthy client. This option is, without argument, the ultimate ecommerce option, but it&#8217;s available only to a very few &#8211; because it costs a fortune to create and develop. There are many reasons to go bespoke &#8211; but these days they apply to a small percentage of ecommerce retailers &#8211; those who can afford the time and who have the resources,  and (usually to their chagrin) those whose business models don&#8217;t allow them to use off-the-shelf solutions. Going for a bespoke solution without a real need or more importantly the time and money to do it properly is a brave decision.</p>
<h5>Conclusion</h5>
<p>You know what I&#8217;m going to say. It&#8217;s a no brainer! at least for almost all small or medium-sized businesses. You will pay ten or fifteen times the price for a bespoke system that is as powerful, making them easily the best ecommerce websites available. Which, obviously, they would have to be for Kilroy James to recommend them. </p>
<dl class="footnotes">
<dt>Waiver:</dt>
<dd>Neither John Kilroy or anyone at Kilroy James has been bribed by Actinic in the making of this article <img src='http://www.kilroyjames.co.uk/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' /> </dd>
</dl>
]]></content:encoded>
			<wfw:commentRss>http://www.kilroyjames.co.uk/2008/05/actinic-ecommerce-primer/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Recommending HTML rather than XHTML</title>
		<link>http://www.kilroyjames.co.uk/2008/04/recommending-html-rather-than-xhtml/</link>
		<comments>http://www.kilroyjames.co.uk/2008/04/recommending-html-rather-than-xhtml/#comments</comments>
		<pubDate>Fri, 18 Apr 2008 18:53:28 +0000</pubDate>
		<dc:creator>John Kilroy</dc:creator>
				<category><![CDATA[Technical]]></category>
		<category><![CDATA[doctype]]></category>
		<category><![CDATA[html]]></category>
		<category><![CDATA[xhtml]]></category>
		<category><![CDATA[xml]]></category>

		<guid isPermaLink="false">http://www.kilroyjames.co.uk/?p=14</guid>
		<description><![CDATA[I know the current fad is to serve web pages using XHTML doctype, but this is, in almost all situations, wrong. OK, count to ten, and read on.
Unless you are going to serve your pages with a mime-type of application/xml (which virtually nobody does), and therefore make your pages innaccessible to the 65% of your [...]]]></description>
			<content:encoded><![CDATA[<p>I know the current fad is to serve web pages using XHTML doctype, but this is, in almost all situations, wrong. OK, count to ten, and read on.</p>
<p>Unless you are going to serve your pages with a mime-type of application/xml (which virtually nobody does), and therefore make your pages innaccessible to the 65% of your viewers who use Microsoft browsers &#8211; you should <strong>NOT</strong> use the XHTML doctype.<span id="more-14"></span></p>
<p>I do sympathise with the Wordpress developers, who&#8217;ve clearly gone to a lot of effort to provide output that validates using the W3C HTML validator. However, whilst admirable it is, nevertheless, a mistake, and if Wordpress is really interested in standards and valid markup they should head back to HTML &#8211; awaiting the release of HTML 5 (the likely successor to HTML 4.01).</p>
<p>This is a rather technical issue and to explain it fully needs more detail than I can afford here. However, there are some clear explanations of the major issues here:<br />
<a href="http://webkit.org/blog/68/understanding-html-xml-and-xhtml">http://webkit.org/blog/68/understanding-html-xml-and-xhtml</a></p>
<p>and a more technical discussion here:<br />
<a href="http://www.hixie.ch/advocacy/xhtml">http://www.hixie.ch/advocacy/xhtml</a></p>
<p>Please either revert back to HTML as the default, provide the option to select it in the Dashboard, or write a plugin that will translate back to HTML (thereby allowing Wordpress to serve valid markup).</p>
]]></content:encoded>
			<wfw:commentRss>http://www.kilroyjames.co.uk/2008/04/recommending-html-rather-than-xhtml/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>FTSE 100 web site survey, 2006</title>
		<link>http://www.kilroyjames.co.uk/2006/06/ftse-100-web-site-survey-2006/</link>
		<comments>http://www.kilroyjames.co.uk/2006/06/ftse-100-web-site-survey-2006/#comments</comments>
		<pubDate>Wed, 14 Jun 2006 09:15:27 +0000</pubDate>
		<dc:creator>John Kilroy</dc:creator>
				<category><![CDATA[Technical]]></category>
		<category><![CDATA[Web Design]]></category>
		<category><![CDATA[Web Standards]]></category>
		<category><![CDATA[accessibility]]></category>
		<category><![CDATA[FTSE 100]]></category>
		<category><![CDATA[usability]]></category>
		<category><![CDATA[web standards]]></category>

		<guid isPermaLink="false">http://www.kilroyjames.co.uk/?p=45</guid>
		<description><![CDATA[This survey assesses the technical quality, usability and accessibility of the homepage on the main web site of each member of the FTSE 100 group of companies.]]></description>
			<content:encoded><![CDATA[<p class="intro">This survey assesses the technical quality, usability and accessibility of the homepage on the main web site of each member of the FTSE 100 group of companies.</p>
<p>Kilroy James first surveyed this group, and a much larger group of smaller companies, in 2004 in order to get a picture of the general web design standards promoted and achieved by British companies. Now in its third year the survey has developed greatly, applying up to twenty tests during each homepage examination.</p>
<p>The FTSE 100 survey looks at WCAG Accessibility ratings, W3C technical testing, and the use (and omittance) of numerous usability features. It measures basic good design and technical practice. We view it and encourage others to view it as a benchmark of basic quality, indicating entry-level standards we think all web sites should meet.</p>
<h5>Main findings</h5>
<ul>
<li>75% of homepages fail basic technical testing and 86% contain programming faults.</li>
<li>93% do not meet recommended accessibility standards (WCAG priority II). 56% do not meet the industry minimum standard.</li>
<li>Less than a third (30%) provide properly resizeable text.</li>
<li>87% have a search facility on their web site, but only 71% present it on the homepage.</li>
<li>The average score is 38%.</li>
</ul>
<div class="survey-results">
<div id="d1">
<p> <strong>Top of the survey results.</strong><br/><br />
        Companies scoring 60% or higher</p>
<table summary="Companies scoring 60% or higher.">
<thead>
<tr>
<th id="c1">Rank</th>
<th id="c2">Company</th>
<th id="c3">Score</th>
</tr>
</thead>
<tbody>
<tr>
<td headers="c1">1</td>
<td headers="c2">J  Sainsbury</td>
<td headers="c3">83%</td>
</tr>
<tr>
<td headers="c1">2</td>
<td headers="c2">Xstrata</td>
<td headers="c3">78%</td>
</tr>
<tr>
<td headers="c1">3</td>
<td headers="c2">National  Grid</td>
<td headers="c3">73%</td>
</tr>
<tr>
<td headers="c1">4</td>
<td headers="c2">Boots PLC</td>
<td headers="c3">71%</td>
</tr>
<tr>
<td headers="c1">5</td>
<td headers="c2">British Land</td>
<td headers="c3">71%</td>
</tr>
<tr>
<td headers="c1">6</td>
<td headers="c2">Rentokil Initial</td>
<td headers="c3">70%</td>
</tr>
<tr>
<td headers="c1">7</td>
<td headers="c2">Imperial Tobacco</td>
<td headers="c3">68%</td>
</tr>
<tr>
<td headers="c1">8</td>
<td headers="c2">Royal  &#038; SunAlliance</td>
<td headers="c3">65%</td>
</tr>
<tr>
<td headers="c1">9</td>
<td headers="c2">Alliance Boots</td>
<td headers="c3">64%</td>
</tr>
</tbody>
</table></div>
<div id="d2">
<p> <strong>Bottom of the survey results.</strong><br/><br />
        Companies scoring 20% or lower</p>
<table summary="Companies scoring 20% or lower.">
<thead>
<tr>
<th id="c4">Rank</th>
<th id="c5">Company</th>
<th id="c6">Score</th>
</tr>
</thead>
<tbody>
<tr>
<td headers="c4">87</td>
<td headers="c5">Carnival</td>
<td headers="c6">18%</td>
</tr>
<tr>
<td headers="c4">88</td>
<td headers="c5">Rolls Royce</td>
<td headers="c6">17%</td>
</tr>
<tr>
<td headers="c4">89</td>
<td headers="c5">Legal &#038; General</td>
<td headers="c6">16%</td>
</tr>
<tr>
<td headers="c4">90</td>
<td headers="c5">Barclays</td>
<td headers="c6">16%</td>
</tr>
<tr>
<td headers="c4">91</td>
<td headers="c5">Next</td>
<td headers="c6">16%</td>
</tr>
<tr>
<td headers="c4">92</td>
<td headers="c5">Vedanta</td>
<td headers="c6">16%</td>
</tr>
<tr>
<td headers="c4">93</td>
<td headers="c5">Kazakhmys</td>
<td headers="c6">16%</td>
</tr>
<tr>
<td headers="c4">94</td>
<td headers="c5">International Power</td>
<td headers="c6">12%</td>
</tr>
<tr>
<td headers="c4">95</td>
<td headers="c5">Cairn Energy</td>
<td headers="c6">12%</td>
</tr>
<tr>
<td headers="c4">96</td>
<td headers="c5">Antofagasta</td>
<td headers="c6">12%</td>
</tr>
<tr>
<td headers="c4">97</td>
<td headers="c5">DSG International</td>
<td headers="c6">10%</td>
</tr>
<tr>
<td headers="c4">98</td>
<td headers="c5">Persimmon</td>
<td headers="c6">9%</td>
</tr>
<tr>
<td headers="c4">99</td>
<td headers="c5">Prudential</td>
<td headers="c6">4%</td>
</tr>
<tr>
<td headers="c4">100</td>
<td headers="c5">Enterprise Inns</td>
<td headers="c6">0%</td>
</tr>
</tbody>
</table></div>
</p></div>
<h5>Interpretation of results</h5>
<p>The best homepages meet basic standards and get the important things right. However, 86% do not meet basic standards, which is a poor figure lending a certain distinction to the 14% who do. Beyond standards conformance, the best sites achieve good accessibility ratings and show that the designer has considered Information Architecture and Usability issues.</p>
<p>The survey&#8217;s overall finding though is that the majority of tested homepages are poor (some are very poor indeed) and only a few would meet the standards required of a public sector web site, which isn&#8217;t very encouraging considering these are the UK&#8217;s largest companies.</p>
<h5>Methodology</h5>
<p>The survey tests the homepage of the main corporate web site for each member of the FTSE 100 and is in two parts: Basic and Extended. The Basic test looks at eleven aspects of a page&#8217;s design and implementation including: whether text resizing is properly implemented; W3C markup and CSS validation; and the presence, form and positioning of any search function. The Extended test looks at nine other elements including WCAG ratings.</p>
<p>We do not publish the exact survey methodology but it does account for qualities such as scrolling, title length and text resizeability, and the use of popup windows, splash pages and search functions.</p>
<p>The scoring method reflects the fact that the tests cover a range of faults with varying degrees of scope and seriousness. For example text resizeability is considered to be more important than whether a homepage scrolls or not: because scrolling is only bad if it makes the scrollbar difficult to use (and homepages are rarely that long, plus there are other ways to scroll a page) whereas a web page with unredeemably small text can, to people with less than perfect eyesight, be rendered unusable.</p>
<p>The 2006 survey was conducted during July and August; web pages may have changed since they were surveyed. </p>
]]></content:encoded>
			<wfw:commentRss>http://www.kilroyjames.co.uk/2006/06/ftse-100-web-site-survey-2006/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>
