MOD sticks with insecure browser: According to parliamentary written answers received by Labour MP Tom Watson, the majority of departments still require staff to use IE6. Most have plans to upgrade to the more secure IE7, and some to IE8, but the Ministry of Defence (MoD) has no plans to change.But where is the voice of Local Government? Â Who is lobbying for change in local councils? Itâ€™s all very quiet over at the LGA, â€œthe voice of the local government sectorâ€ to quote from their website. Â Maybe they donâ€™t see this as cost-saving measure, which is perhaps understandable if you take the short term (some may argue â€˜myopicâ€™) view. Â Iâ€™m assuming here that reluctance to upgrade from IE6 is likely to be because of cost; most internal websites (e.g. intranets) within Gov/Local Gov will have been tailored to work with the IE6 browser, and since IE6 did not follow W3C standards (Microsoft deciding at the time that they were above following any standard other than their own), any other browser type (Firefox, Opera, Safari etc.) would not render the content correctly. They (Microsoft) have since seen the error of their ways and have fallen into line with globally agreed standards when they released IE7 and IE8. The problem will be making changes to all of the legacy websites to work correctly with a new browser version. From this perspective yes, there is a cost, but what appears to have been forgotten is that any new web services or enhancements to existing websites have to be made backwards compatible to IE6. I can speak with a bit of authority here because Iâ€™ve been involved with the development of the IDEA Communities of Practice platform over the past 5 years. I know for a fact that for every change and enhancement to the website, around 15-20% of the cost goes into making it work with IE6. I estimate this to have cost almost Â£100k over the 5 years. If we took these same figures, i.e. 15-20% of website development costs going into ensuring compatibility with IE6, multiplied by the 400 or so local authority websites (and not even counting the fire services, the police and other agency websites) we end up with a pretty significant cost. Â Iâ€™m not quite sure how this squares with the LGAâ€™s priority for 2009/100 of â€œEfficiency and value for moneyâ€. But don’t take my word for it. Perhaps this article from Craig Grannell sums the issue up more succinctly than I can, abstract below:
Craig Grannell asks designers and developers if it’s finally time to take IE6 behind the shed and shoot it. Many argue that IE6 hinders development, due to the number of hacks required to get sites working in it. Opera web evangelist Bruce Lawson goes further, squarely blaming IE6 for â€œhindering the development of the webâ€, due to its lack of support for advanced CSS and XHTML. Many in the industry tell such tales: horror stories of a third of a siteâ€™s development time taken up by dealing with IE6; major display issues requiring a partial site rebuild, despite everything looking fine in all other browsers; elements randomly disappearing entirely due to the â€˜hasLayoutâ€™ bug. â€œIf anything, things will get worse, since weâ€™re now battling three versions: 6, 7 and 8,â€ says Tom Muller of Kleber. â€œThey all display content slightly differently and we regularly work up a site in Firefox or Safari, only to spend a day figuring out why our valid, semantic code doesnâ€™t render correctly in Internet Explorer.â€But aside from cost, there is the other issue I alluded to at the start of this article, i.e. productivity of staff. Â Weâ€™re increasingly recognising the power of social media tools and the social web to connect people with similar interests; to improve collaboration and knowledge sharing; to get a better understanding of what people think about gov/local gov services and how they can be improved.Â We need to give staff working in the public sector access to the same tools and facilities that ordinary citizens are using to connect, share and collaborate.Â Doing nothing is not an option, and is likely to make the gap between technologies that are available a private user and what is available to a public sector worker even greater. Â Fore example:
YouTube to stop IE6 support: YouTube will no longer support Internet Explorer 6, TechRadar can confirm, with Google beginning to roll out warnings to those accessing the video site that they should update to a better browser. Google Docs, Google sites dropping support for IE6And I’m sure we’re going to be seeing a lot of similar announcements in the coming year. So, what do we do about it (if we’re passionate enough about the topic)?
- I’d like to see a similar survey to that instigated by Tom Watson for central government, but this time getting information on council plans for upgrading from IE6. However, I assume this may have to be through the Freedom of Information route, since I’m not aware if or how a parliamentary question would solicit this information – unless CLG were obliged to supply it on behalf of all local councils in England and Wales.
- In anticipation of cost being the main barrier for most councils, I’d like to see a policy agreed whereby staff could use an alternative browser for accessing social media websites and as a general productivity tool, whilst still using IE6 for accessing internally-dependent websites, thus circumnavigating the issues of cost. If necessary, and to accommodate the natural desire of IT departments to lock down all installed software, staff or their department could make the business case for having Firefox installed and then IT enable this as a Group Policy.
- I’dÂ be interested to know where SOCITM stood on this issue, and whether they felt passionate enough about it to be a catalyst for change. After all, they are representing the IT managers. I have in fact written to them recently to solicit their views on all of this.