<?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: SharePoint and Web Accessibility</title>
	<atom:link href="http://www.brucelawson.co.uk/2008/sharepoint-and-web-accessibility/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.brucelawson.co.uk/2008/sharepoint-and-web-accessibility/</link>
	<description></description>
	<lastBuildDate>Fri, 10 Sep 2010 10:08:26 +0100</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: What does &#8220;making your website accessible&#8221; actually mean? &#124; Aarhus 2010 News &#124; J. Boye Conferences</title>
		<link>http://www.brucelawson.co.uk/2008/sharepoint-and-web-accessibility/comment-page-1/#comment-689037</link>
		<dc:creator>What does &#8220;making your website accessible&#8221; actually mean? &#124; Aarhus 2010 News &#124; J. Boye Conferences</dc:creator>
		<pubDate>Mon, 06 Sep 2010 13:58:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.brucelawson.co.uk/index.php/?p=461#comment-689037</guid>
		<description>[...] use SharePoint 2007 for all their online activities. SharePoint 2007 is not exactly known for it&#8217;s great accessibility, so the organisation faced quite a challenge. The ambition was to customise SharePoint in [...]</description>
		<content:encoded><![CDATA[<p>[...] use SharePoint 2007 for all their online activities. SharePoint 2007 is not exactly known for it&#8217;s great accessibility, so the organisation faced quite a challenge. The ambition was to customise SharePoint in [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Doug</title>
		<link>http://www.brucelawson.co.uk/2008/sharepoint-and-web-accessibility/comment-page-1/#comment-682333</link>
		<dc:creator>Doug</dc:creator>
		<pubDate>Thu, 05 Aug 2010 23:06:54 +0000</pubDate>
		<guid isPermaLink="false">http://www.brucelawson.co.uk/index.php/?p=461#comment-682333</guid>
		<description>Unfortunately- some of us don&#039;t have the option of using another cms.  We have to give every effort to seeing if we can make it work, because that&#039;s what they want.  In a year- maybe we can convince them.

So for now, I have to find ways to make this accessible.  Especially for the state of kansas (which I do sites for city, county and state agencies) which is strict on enforcing section 508 as well WCAG standards.

I am currently researching web parts that are compliant and finding ways to make a more compliant template.</description>
		<content:encoded><![CDATA[<p>Unfortunately- some of us don&#8217;t have the option of using another cms.  We have to give every effort to seeing if we can make it work, because that&#8217;s what they want.  In a year- maybe we can convince them.</p>
<p>So for now, I have to find ways to make this accessible.  Especially for the state of kansas (which I do sites for city, county and state agencies) which is strict on enforcing section 508 as well WCAG standards.</p>
<p>I am currently researching web parts that are compliant and finding ways to make a more compliant template.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Weekend Gazette &#8211; Link Collection for February 7 at STC AccessAbility SIG</title>
		<link>http://www.brucelawson.co.uk/2008/sharepoint-and-web-accessibility/comment-page-1/#comment-657452</link>
		<dc:creator>Weekend Gazette &#8211; Link Collection for February 7 at STC AccessAbility SIG</dc:creator>
		<pubDate>Sun, 07 Feb 2010 22:40:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.brucelawson.co.uk/index.php/?p=461#comment-657452</guid>
		<description>[...] and education, but that requires knowledge about its accessibility. Bruce Lawson wrote about SharePoint accessibility in 2008 and Alastair Campbell wrote about SharePoint 2010 late last year. These two posts should get you [...]</description>
		<content:encoded><![CDATA[<p>[...] and education, but that requires knowledge about its accessibility. Bruce Lawson wrote about SharePoint accessibility in 2008 and Alastair Campbell wrote about SharePoint 2010 late last year. These two posts should get you [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: AlastairC</title>
		<link>http://www.brucelawson.co.uk/2008/sharepoint-and-web-accessibility/comment-page-1/#comment-657126</link>
		<dc:creator>AlastairC</dc:creator>
		<pubDate>Fri, 05 Feb 2010 17:30:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.brucelawson.co.uk/index.php/?p=461#comment-657126</guid>
		<description>From what I gathered at a SharePoint 2010 event:
http://alastairc.ac/2009/11/sharepoint-2010-accessibility-event/

The accessibility &#039;kit&#039; didn&#039;t help a whole lot, the developers there sounded pretty defeated.

The new version (not released yet) may improve things, but the devils in the detail (e.g. is accessibility possible vs is it default), and it&#039;s unknown so far.</description>
		<content:encoded><![CDATA[<p>From what I gathered at a SharePoint 2010 event:<br />
<a href="http://alastairc.ac/2009/11/sharepoint-2010-accessibility-event/" rel="nofollow">http://alastairc.ac/2009/11/sharepoint-2010-accessibility-event/</a></p>
<p>The accessibility &#8216;kit&#8217; didn&#8217;t help a whole lot, the developers there sounded pretty defeated.</p>
<p>The new version (not released yet) may improve things, but the devils in the detail (e.g. is accessibility possible vs is it default), and it&#8217;s unknown so far.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David McElroy</title>
		<link>http://www.brucelawson.co.uk/2008/sharepoint-and-web-accessibility/comment-page-1/#comment-517695</link>
		<dc:creator>David McElroy</dc:creator>
		<pubDate>Mon, 16 Jun 2008 12:27:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.brucelawson.co.uk/index.php/?p=461#comment-517695</guid>
		<description>Nice article, thanks. Without going about it myself does anyone know of an article that lists what points SharePoint does and doesnt meet out of the box and out of the box with accessability mode?

On the last comment
&quot;My point is - why bother, when most of the new generation Content Management Systems do a better job out of the box?&quot;

You have to bother when you are stuck in an organisation who already have SharePoint/MOSS 2007 and it needs to become accessible.</description>
		<content:encoded><![CDATA[<p>Nice article, thanks. Without going about it myself does anyone know of an article that lists what points SharePoint does and doesnt meet out of the box and out of the box with accessability mode?</p>
<p>On the last comment<br />
&#8220;My point is &#8211; why bother, when most of the new generation Content Management Systems do a better job out of the box?&#8221;</p>
<p>You have to bother when you are stuck in an organisation who already have SharePoint/MOSS 2007 and it needs to become accessible.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bruce</title>
		<link>http://www.brucelawson.co.uk/2008/sharepoint-and-web-accessibility/comment-page-1/#comment-488002</link>
		<dc:creator>Bruce</dc:creator>
		<pubDate>Thu, 24 Apr 2008 06:08:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.brucelawson.co.uk/index.php/?p=461#comment-488002</guid>
		<description>Interesting, Ivan. Thanks.

The Equality and Human Rights Commission might be single A compliant, but its homepage contains errors preventing it meeting AA compliance (largely html validation errors). It&#039;s riddled with inline styling, obtrusive JavaScript, the home page has this charming markup

&lt;code&gt;&lt;p&gt;&lt;strong&gt;&lt;font color=&quot;#cb1e4a&quot; size=&quot;4&quot;&gt;&lt;/code&gt; 

to &lt;strong&gt;look like&lt;/strong&gt; a heading - thereby not fully conforming to &lt;a href=&quot;http://www.w3.org/TR/WCAG10/wai-pageauth.html#tech-logical-headingscheckpoint&quot; rel=&quot;nofollow&quot;&gt; WCAG checkpoint 3.5&lt;/a&gt; &quot;Use header elements to convey document structure and use them according to specification. [Priority 2] For example, in HTML, use H2 to indicate a subsection of H1. Do not use headers for font effects.&quot;

He doesn&#039;t mention whether he uses AKS or not. I don&#039;t doubt that it&#039;s possible to force Sharepoint to produce ugly, bloated code that almost meets priority AA, with a hell of a lot of work and voodoo magic.
 
My point is - why bother, when most of the new generation Content Management Systems do a better job out of the box?</description>
		<content:encoded><![CDATA[<p>Interesting, Ivan. Thanks.</p>
<p>The Equality and Human Rights Commission might be single A compliant, but its homepage contains errors preventing it meeting AA compliance (largely html validation errors). It&#8217;s riddled with inline styling, obtrusive JavaScript, the home page has this charming markup</p>
<p><code>&lt;p&gt;&lt;strong&gt;&lt;font color="#cb1e4a" size="4"&gt;</code> </p>
<p>to <strong>look like</strong> a heading &#8211; thereby not fully conforming to <a href="http://www.w3.org/TR/WCAG10/wai-pageauth.html#tech-logical-headingscheckpoint" rel="nofollow"> WCAG checkpoint 3.5</a> &#8220;Use header elements to convey document structure and use them according to specification. [Priority 2] For example, in HTML, use H2 to indicate a subsection of H1. Do not use headers for font effects.&#8221;</p>
<p>He doesn&#8217;t mention whether he uses AKS or not. I don&#8217;t doubt that it&#8217;s possible to force Sharepoint to produce ugly, bloated code that almost meets priority AA, with a hell of a lot of work and voodoo magic.</p>
<p>My point is &#8211; why bother, when most of the new generation Content Management Systems do a better job out of the box?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
