<?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: Corporate websites and the case for accessibility	</title>
	<atom:link href="https://www.corporate-eye.com/main/corporate-websites-accessibility/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.corporate-eye.com/main/corporate-websites-accessibility/</link>
	<description>...compare, compete, excel</description>
	<lastBuildDate>Wed, 29 Jul 2020 11:30:50 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	
	<item>
		<title>
		By: Brian Kelly		</title>
		<link>https://www.corporate-eye.com/main/corporate-websites-accessibility/#comment-1998</link>

		<dc:creator><![CDATA[Brian Kelly]]></dc:creator>
		<pubDate>Tue, 17 Mar 2009 11:50:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.corporate-eye.com/?p=4743#comment-1998</guid>

					<description><![CDATA[Hi Helen
   I agree completely with you when you say &quot;websites cannot meet the needs of every visitor&quot;. The problem is that the guidelines developed by WAI and the accompanying hype has led people to believe that applying a few simple rules will provide universal accessibility. And the dangers with this view are that people may think that WCAG conformance is all they need, that if WCAG conformance proves difficult they should ignore the guidelines completely or if  WCAG conformance proves difficult they should not deploy a service, even if it proves beneficial to many.
   I have written a blog post which summarises my views in the context of e-learning, which is available at
http://ukwebfocus.wordpress.com/2009/03/02/rethinking-web-accessibility-for-e-learning/
   I should add that I have submitted this blog post to the Edublogger Scholar contest, so I have a vested interest in clicks on the Edublogger Scholar contest logo - but if you think it would be beneficial to those interested in promoting best practices for accessibility if a blog post on accessibility was to win a prize, then I&#039;d be happy for you to do that :-)
    Further thoughts on my views on accessibility are available on my blog:
http://ukwebfocus.wordpress.com/category/accessibility/
  or have been published in various peer-reviewed publications:
http://www.ukoln.ac.uk/web-focus/papers/#accessibility

All the best

Brian Kelly, UKOLN]]></description>
			<content:encoded><![CDATA[<p>Hi Helen<br />
   I agree completely with you when you say &#8220;websites cannot meet the needs of every visitor&#8221;. The problem is that the guidelines developed by WAI and the accompanying hype has led people to believe that applying a few simple rules will provide universal accessibility. And the dangers with this view are that people may think that WCAG conformance is all they need, that if WCAG conformance proves difficult they should ignore the guidelines completely or if  WCAG conformance proves difficult they should not deploy a service, even if it proves beneficial to many.<br />
   I have written a blog post which summarises my views in the context of e-learning, which is available at<br />
<a href="http://ukwebfocus.wordpress.com/2009/03/02/rethinking-web-accessibility-for-e-learning/" rel="nofollow ugc">http://ukwebfocus.wordpress.com/2009/03/02/rethinking-web-accessibility-for-e-learning/</a><br />
   I should add that I have submitted this blog post to the Edublogger Scholar contest, so I have a vested interest in clicks on the Edublogger Scholar contest logo &#8211; but if you think it would be beneficial to those interested in promoting best practices for accessibility if a blog post on accessibility was to win a prize, then I&#8217;d be happy for you to do that :-)<br />
    Further thoughts on my views on accessibility are available on my blog:<br />
<a href="http://ukwebfocus.wordpress.com/category/accessibility/" rel="nofollow ugc">http://ukwebfocus.wordpress.com/category/accessibility/</a><br />
  or have been published in various peer-reviewed publications:<br />
<a href="http://www.ukoln.ac.uk/web-focus/papers/#accessibility" rel="nofollow ugc">http://www.ukoln.ac.uk/web-focus/papers/#accessibility</a></p>
<p>All the best</p>
<p>Brian Kelly, UKOLN</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Helen		</title>
		<link>https://www.corporate-eye.com/main/corporate-websites-accessibility/#comment-1997</link>

		<dc:creator><![CDATA[Helen]]></dc:creator>
		<pubDate>Tue, 17 Mar 2009 08:12:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.corporate-eye.com/?p=4743#comment-1997</guid>

					<description><![CDATA[Hello Brian,

Thanks very much for your comments, which have provided some great ideas for future posts! The article is simply an introduction to accessibility for corporate website managers, and we hoped it would create some discussion. 

As with most things, websites cannot meet the needs of every visitor. The aim is to make as much content accessible to as many people as possible. If we could encourage corporate websites to meet even minimum requirements, it would make them much more accessible for a larger range of visitors (across as many browsers as possible, even if they’re far from perfect).

We tried to provide a few ideas for things web masters could change in the short term to make a small difference, but also help them open internal discussions on the business benefits of replacing legacy systems or technologies with those that support accessibility best practice when the time comes to update.

The DRC (now the Equality and Human Rights Commission) report from 2004 that you mention (which I previously hadn’t read) received a very mixed response. Here are a few of the interesting and varied posts I found:

- ’&lt;a href=&quot;http://www.isolani.co.uk/blog/access/DrcReportOnUkWebAccessibility&quot; rel=&quot;nofollow ugc&quot;&gt;The DRC report into UK web accessibility&lt;/a&gt;’, by Mike Davies (who was the Technical Lead Web Developer on Legal &amp; General&#039;s web accessibility project)
- ‘DRC report says accessible websites are 35% more usable for all’, AbilityNet
- &#039;&lt;a href=&quot;http://www.webcredible.co.uk/user-friendly-resources/web-accessibility/drc-blew-it.shtml&quot; rel=&quot;nofollow ugc&quot;&gt;The DRC blew it&lt;/a&gt;&#039;, Webcredible 

(Read the report )

The accessibility guidelines aim to make websites more accessible and therefore more usable for disabled users. However, just because a website is accessible, it doesn’t necessarily follow that it’s usable for all visitors, and vice versa (although both go a long way to helping the other).

I’m not sure that it’s helpful for companies to believe that because their website is usable, they don’t need to implement or worry about meeting additional accessibility standards that could make it more so. They need to meet both requirements, as Mike Davies notes in &lt;a href=&quot;http://www.isolani.co.uk/blog/access/SitemorseCriticisesDrcsUsabilityStance&quot; rel=&quot;nofollow ugc&quot;&gt;another post on the subject&lt;/a&gt;.

We’ll try to cover some of the issues you’ve raised in coming posts. I’d be interested to hear what you think, Brian, and what other experts also think about these topics. Do you agree? If you&#039;re a corporate web manager who’s tackled these issues, get in touch!

Helen]]></description>
			<content:encoded><![CDATA[<p>Hello Brian,</p>
<p>Thanks very much for your comments, which have provided some great ideas for future posts! The article is simply an introduction to accessibility for corporate website managers, and we hoped it would create some discussion. </p>
<p>As with most things, websites cannot meet the needs of every visitor. The aim is to make as much content accessible to as many people as possible. If we could encourage corporate websites to meet even minimum requirements, it would make them much more accessible for a larger range of visitors (across as many browsers as possible, even if they’re far from perfect).</p>
<p>We tried to provide a few ideas for things web masters could change in the short term to make a small difference, but also help them open internal discussions on the business benefits of replacing legacy systems or technologies with those that support accessibility best practice when the time comes to update.</p>
<p>The DRC (now the Equality and Human Rights Commission) report from 2004 that you mention (which I previously hadn’t read) received a very mixed response. Here are a few of the interesting and varied posts I found:</p>
<p>&#8211; ’<a href="http://www.isolani.co.uk/blog/access/DrcReportOnUkWebAccessibility" rel="nofollow ugc">The DRC report into UK web accessibility</a>’, by Mike Davies (who was the Technical Lead Web Developer on Legal &#038; General&#8217;s web accessibility project)<br />
&#8211; ‘DRC report says accessible websites are 35% more usable for all’, AbilityNet<br />
&#8211; &#8216;<a href="http://www.webcredible.co.uk/user-friendly-resources/web-accessibility/drc-blew-it.shtml" rel="nofollow ugc">The DRC blew it</a>&#8216;, Webcredible </p>
<p>(Read the report )</p>
<p>The accessibility guidelines aim to make websites more accessible and therefore more usable for disabled users. However, just because a website is accessible, it doesn’t necessarily follow that it’s usable for all visitors, and vice versa (although both go a long way to helping the other).</p>
<p>I’m not sure that it’s helpful for companies to believe that because their website is usable, they don’t need to implement or worry about meeting additional accessibility standards that could make it more so. They need to meet both requirements, as Mike Davies notes in <a href="http://www.isolani.co.uk/blog/access/SitemorseCriticisesDrcsUsabilityStance" rel="nofollow ugc">another post on the subject</a>.</p>
<p>We’ll try to cover some of the issues you’ve raised in coming posts. I’d be interested to hear what you think, Brian, and what other experts also think about these topics. Do you agree? If you&#8217;re a corporate web manager who’s tackled these issues, get in touch!</p>
<p>Helen</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Brian Kelly		</title>
		<link>https://www.corporate-eye.com/main/corporate-websites-accessibility/#comment-1988</link>

		<dc:creator><![CDATA[Brian Kelly]]></dc:creator>
		<pubDate>Mon, 16 Mar 2009 13:06:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.corporate-eye.com/?p=4743#comment-1988</guid>

					<description><![CDATA[Although the blog post provides some examples of potential benefits of implementing best practices to enhance accessibility, it fails to provide any advice on the approaches organisations should take if there are conflicts with other business objectives.  

For example, what if:

o There are tensions between the requirements of different groups of people with disabilities?
o Business have existing systems which don&#039;t support accessibility best practices?
o Browser support lags behind best practices (e.g. IE 6)?
o Evidence shows that Web sites which don&#039;t implement accessibility guidelines do well in usability studies by people with disabilities (e.g. the DRC report and the Egg.co.uk Web site)?]]></description>
			<content:encoded><![CDATA[<p>Although the blog post provides some examples of potential benefits of implementing best practices to enhance accessibility, it fails to provide any advice on the approaches organisations should take if there are conflicts with other business objectives.  </p>
<p>For example, what if:</p>
<p>o There are tensions between the requirements of different groups of people with disabilities?<br />
o Business have existing systems which don&#8217;t support accessibility best practices?<br />
o Browser support lags behind best practices (e.g. IE 6)?<br />
o Evidence shows that Web sites which don&#8217;t implement accessibility guidelines do well in usability studies by people with disabilities (e.g. the DRC report and the Egg.co.uk Web site)?</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Corporate websites and the case for accessibility		</title>
		<link>https://www.corporate-eye.com/main/corporate-websites-accessibility/#comment-1979</link>

		<dc:creator><![CDATA[Corporate websites and the case for accessibility]]></dc:creator>
		<pubDate>Fri, 13 Mar 2009 21:54:27 +0000</pubDate>
		<guid isPermaLink="false">http://www.corporate-eye.com/?p=4743#comment-1979</guid>

					<description><![CDATA[[...] Excerpt from:  Corporate websites and the case for accessibility [...]]]></description>
			<content:encoded><![CDATA[<p>[&#8230;] Excerpt from:  Corporate websites and the case for accessibility [&#8230;]</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Jonathan Waddingham		</title>
		<link>https://www.corporate-eye.com/main/corporate-websites-accessibility/#comment-1973</link>

		<dc:creator><![CDATA[Jonathan Waddingham]]></dc:creator>
		<pubDate>Fri, 13 Mar 2009 11:23:28 +0000</pubDate>
		<guid isPermaLink="false">http://www.corporate-eye.com/?p=4743#comment-1973</guid>

					<description><![CDATA[I think Helen makes some great points there - especially about having better accessibility making sites easier for *everyone* to use. There&#039;s really no excuse for jargon-filled brochureware sites these days, and they are ultimately self-defeating - if a site isn&#039;t clear, obtuse, or just plain unfriendly, then people are less likely to use it.

Thanks for the insight!]]></description>
			<content:encoded><![CDATA[<p>I think Helen makes some great points there &#8211; especially about having better accessibility making sites easier for *everyone* to use. There&#8217;s really no excuse for jargon-filled brochureware sites these days, and they are ultimately self-defeating &#8211; if a site isn&#8217;t clear, obtuse, or just plain unfriendly, then people are less likely to use it.</p>
<p>Thanks for the insight!</p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>
