<?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: Council Web Accessibility ‘Should Be Built Into Procurement’</title>
	<atom:link href="http://www.headstar.com/eablive/?feed=rss2&#038;p=566" rel="self" type="application/rss+xml" />
	<link>http://www.headstar.com/eablive/?p=566</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: Martin Sloan</title>
		<link>http://www.headstar.com/eablive/?p=566&#038;cpage=1#comment-6115</link>
		<dc:creator><![CDATA[Martin Sloan]]></dc:creator>
		<pubDate>Thu, 21 Apr 2011 16:32:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.headstar.com/eablive/?p=566#comment-6115</guid>
		<description><![CDATA[Interesting to see that the report concludes that accessibility &quot;should be built into procurement&quot;.

Councils and other public sector bodies have, since January 2006, been required by law to specify appropriate accessibility requirements, but clearly awareness of these legal requirements remains low.

The Public Contracts Regulations 2006 (and the Scottish equivalent, the Public Contracts (Scotland) Regulations 2006) require that:

&quot;[w]hen laying down technical specifications…a contracting authority shall, wherever possible, take into account criteria for disabled persons or the suitability of the design for all users.&quot;

This means that whenever a contracting authority issues an ITT for the procurement of any ICT goods and services (including software, hardware and websites), it should include appropriate requirements in relation to the accessibility of that ICT.

The regulations go on to say that technical specifications should be defined by reference to technical specifications in the following order of preference: British standards transposing European standards; European technical approvals; common technical specifications; international standards; or other technical reference systems established by the European standardisation bodies. In their absence, the relevant British equivalent should be used.

Clearly, this could include the W3C&#039;s Web Content Accessibility Guidelines (WCAG), BS8878 (which references the WCAG), and the various ICOs that deal with human computer interaction and human centred design.

Martin]]></description>
		<content:encoded><![CDATA[<p>Interesting to see that the report concludes that accessibility &#8220;should be built into procurement&#8221;.</p>
<p>Councils and other public sector bodies have, since January 2006, been required by law to specify appropriate accessibility requirements, but clearly awareness of these legal requirements remains low.</p>
<p>The Public Contracts Regulations 2006 (and the Scottish equivalent, the Public Contracts (Scotland) Regulations 2006) require that:</p>
<p>&#8220;[w]hen laying down technical specifications…a contracting authority shall, wherever possible, take into account criteria for disabled persons or the suitability of the design for all users.&#8221;</p>
<p>This means that whenever a contracting authority issues an ITT for the procurement of any ICT goods and services (including software, hardware and websites), it should include appropriate requirements in relation to the accessibility of that ICT.</p>
<p>The regulations go on to say that technical specifications should be defined by reference to technical specifications in the following order of preference: British standards transposing European standards; European technical approvals; common technical specifications; international standards; or other technical reference systems established by the European standardisation bodies. In their absence, the relevant British equivalent should be used.</p>
<p>Clearly, this could include the W3C&#8217;s Web Content Accessibility Guidelines (WCAG), BS8878 (which references the WCAG), and the various ICOs that deal with human computer interaction and human centred design.</p>
<p>Martin</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Walker</title>
		<link>http://www.headstar.com/eablive/?p=566&#038;cpage=1#comment-6109</link>
		<dc:creator><![CDATA[David Walker]]></dc:creator>
		<pubDate>Mon, 04 Apr 2011 15:24:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.headstar.com/eablive/?p=566#comment-6109</guid>
		<description><![CDATA[I agree with Mick in that getting a CMS or a developer to program one, that is accessible across the board is easier said than done. However, the good news is that things are heading in the right direction with more council websites passing the RNIB accessibility assessment in 2011 than in 2010.

David]]></description>
		<content:encoded><![CDATA[<p>I agree with Mick in that getting a CMS or a developer to program one, that is accessible across the board is easier said than done. However, the good news is that things are heading in the right direction with more council websites passing the RNIB accessibility assessment in 2011 than in 2010.</p>
<p>David</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mick Phythian</title>
		<link>http://www.headstar.com/eablive/?p=566&#038;cpage=1#comment-6103</link>
		<dc:creator><![CDATA[Mick Phythian]]></dc:creator>
		<pubDate>Wed, 30 Mar 2011 13:36:28 +0000</pubDate>
		<guid isPermaLink="false">http://www.headstar.com/eablive/?p=566#comment-6103</guid>
		<description><![CDATA[When I wrote the tender documents for our current site in 2005/6 I did of course specify accessibility (to &#039;AA&#039; standard minimum) as one would expect, as as the report proposes. Without naming names, getting a CMS supplier to actually deliver that is a nightmare, since one doesn&#039;t find out until the content is loaded and the site is up and running whether it actually is or not - and what do you do then? There is also the additional complexity of webservices, which are frequently procured and delivered from a range of suppliers, and can also impact upon a sites accessibility.

To quote an expert on this field, &quot;accessibility is not a binary state&quot;, and is therefore not easy to contractually specify.

So, yet again, from a practitioner&#039;s view, easier said than done!]]></description>
		<content:encoded><![CDATA[<p>When I wrote the tender documents for our current site in 2005/6 I did of course specify accessibility (to &#8216;AA&#8217; standard minimum) as one would expect, as as the report proposes. Without naming names, getting a CMS supplier to actually deliver that is a nightmare, since one doesn&#8217;t find out until the content is loaded and the site is up and running whether it actually is or not &#8211; and what do you do then? There is also the additional complexity of webservices, which are frequently procured and delivered from a range of suppliers, and can also impact upon a sites accessibility.</p>
<p>To quote an expert on this field, &#8220;accessibility is not a binary state&#8221;, and is therefore not easy to contractually specify.</p>
<p>So, yet again, from a practitioner&#8217;s view, easier said than done!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
