<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: Microsoft wants you to stop using IE6.</title>
	<atom:link href="http://blog.komosion.com/boffinry/microsoft-wants-you-to-stop-using-ie6/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.komosion.com/boffinry/microsoft-wants-you-to-stop-using-ie6/</link>
	<description></description>
	<lastBuildDate>Wed, 13 Oct 2010 21:10:59 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1</generator>
	<item>
		<title>By: admin</title>
		<link>http://blog.komosion.com/boffinry/microsoft-wants-you-to-stop-using-ie6/comment-page-1/#comment-443</link>
		<dc:creator>admin</dc:creator>
		<pubDate>Mon, 17 May 2010 04:21:07 +0000</pubDate>
		<guid isPermaLink="false">http://blog.komosion.com/?p=165#comment-443</guid>
		<description>Fair enough points Ryan.

All Komosion&#039;s websites are still coded to present perfectly to IE6. Our stats tell us that it is more like 10% of people using it, but that is still a statistically significant amount. And as we work with councils, government departments and the like, accessibility is a major factor that we do work hard to maintain.

When using Komodo CMS, however, we have now had to let people know that things like our In-Line editing will not function for that dinosaur of a browser, because the AJAX involved just can&#039;t be handled by IE6. Or software is going to continue to develop and advance, and we cannot let the limitations of the oldest browser on the market limit the kind of features that we offer to our clients. Just like Google (as we mentioned a few blog posts down) we are going to get better, while that browser version will not.

So in answer to your concerns: Komosion website will still be as accessible to all audiences (and we make sure it is absolutely right for the target audience) no matter how much we improve the CMS behind it.</description>
		<content:encoded><![CDATA[<p>Fair enough points Ryan.</p>
<p>All Komosion&#8217;s websites are still coded to present perfectly to IE6. Our stats tell us that it is more like 10% of people using it, but that is still a statistically significant amount. And as we work with councils, government departments and the like, accessibility is a major factor that we do work hard to maintain.</p>
<p>When using Komodo CMS, however, we have now had to let people know that things like our In-Line editing will not function for that dinosaur of a browser, because the AJAX involved just can&#8217;t be handled by IE6. Or software is going to continue to develop and advance, and we cannot let the limitations of the oldest browser on the market limit the kind of features that we offer to our clients. Just like Google (as we mentioned a few blog posts down) we are going to get better, while that browser version will not.</p>
<p>So in answer to your concerns: Komosion website will still be as accessible to all audiences (and we make sure it is absolutely right for the target audience) no matter how much we improve the CMS behind it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ryan</title>
		<link>http://blog.komosion.com/boffinry/microsoft-wants-you-to-stop-using-ie6/comment-page-1/#comment-442</link>
		<dc:creator>Ryan</dc:creator>
		<pubDate>Mon, 17 May 2010 03:46:27 +0000</pubDate>
		<guid isPermaLink="false">http://blog.komosion.com/?p=165#comment-442</guid>
		<description>Hi,

Valid point on IE6, but if visitors using this browser still account for a fifth of traffic is it not realistic to accommodate this? Your thoughts?

Additionally, if your usability/persona mapping picks up an &#039;older&#039; demographic where an assumption can be made on IE6 utlisation - how would you prepare or mitgate this both from a front end and CMS perspective?</description>
		<content:encoded><![CDATA[<p>Hi,</p>
<p>Valid point on IE6, but if visitors using this browser still account for a fifth of traffic is it not realistic to accommodate this? Your thoughts?</p>
<p>Additionally, if your usability/persona mapping picks up an &#8216;older&#8217; demographic where an assumption can be made on IE6 utlisation &#8211; how would you prepare or mitgate this both from a front end and CMS perspective?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

