<?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: The &#8216;accessibility backlash&#8217; &#8211; it&#8217;s a good thing!</title>
	<atom:link href="http://www.headstar.com/eablive/?feed=rss2&#038;p=55" rel="self" type="application/rss+xml" />
	<link>http://www.headstar.com/eablive/?p=55</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: Geoff Vines</title>
		<link>http://www.headstar.com/eablive/?p=55&#038;cpage=1#comment-29</link>
		<dc:creator><![CDATA[Geoff Vines]]></dc:creator>
		<pubDate>Tue, 20 Feb 2007 15:27:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.headstar.com/eablog/?p=55#comment-29</guid>
		<description><![CDATA[I think there is a risk some web site designers spend, and therefore waste, too much time adding percieved accessibility features that should not be required.

For example, you see three sizes of the letter &#039;A&#039; for adjusting text size, but it doesn&#039;t work cross-browser. The site is offered with alternative contrasts. A text only version is provided.

If the site is properly designed not to be &#039;anti-accessible&#039;, then I think we should give more credit to the end-user to know how to use the tools of their choice so that the site is accessible for them, whatever their particular disability.]]></description>
		<content:encoded><![CDATA[<p>I think there is a risk some web site designers spend, and therefore waste, too much time adding percieved accessibility features that should not be required.</p>
<p>For example, you see three sizes of the letter &#8216;A&#8217; for adjusting text size, but it doesn&#8217;t work cross-browser. The site is offered with alternative contrasts. A text only version is provided.</p>
<p>If the site is properly designed not to be &#8216;anti-accessible&#8217;, then I think we should give more credit to the end-user to know how to use the tools of their choice so that the site is accessible for them, whatever their particular disability.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Julie Howell</title>
		<link>http://www.headstar.com/eablive/?p=55&#038;cpage=1#comment-28</link>
		<dc:creator><![CDATA[Julie Howell]]></dc:creator>
		<pubDate>Mon, 19 Feb 2007 12:50:14 +0000</pubDate>
		<guid isPermaLink="false">http://www.headstar.com/eablog/?p=55#comment-28</guid>
		<description><![CDATA[Hi Andy

For me, usability and accessibility and two sides of the ‘good web design coin’.

Accessibility is the ability of any person, in any circumstance using any device to access content. Usability is the success of the user in completed a task in a reasonable amount of time, etc.

When considering the rights of disabled people, I use the term ‘usability by disabled people’. This is really what the Disability Discrimination Act is about.

Hmm… I feel a couple of blog posts coming on. Stay tuned…

I entirely agree with you regarding the disconnect between theory and practice. This is the very reason PAS 78: Guide to Good Practice in Commissioning Accessible Websites was commissioned (by the Disability Rights Commission… and it’s free of charge).

http://www.drc-gb.org/pas]]></description>
		<content:encoded><![CDATA[<p>Hi Andy</p>
<p>For me, usability and accessibility and two sides of the ‘good web design coin’.</p>
<p>Accessibility is the ability of any person, in any circumstance using any device to access content. Usability is the success of the user in completed a task in a reasonable amount of time, etc.</p>
<p>When considering the rights of disabled people, I use the term ‘usability by disabled people’. This is really what the Disability Discrimination Act is about.</p>
<p>Hmm… I feel a couple of blog posts coming on. Stay tuned…</p>
<p>I entirely agree with you regarding the disconnect between theory and practice. This is the very reason PAS 78: Guide to Good Practice in Commissioning Accessible Websites was commissioned (by the Disability Rights Commission… and it’s free of charge).</p>
<p><a href="http://www.drc-gb.org/pas" rel="nofollow">http://www.drc-gb.org/pas</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andy Baker</title>
		<link>http://www.headstar.com/eablive/?p=55&#038;cpage=1#comment-3</link>
		<dc:creator><![CDATA[Andy Baker]]></dc:creator>
		<pubDate>Fri, 26 Jan 2007 14:23:01 +0000</pubDate>
		<guid isPermaLink="false">http://www.headstar.com/eablog/?p=55#comment-3</guid>
		<description><![CDATA[That’s funny. I just wrote a late night rant about the same issue! &lt;a rel=&quot;nofollow&quot; title=&quot;http://www.90percentofeverything.com/2007/01/17/&quot; href=&quot;http://www.90percentofeverything.com/2007/01/17/&quot; rel=&quot;nofollow&quot;&gt;http://www.90percentofeverything.com/2007/01/17/
usability-over-accessibility-and-web-standards-any-day/&lt;/a&gt;

I think my beef is about the disconnect between what gets passed down as best practice and what actually provides tangible benefits.

With so many websites falling short on both accessibility *and* usability I would argue that in a situation where resources are limited (most of the time for most websites), prioritising usability is more likely to impact positively on accessibility than the other way round.

The cost benefit analysis with a lot of accessibility guidelines is rather lacking so it’s easy for the well intentioned to spend too much time on areas that produce only minimal benefit to the intended beneficiaries…]]></description>
		<content:encoded><![CDATA[<p>That’s funny. I just wrote a late night rant about the same issue! <a rel="nofollow" title="http://www.90percentofeverything.com/2007/01/17/" href="http://www.90percentofeverything.com/2007/01/17/" rel="nofollow"></a><a href="http://www.90percentofeverything.com/2007/01/17/" rel="nofollow">http://www.90percentofeverything.com/2007/01/17/</a><br />
usability-over-accessibility-and-web-standards-any-day/</p>
<p>I think my beef is about the disconnect between what gets passed down as best practice and what actually provides tangible benefits.</p>
<p>With so many websites falling short on both accessibility *and* usability I would argue that in a situation where resources are limited (most of the time for most websites), prioritising usability is more likely to impact positively on accessibility than the other way round.</p>
<p>The cost benefit analysis with a lot of accessibility guidelines is rather lacking so it’s easy for the well intentioned to spend too much time on areas that produce only minimal benefit to the intended beneficiaries…</p>
]]></content:encoded>
	</item>
</channel>
</rss>
