<?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: Déjà Vu All Over Again?</title>
	<atom:link href="http://www.headstar.com/eablive/?feed=rss2&#038;p=253" rel="self" type="application/rss+xml" />
	<link>http://www.headstar.com/eablive/?p=253</link>
	<description>Access to technology for all</description>
	<lastBuildDate>Sun, 01 Apr 2018 16:32:15 +0000</lastBuildDate>
		<sy:updatePeriod>hourly</sy:updatePeriod>
		<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=4.0.1</generator>
	<item>
		<title>By: paul canning</title>
		<link>http://www.headstar.com/eablive/?p=253&#038;cpage=1#comment-5402</link>
		<dc:creator><![CDATA[paul canning]]></dc:creator>
		<pubDate>Wed, 25 Mar 2009 12:24:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.headstar.com/eablive/?p=253#comment-5402</guid>
		<description><![CDATA[Have blogged a response to this article here
tinyurl.com/deb6es]]></description>
		<content:encoded><![CDATA[<p>Have blogged a response to this article here<br />
tinyurl.com/deb6es</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andrew Hart</title>
		<link>http://www.headstar.com/eablive/?p=253&#038;cpage=1#comment-5401</link>
		<dc:creator><![CDATA[Andrew Hart]]></dc:creator>
		<pubDate>Tue, 24 Mar 2009 13:58:01 +0000</pubDate>
		<guid isPermaLink="false">http://www.headstar.com/eablive/?p=253#comment-5401</guid>
		<description><![CDATA[I&#039;ve been working with Government clients for years now and the biggest hindrance to implementing accessibility is the laughably weak &#039;pressure&#039; from central Government.

Everyone know that &quot;Existing central government department websites must conform to &#039;AA&#039; by December 2009 and all other government agencies and non- departmental bodies by March 2011&quot; [http://www.headstar.com/eablive/?p=191] ...but how many times has this deadline changed?  I&#039;ve lost count!

Back in May 2002 the Office of the e-Envoy (long since disbanded as a bad joke) issued the &quot;Guidelines for UK Government Websites&quot; along with a mandate of &quot;conform or lose the funding for your website which will be managed centrally by the e-Envoy dept.&quot;  This concerned many of my clients and action was urgent.

The Government had no backbone and was soon extending deadlines and watering down penalties for non-conforming websites...and NOTHING has changed since!

The Disability Discrimination Act is law and it&#039;s about time the Government started enforcing it.  Sadly this is not going to happen any time soon.

There are some ways to speed up the process:

1) pressure Government through lobbying and legal action
2) if you own or run a website embrace accessibility and reap the rewards (better SEO, greater market reach, public response to ethical trading)
3) if you design websites build accessibility in as STANDARD...not an optional extra

Annual reviews of Government failures are important but are only one part of the picture.  Real change comes from getting involved!]]></description>
		<content:encoded><![CDATA[<p>I&#8217;ve been working with Government clients for years now and the biggest hindrance to implementing accessibility is the laughably weak &#8216;pressure&#8217; from central Government.</p>
<p>Everyone know that &#8220;Existing central government department websites must conform to &#8216;AA&#8217; by December 2009 and all other government agencies and non- departmental bodies by March 2011&#8243; [http://www.headstar.com/eablive/?p=191] &#8230;but how many times has this deadline changed?  I&#8217;ve lost count!</p>
<p>Back in May 2002 the Office of the e-Envoy (long since disbanded as a bad joke) issued the &#8220;Guidelines for UK Government Websites&#8221; along with a mandate of &#8220;conform or lose the funding for your website which will be managed centrally by the e-Envoy dept.&#8221;  This concerned many of my clients and action was urgent.</p>
<p>The Government had no backbone and was soon extending deadlines and watering down penalties for non-conforming websites&#8230;and NOTHING has changed since!</p>
<p>The Disability Discrimination Act is law and it&#8217;s about time the Government started enforcing it.  Sadly this is not going to happen any time soon.</p>
<p>There are some ways to speed up the process:</p>
<p>1) pressure Government through lobbying and legal action<br />
2) if you own or run a website embrace accessibility and reap the rewards (better SEO, greater market reach, public response to ethical trading)<br />
3) if you design websites build accessibility in as STANDARD&#8230;not an optional extra</p>
<p>Annual reviews of Government failures are important but are only one part of the picture.  Real change comes from getting involved!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: James Coltham</title>
		<link>http://www.headstar.com/eablive/?p=253&#038;cpage=1#comment-5399</link>
		<dc:creator><![CDATA[James Coltham]]></dc:creator>
		<pubDate>Thu, 19 Mar 2009 15:45:17 +0000</pubDate>
		<guid isPermaLink="false">http://www.headstar.com/eablive/?p=253#comment-5399</guid>
		<description><![CDATA[We all know that WCAG 1.0 is outdated, especially now that it has been superseded by version 2, so the 8% stat is fairly meaningless (many of the conditions for failure are arbitrary and no longer relevant, as Bim herself alludes to). The RNIB&#039;s own rating system seems far more pertinent - based on real-life accessibility - so let&#039;s have more discussion around that and less of the talk about déjà vu!

I look forward to seeing what results come next year, when measured against WCAG 2.0, but it&#039;s interesting to note that the COI&#039;s Delivering Inclusive Websites guidance does not yet refer to these.]]></description>
		<content:encoded><![CDATA[<p>We all know that WCAG 1.0 is outdated, especially now that it has been superseded by version 2, so the 8% stat is fairly meaningless (many of the conditions for failure are arbitrary and no longer relevant, as Bim herself alludes to). The RNIB&#8217;s own rating system seems far more pertinent &#8211; based on real-life accessibility &#8211; so let&#8217;s have more discussion around that and less of the talk about déjà vu!</p>
<p>I look forward to seeing what results come next year, when measured against WCAG 2.0, but it&#8217;s interesting to note that the COI&#8217;s Delivering Inclusive Websites guidance does not yet refer to these.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Stuart Harrison</title>
		<link>http://www.headstar.com/eablive/?p=253&#038;cpage=1#comment-5398</link>
		<dc:creator><![CDATA[Stuart Harrison]]></dc:creator>
		<pubDate>Thu, 19 Mar 2009 15:05:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.headstar.com/eablive/?p=253#comment-5398</guid>
		<description><![CDATA[(I&#039;ll try and post my comments in the right article this time!)

Accessibility has to be seen as more than just a binary pass / fail scenario. Just because a few pages fail on a few minor points doesn’t mean the whole site is inaccessible. Sure, point out the problems so they can be fixed, but don’t brand websites with the label ‘inaccessible’ just because of a few issues.

And don’t get me started on suppliers. The main problem is that web teams aren’t consulted before deals are entered into and contracts are signed. As a local authority web person, I’ve found myself on more than one occasion being forced to implement systems that I know are inaccessible, but I’ve got no way of blocking their release.]]></description>
		<content:encoded><![CDATA[<p>(I&#8217;ll try and post my comments in the right article this time!)</p>
<p>Accessibility has to be seen as more than just a binary pass / fail scenario. Just because a few pages fail on a few minor points doesn’t mean the whole site is inaccessible. Sure, point out the problems so they can be fixed, but don’t brand websites with the label ‘inaccessible’ just because of a few issues.</p>
<p>And don’t get me started on suppliers. The main problem is that web teams aren’t consulted before deals are entered into and contracts are signed. As a local authority web person, I’ve found myself on more than one occasion being forced to implement systems that I know are inaccessible, but I’ve got no way of blocking their release.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
