<?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: Crying Foul on Accessibility Claims</title>
	<atom:link href="http://www.webstandards.org/2006/06/27/spurious-accessibility-claims-and-designs/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.webstandards.org/2006/06/27/spurious-accessibility-claims-and-designs/</link>
	<description>Working together for standards</description>
	<lastBuildDate>Wed, 27 Mar 2013 12:19:03 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Internet Buzz Words - JP2 Designs - Web and Print Development - Perth, Western Australia</title>
		<link>http://www.webstandards.org/2006/06/27/spurious-accessibility-claims-and-designs/comment-page-1/#comment-29606</link>
		<dc:creator>Internet Buzz Words - JP2 Designs - Web and Print Development - Perth, Western Australia</dc:creator>
		<pubDate>Thu, 04 Jan 2007 00:37:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.webstandards.org/2006/06/27/spurious-accessibility-claims-and-designs/#comment-29606</guid>
		<description>[...] AAA Web Accessibility Rating: Yes you can get different so called levels of accessibility for a website. The way I see it is that the website either meets the standard or it does not. Hear is two links for information on Web Accessibility Rating (One by Steel Technology and one written by webstandards.org). [...]</description>
		<content:encoded><![CDATA[<p>[...] AAA Web Accessibility Rating: Yes you can get different so called levels of accessibility for a website. The way I see it is that the website either meets the standard or it does not. Hear is two links for information on Web Accessibility Rating (One by Steel Technology and one written by webstandards.org). [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: &#187; Internet Buzz Words &#187; GermWorks - Web &#38; Multimedia</title>
		<link>http://www.webstandards.org/2006/06/27/spurious-accessibility-claims-and-designs/comment-page-1/#comment-28619</link>
		<dc:creator>&#187; Internet Buzz Words &#187; GermWorks - Web &#38; Multimedia</dc:creator>
		<pubDate>Tue, 02 Jan 2007 02:19:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.webstandards.org/2006/06/27/spurious-accessibility-claims-and-designs/#comment-28619</guid>
		<description>[...] AAA Web Accessibility Rating: Yes you can get different so called levels of accessibility for a website. The way I see it is that the website either meets the standard or it does not. Hear is two links for information on Web Accessibility Rating (One by Steel Technology and one written by webstandards.org). [...]</description>
		<content:encoded><![CDATA[<p>[...] AAA Web Accessibility Rating: Yes you can get different so called levels of accessibility for a website. The way I see it is that the website either meets the standard or it does not. Hear is two links for information on Web Accessibility Rating (One by Steel Technology and one written by webstandards.org). [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kary Lawson&#8217;s Blog &#187; Crying Foul on Accessibility Claims</title>
		<link>http://www.webstandards.org/2006/06/27/spurious-accessibility-claims-and-designs/comment-page-1/#comment-4396</link>
		<dc:creator>Kary Lawson&#8217;s Blog &#187; Crying Foul on Accessibility Claims</dc:creator>
		<pubDate>Mon, 04 Sep 2006 13:16:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.webstandards.org/2006/06/27/spurious-accessibility-claims-and-designs/#comment-4396</guid>
		<description>[...] By Ian Lloyd [...]</description>
		<content:encoded><![CDATA[<p>[...] By Ian Lloyd [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ashley Bowers Blog &#187; Crying Foul on Accessibility Claims</title>
		<link>http://www.webstandards.org/2006/06/27/spurious-accessibility-claims-and-designs/comment-page-1/#comment-2943</link>
		<dc:creator>Ashley Bowers Blog &#187; Crying Foul on Accessibility Claims</dc:creator>
		<pubDate>Fri, 04 Aug 2006 03:51:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.webstandards.org/2006/06/27/spurious-accessibility-claims-and-designs/#comment-2943</guid>
		<description>[...] Crying Foul on Accessibility Claims  Or how not to waste tax-payers’ money on inaccessible sites or make grand claims on accessibility that you cannot fully back up. [...]</description>
		<content:encoded><![CDATA[<p>[...] Crying Foul on Accessibility Claims  Or how not to waste tax-payers’ money on inaccessible sites or make grand claims on accessibility that you cannot fully back up. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ashley Bowers Blog</title>
		<link>http://www.webstandards.org/2006/06/27/spurious-accessibility-claims-and-designs/comment-page-1/#comment-2942</link>
		<dc:creator>Ashley Bowers Blog</dc:creator>
		<pubDate>Fri, 04 Aug 2006 03:50:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.webstandards.org/2006/06/27/spurious-accessibility-claims-and-designs/#comment-2942</guid>
		<description>&lt;strong&gt;Crying Foul on Accessibility Claims...&lt;/strong&gt;

	Crying Foul on Accessibility Claims 
Or how not to waste tax-payers’ money on inaccessible sites or make grand claims on accessibility that you cannot fully back up. 
	By Ian Lloyd
	This has an interesting list of ten things to do and a piece on tru...</description>
		<content:encoded><![CDATA[<p><strong>Crying Foul on Accessibility Claims&#8230;</strong></p>
<p>	Crying Foul on Accessibility Claims<br />
Or how not to waste tax-payers’ money on inaccessible sites or make grand claims on accessibility that you cannot fully back up.<br />
	By Ian Lloyd<br />
	This has an interesting list of ten things to do and a piece on tru&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tim</title>
		<link>http://www.webstandards.org/2006/06/27/spurious-accessibility-claims-and-designs/comment-page-1/#comment-2252</link>
		<dc:creator>Tim</dc:creator>
		<pubDate>Sun, 16 Jul 2006 06:27:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.webstandards.org/2006/06/27/spurious-accessibility-claims-and-designs/#comment-2252</guid>
		<description>You guys have problems, but Australia is in the dark ages, the peak body in Australia the Australian Government Information Office AGIMO made awards for excellence to these broken websites.

http://www.hereticpress.com/Dogstar/Publishing/AustWeb.html#roadready

My review of some UK governmenet sites:

http://www.hereticpress.com/Dogstar/Publishing/UKweb.html

Keep up the good work

Tim
http://www.hereticpress.com</description>
		<content:encoded><![CDATA[<p>You guys have problems, but Australia is in the dark ages, the peak body in Australia the Australian Government Information Office AGIMO made awards for excellence to these broken websites.</p>
<p><a href="http://www.hereticpress.com/Dogstar/Publishing/AustWeb.html#roadready" rel="nofollow">http://www.hereticpress.com/Dogstar/Publishing/AustWeb.html#roadready</a></p>
<p>My review of some UK governmenet sites:</p>
<p><a href="http://www.hereticpress.com/Dogstar/Publishing/UKweb.html" rel="nofollow">http://www.hereticpress.com/Dogstar/Publishing/UKweb.html</a></p>
<p>Keep up the good work</p>
<p>Tim<br />
<a href="http://www.hereticpress.com" rel="nofollow">http://www.hereticpress.com</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Paul Walsh</title>
		<link>http://www.webstandards.org/2006/06/27/spurious-accessibility-claims-and-designs/comment-page-1/#comment-1947</link>
		<dc:creator>Paul Walsh</dc:creator>
		<pubDate>Fri, 30 Jun 2006 17:10:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.webstandards.org/2006/06/27/spurious-accessibility-claims-and-designs/#comment-1947</guid>
		<description>In view of the comments and opinions expressed here, I would like to state for the record that Segala is not connected or involved with www.sonyericsson.com or any of its sub-sites, this includes the DaVinci Code section of this site.  Segala has not audited or certified this website for accessibility and has made no claims to that effect.

Segala was not responsible for the design or build of the www.davincicodetrail.co.uk website, nor indeed the decision to provide one version in Flash and an alternative HTML version.  The Segala certificate clearly states which URLs it has certified.  

The decision to create the http://www.davincicodetrail.co.uk/ website and the hosting of the Flash game on a separate URL was in no way influenced by and beyond any control of Segala.

Our press release states that we certified http://www.davincicodetrail.co.uk/.  We would like to point out that it does not allude to or suggest that we certified the flash game or any other elements on www.sonyericsson.com, however we do acknowledge that the wording may have caused some confusion as to whether or not we certified the flash game on which the O2 website is centered around.  For this we apologise and we thank you for pointing this out to us.  We sincerely did not intend for this Press release to be “misleading propaganda” and we have taken the decision to amend our press release to clarify the issues raised.

Unfortunately, the flash site/elements were already built before Segala was engaged to audit and certify the accessible alternative. I must point out that with the exception of the game (which is now clearly marked as inaccessible to some) the HTML alternative provides exactly the same information as the flash site. So, although I agree it is best practice to create one site that is accessible to all, in this instance the best alternative was to create an accessible HTML version of the site.

We could have been less enthusiastic in issuing the PR for this particular site, but we are keen to help move the industry forward from what it currently perceives as ‘accessibility extremism’ by demonstrating how some companies embrace accessibility for the long haul and are embedding it into their strategies, brand marketing and development guidelines. However, even those companies that take their responsibilities seriously sometimes have difficulty in releasing fully (what is that anyway!) accessible sites all of the time – BUT let’s not shoot them right away or we’ll turn them away from accessibility altogether.

In an ideal world, every new site developed would be as accessible as possible to as many people as possible, but in reality it’s important to realise that this may not happen for some time. So, whilst I think it’s valuable to highlight the failures of some, I also think we need to recognise and support the efforts of others.

If you would like to know more about my own personal philosophy and belief that underpins Segala’s long-term vision of where the industry should be heading, please take a look at my post on E-consultancy.

I would welcome anybody to get in touch with Segala (or me) directly if they have any further comments or concerns.

Paul Walsh, CEO, Segala

Link: http://www.e-consultancy.com/forum/103761-accessibility-we-can-t-get-it-right-on-the-high-street-what-hope-do-we-have-on-the-web.html?keywords=segala</description>
		<content:encoded><![CDATA[<p>In view of the comments and opinions expressed here, I would like to state for the record that Segala is not connected or involved with <a href="http://www.sonyericsson.com" rel="nofollow">http://www.sonyericsson.com</a> or any of its sub-sites, this includes the DaVinci Code section of this site.  Segala has not audited or certified this website for accessibility and has made no claims to that effect.</p>
<p>Segala was not responsible for the design or build of the <a href="http://www.davincicodetrail.co.uk" rel="nofollow">http://www.davincicodetrail.co.uk</a> website, nor indeed the decision to provide one version in Flash and an alternative HTML version.  The Segala certificate clearly states which URLs it has certified.  </p>
<p>The decision to create the <a href="http://www.davincicodetrail.co.uk/" rel="nofollow">http://www.davincicodetrail.co.uk/</a> website and the hosting of the Flash game on a separate URL was in no way influenced by and beyond any control of Segala.</p>
<p>Our press release states that we certified <a href="http://www.davincicodetrail.co.uk/" rel="nofollow">http://www.davincicodetrail.co.uk/</a>.  We would like to point out that it does not allude to or suggest that we certified the flash game or any other elements on <a href="http://www.sonyericsson.com" rel="nofollow">http://www.sonyericsson.com</a>, however we do acknowledge that the wording may have caused some confusion as to whether or not we certified the flash game on which the O2 website is centered around.  For this we apologise and we thank you for pointing this out to us.  We sincerely did not intend for this Press release to be “misleading propaganda” and we have taken the decision to amend our press release to clarify the issues raised.</p>
<p>Unfortunately, the flash site/elements were already built before Segala was engaged to audit and certify the accessible alternative. I must point out that with the exception of the game (which is now clearly marked as inaccessible to some) the HTML alternative provides exactly the same information as the flash site. So, although I agree it is best practice to create one site that is accessible to all, in this instance the best alternative was to create an accessible HTML version of the site.</p>
<p>We could have been less enthusiastic in issuing the PR for this particular site, but we are keen to help move the industry forward from what it currently perceives as ‘accessibility extremism’ by demonstrating how some companies embrace accessibility for the long haul and are embedding it into their strategies, brand marketing and development guidelines. However, even those companies that take their responsibilities seriously sometimes have difficulty in releasing fully (what is that anyway!) accessible sites all of the time – BUT let’s not shoot them right away or we’ll turn them away from accessibility altogether.</p>
<p>In an ideal world, every new site developed would be as accessible as possible to as many people as possible, but in reality it’s important to realise that this may not happen for some time. So, whilst I think it’s valuable to highlight the failures of some, I also think we need to recognise and support the efforts of others.</p>
<p>If you would like to know more about my own personal philosophy and belief that underpins Segala’s long-term vision of where the industry should be heading, please take a look at my post on E-consultancy.</p>
<p>I would welcome anybody to get in touch with Segala (or me) directly if they have any further comments or concerns.</p>
<p>Paul Walsh, CEO, Segala</p>
<p>Link: <a href="http://www.e-consultancy.com/forum/103761-accessibility-we-can-t-get-it-right-on-the-high-street-what-hope-do-we-have-on-the-web.html?keywords=segala" rel="nofollow">http://www.e-consultancy.com/forum/103761-accessibility-we-can-t-get-it-right-on-the-high-street-what-hope-do-we-have-on-the-web.html?keywords=segala</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: chickenskinners.com &#187; Blog Archive &#187; DTI website</title>
		<link>http://www.webstandards.org/2006/06/27/spurious-accessibility-claims-and-designs/comment-page-1/#comment-1945</link>
		<dc:creator>chickenskinners.com &#187; Blog Archive &#187; DTI website</dc:creator>
		<pubDate>Fri, 30 Jun 2006 16:25:01 +0000</pubDate>
		<guid isPermaLink="false">http://www.webstandards.org/2006/06/27/spurious-accessibility-claims-and-designs/#comment-1945</guid>
		<description>[...] Again this is something I saw on the WaSP site. [...]</description>
		<content:encoded><![CDATA[<p>[...] Again this is something I saw on the WaSP site. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: nortypig</title>
		<link>http://www.webstandards.org/2006/06/27/spurious-accessibility-claims-and-designs/comment-page-1/#comment-1930</link>
		<dc:creator>nortypig</dc:creator>
		<pubDate>Fri, 30 Jun 2006 01:54:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.webstandards.org/2006/06/27/spurious-accessibility-claims-and-designs/#comment-1930</guid>
		<description>I&#039;m also concerned that from a managerial standpoint the only thing the powers in these companies may actually know about accessiblility comes across their desk in a memo. They rely on a technical department to advise and serve them and often you might find these people not only lacking but unwilling to admit there is something in the world of web development they may not be the best in the world at doing.

So web guys / girls say its AAA and manager signs piece of paper and sends off to PR guys / girls and the show begins.

Either that or I&#039;ve had the exact same experiences with a number of agencies and a major CMS developer who are just bold faced liars. I&#039;m not sure which is scarier.</description>
		<content:encoded><![CDATA[<p>I&#8217;m also concerned that from a managerial standpoint the only thing the powers in these companies may actually know about accessiblility comes across their desk in a memo. They rely on a technical department to advise and serve them and often you might find these people not only lacking but unwilling to admit there is something in the world of web development they may not be the best in the world at doing.</p>
<p>So web guys / girls say its AAA and manager signs piece of paper and sends off to PR guys / girls and the show begins.</p>
<p>Either that or I&#8217;ve had the exact same experiences with a number of agencies and a major CMS developer who are just bold faced liars. I&#8217;m not sure which is scarier.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sophie Dennis</title>
		<link>http://www.webstandards.org/2006/06/27/spurious-accessibility-claims-and-designs/comment-page-1/#comment-1918</link>
		<dc:creator>Sophie Dennis</dc:creator>
		<pubDate>Thu, 29 Jun 2006 13:38:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.webstandards.org/2006/06/27/spurious-accessibility-claims-and-designs/#comment-1918</guid>
		<description>Doing a little digging I noticed that neither of the main design/build agencies used - Fresh01 and Fujitsu - are on the new official Central Office of Information (&lt;abbr&gt;COI&lt;/abbr&gt;) &lt;a href=&quot;http://www.coi.gov.uk/aboutcoi.php?page=80&quot; title=&quot;COI Digital Media Roster&quot; rel=&quot;nofollow&quot;&gt;digital media roster&lt;/a&gt;. (The COI is the official UK Government department which &quot;provides advice, procurement and project management on every aspect of communications&quot; to other govenment departments. The roster is essentially a list of pre-approved suppliers for government communications projects). Leaving aside the issues with how the hoop-jumping required to get on the roster effectively excludes smaller agencies, the &lt;abbr title=&quot;Department of Trade and Industry&quot;&gt;DTI&lt;/abbr&gt; fiasco is surely exactly the kind of thing the COI and their roster exist to prevent? 

So I&#039;d suggest a couple of other interesting questions to add to Bruce and Dan&#039;s list:

1) Did the DTI use the services of the COI when commissioning the website?

and one for the COI:

2) Were agencies&#039; capabilities in producing digital media which complies with the &lt;abbr title=&quot;Disability Discrimination Act&quot;&gt;DDA&lt;/abbr&gt; and &lt;abbr title=&quot;World Wide Web Consortium&quot;&gt;W3C&lt;/abbr&gt; standards a criteria used when compiling the roster, and if so, how were the agencies&#039; capabilities in these areas assessed?</description>
		<content:encoded><![CDATA[<p>Doing a little digging I noticed that neither of the main design/build agencies used &#8211; Fresh01 and Fujitsu &#8211; are on the new official Central Office of Information (<abbr>COI</abbr>) <a href="http://www.coi.gov.uk/aboutcoi.php?page=80" title="COI Digital Media Roster" rel="nofollow">digital media roster</a>. (The COI is the official UK Government department which &#8220;provides advice, procurement and project management on every aspect of communications&#8221; to other govenment departments. The roster is essentially a list of pre-approved suppliers for government communications projects). Leaving aside the issues with how the hoop-jumping required to get on the roster effectively excludes smaller agencies, the <abbr title="Department of Trade and Industry">DTI</abbr> fiasco is surely exactly the kind of thing the COI and their roster exist to prevent? </p>
<p>So I&#8217;d suggest a couple of other interesting questions to add to Bruce and Dan&#8217;s list:</p>
<p>1) Did the DTI use the services of the COI when commissioning the website?</p>
<p>and one for the COI:</p>
<p>2) Were agencies&#8217; capabilities in producing digital media which complies with the <abbr title="Disability Discrimination Act">DDA</abbr> and <abbr title="World Wide Web Consortium">W3C</abbr> standards a criteria used when compiling the roster, and if so, how were the agencies&#8217; capabilities in these areas assessed?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Dynamic page generated in 0.386 seconds. -->
<!-- Cached page generated by WP-Super-Cache on 2013-05-02 13:05:32 -->