<?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: One Step Forwards, Two Steps Back?</title>
	<atom:link href="http://www.headstar.com/eablive/?feed=rss2&#038;p=164" rel="self" type="application/rss+xml" />
	<link>http://www.headstar.com/eablive/?p=164</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: Stuart Harrison</title>
		<link>http://www.headstar.com/eablive/?p=164&#038;cpage=1#comment-5397</link>
		<dc:creator><![CDATA[Stuart Harrison]]></dc:creator>
		<pubDate>Thu, 19 Mar 2009 14:46:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.headstar.com/eablive/?p=164#comment-5397</guid>
		<description><![CDATA[Couldn&#039;t agree more with Martin. 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&#039;t mean the whole site is inaccessible. Sure, point out the problems so they can be fixed, but don&#039;t brand websites with the label &#039;inaccessible&#039; just because of a few issues.

And don&#039;t get me started on suppliers. The main problem is that web teams aren&#039;t consulted before deals are entered into and contracts are signed. As a local authority web person, I&#039;ve found myself on more than one occasion being forced to implement systems that I know are inaccessible, but I&#039;ve got no way of blocking their release.]]></description>
		<content:encoded><![CDATA[<p>Couldn&#8217;t agree more with Martin. 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&#8217;t mean the whole site is inaccessible. Sure, point out the problems so they can be fixed, but don&#8217;t brand websites with the label &#8216;inaccessible&#8217; just because of a few issues.</p>
<p>And don&#8217;t get me started on suppliers. The main problem is that web teams aren&#8217;t consulted before deals are entered into and contracts are signed. As a local authority web person, I&#8217;ve found myself on more than one occasion being forced to implement systems that I know are inaccessible, but I&#8217;ve got no way of blocking their release.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Martin Kliehm</title>
		<link>http://www.headstar.com/eablive/?p=164&#038;cpage=1#comment-5333</link>
		<dc:creator><![CDATA[Martin Kliehm]]></dc:creator>
		<pubDate>Sun, 16 Mar 2008 14:41:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.headstar.com/eablive/?p=164#comment-5333</guid>
		<description><![CDATA[I don&#039;t think this binary approach passed / failed is helpful. Just because a website failed level A or AA doesn&#039;t necessarily mean it is inaccessible to people with disabilities. Also it would be interesting how badly they failed.

In Germany people often use the &lt;a href=&quot;http://bitvtest.de/index.php?a=dl&amp;s=g&quot; rel=&quot;nofollow&quot;&gt;BITV-Test&lt;/a&gt; based on our legislation of WCAG. It is a well-documented site with much discussion of how to apply the tests. For a quick check, only three pages of different types are chosen, like the home page, a content page, and a contact form.

Each criterion is assigned with a severity: major, normal, or minor. Starting with a total of 100 points, for each failed criterion either 3, 2, or 1 points are subtracted, half of the points when a criterion is partially fulfilled. A website is highly accessible when the total is 95 or above, well accessible at 90-94 points, and badly accessible below 90. Also a few checkpoints can change the result into &quot;inaccessible&quot;, no matter what the actual score was. Think of navigational images without alt-text.

So what we got here is a score that can be benchmarked with other websites, a more precise result how accessible a website is. I think that&#039;s a better approach.]]></description>
		<content:encoded><![CDATA[<p>I don&#8217;t think this binary approach passed / failed is helpful. Just because a website failed level A or AA doesn&#8217;t necessarily mean it is inaccessible to people with disabilities. Also it would be interesting how badly they failed.</p>
<p>In Germany people often use the <a href="http://bitvtest.de/index.php?a=dl&amp;s=g" rel="nofollow">BITV-Test</a> based on our legislation of WCAG. It is a well-documented site with much discussion of how to apply the tests. For a quick check, only three pages of different types are chosen, like the home page, a content page, and a contact form.</p>
<p>Each criterion is assigned with a severity: major, normal, or minor. Starting with a total of 100 points, for each failed criterion either 3, 2, or 1 points are subtracted, half of the points when a criterion is partially fulfilled. A website is highly accessible when the total is 95 or above, well accessible at 90-94 points, and badly accessible below 90. Also a few checkpoints can change the result into &#8220;inaccessible&#8221;, no matter what the actual score was. Think of navigational images without alt-text.</p>
<p>So what we got here is a score that can be benchmarked with other websites, a more precise result how accessible a website is. I think that&#8217;s a better approach.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
