<?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: Don&#8217;t Provide an Accessibility Statement</title>
	<atom:link href="http://www.standards-schmandards.com/2006/just-say-no/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.standards-schmandards.com/2006/just-say-no/</link>
	<description>A pragmatic approach to web standards and accessibility</description>
	<lastBuildDate>Sun, 29 Jan 2012 18:44:22 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.1</generator>
	<item>
		<title>By: شات صوتي</title>
		<link>http://www.standards-schmandards.com/2006/just-say-no/comment-page-1/#comment-150727</link>
		<dc:creator>شات صوتي</dc:creator>
		<pubDate>Sun, 22 Jan 2012 03:13:54 +0000</pubDate>
		<guid isPermaLink="false">http://www.standards-schmandards.com/2006/just-say-no/#comment-150727</guid>
		<description>precious few examples here of Accessibility Statements and why they might be good</description>
		<content:encoded><![CDATA[<p>precious few examples here of Accessibility Statements and why they might be good</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Keydiscount.org, CD Keys for Sale, 100% legal key, cd key store, CD Keys, Trusted Keys, cheap Starcraft, Battlefield 3, Diablo 3, Brand new, un-used, Fast, safe, professional delivery, modern warfare 3, Call of Duty, Games, Star Wars: The Old Republic, ga</title>
		<link>http://www.standards-schmandards.com/2006/just-say-no/comment-page-1/#comment-148185</link>
		<dc:creator>Keydiscount.org, CD Keys for Sale, 100% legal key, cd key store, CD Keys, Trusted Keys, cheap Starcraft, Battlefield 3, Diablo 3, Brand new, un-used, Fast, safe, professional delivery, modern warfare 3, Call of Duty, Games, Star Wars: The Old Republic, ga</dc:creator>
		<pubDate>Tue, 03 Jan 2012 20:41:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.standards-schmandards.com/2006/just-say-no/#comment-148185</guid>
		<description>&lt;strong&gt;Keydiscount.org, CD Keys for Sale, 100% legal key, cd key store, CD Keys, Trusted Keys, cheap Starcraft, Battlefield 3, Diablo 3, Brand new, un-used, Fast, safe, professional delivery, modern warfare 3, Call of Duty, Games, Star Wars: The Old Republi...&lt;/strong&gt;

[...]Don&#8217;t Provide an Accessibility Statement- Standards Schmandards[...]...</description>
		<content:encoded><![CDATA[<p><strong>Keydiscount.org, CD Keys for Sale, 100% legal key, cd key store, CD Keys, Trusted Keys, cheap Starcraft, Battlefield 3, Diablo 3, Brand new, un-used, Fast, safe, professional delivery, modern warfare 3, Call of Duty, Games, Star Wars: The Old Republi&#8230;</strong></p>
<p>[...]Don&#8217;t Provide an Accessibility Statement- Standards Schmandards[...]&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: the world's Scholar Social Network!</title>
		<link>http://www.standards-schmandards.com/2006/just-say-no/comment-page-1/#comment-143387</link>
		<dc:creator>the world's Scholar Social Network!</dc:creator>
		<pubDate>Mon, 12 Dec 2011 07:03:01 +0000</pubDate>
		<guid isPermaLink="false">http://www.standards-schmandards.com/2006/just-say-no/#comment-143387</guid>
		<description>&lt;strong&gt;the world&#039;s Scholar Social Network!...&lt;/strong&gt;

[...]Don&#8217;t Provide an Accessibility Statement- Standards Schmandards[...]...</description>
		<content:encoded><![CDATA[<p><strong>the world&#8217;s Scholar Social Network!&#8230;</strong></p>
<p>[...]Don&#8217;t Provide an Accessibility Statement- Standards Schmandards[...]&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Defining A Good Accessibility Statement &#171; Clear Helper</title>
		<link>http://www.standards-schmandards.com/2006/just-say-no/comment-page-1/#comment-104135</link>
		<dc:creator>Defining A Good Accessibility Statement &#171; Clear Helper</dc:creator>
		<pubDate>Tue, 09 Mar 2010 15:11:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.standards-schmandards.com/2006/just-say-no/#comment-104135</guid>
		<description>[...] Standards Schmandards: Don’t Provide an Accessibility Statement [...]</description>
		<content:encoded><![CDATA[<p>[...] Standards Schmandards: Don’t Provide an Accessibility Statement [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Just another day&#8230; &#187; Blog Archive &#187; Are Accessibility Statements Useful?</title>
		<link>http://www.standards-schmandards.com/2006/just-say-no/comment-page-1/#comment-68780</link>
		<dc:creator>Just another day&#8230; &#187; Blog Archive &#187; Are Accessibility Statements Useful?</dc:creator>
		<pubDate>Tue, 23 Dec 2008 23:33:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.standards-schmandards.com/2006/just-say-no/#comment-68780</guid>
		<description>[...] question the usefulness of accessibility statements. The most notable of these, by Rosie Sherry and Peter Krantz, conclude that accessibility statements are not useful and should therefore be avoided. Reading [...]</description>
		<content:encoded><![CDATA[<p>[...] question the usefulness of accessibility statements. The most notable of these, by Rosie Sherry and Peter Krantz, conclude that accessibility statements are not useful and should therefore be avoided. Reading [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: NovaDexeus &#187; Blog Archive &#187; Podcast 61: Accessibility Statements</title>
		<link>http://www.standards-schmandards.com/2006/just-say-no/comment-page-1/#comment-46696</link>
		<dc:creator>NovaDexeus &#187; Blog Archive &#187; Podcast 61: Accessibility Statements</dc:creator>
		<pubDate>Mon, 09 Jun 2008 12:20:35 +0000</pubDate>
		<guid isPermaLink="false">http://www.standards-schmandards.com/2006/just-say-no/#comment-46696</guid>
		<description>[...] Just Say No [...]</description>
		<content:encoded><![CDATA[<p>[...] Just Say No [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: PGT</title>
		<link>http://www.standards-schmandards.com/2006/just-say-no/comment-page-1/#comment-40890</link>
		<dc:creator>PGT</dc:creator>
		<pubDate>Mon, 14 Apr 2008 00:43:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.standards-schmandards.com/2006/just-say-no/#comment-40890</guid>
		<description>So, is this a bad thing? http://home.earthlink.net/~patrickgtracy/accessibility.html

I have seen precious few examples here of Accessibility Statements and why they might be good or bad.</description>
		<content:encoded><![CDATA[<p>So, is this a bad thing? <a href="http://home.earthlink.net/~patrickgtracy/accessibility.html" rel="nofollow">http://home.earthlink.net/~patrickgtracy/accessibility.html</a></p>
<p>I have seen precious few examples here of Accessibility Statements and why they might be good or bad.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: &#187; Blog Archive &#187; Accessibility, Usability and Resizing Widgets - StevenClark.com.au</title>
		<link>http://www.standards-schmandards.com/2006/just-say-no/comment-page-1/#comment-20241</link>
		<dc:creator>&#187; Blog Archive &#187; Accessibility, Usability and Resizing Widgets - StevenClark.com.au</dc:creator>
		<pubDate>Tue, 25 Sep 2007 10:32:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.standards-schmandards.com/2006/just-say-no/#comment-20241</guid>
		<description>[...] text manually. I&#8217;m a big fan of providing extra information, reminiscent of the now faux pas accessibility page heavily campaigned against not so long ago. In the big picture I&#8217;m a fan of these documents [...]</description>
		<content:encoded><![CDATA[<p>[...] text manually. I&#8217;m a big fan of providing extra information, reminiscent of the now faux pas accessibility page heavily campaigned against not so long ago. In the big picture I&#8217;m a fan of these documents [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael Hart</title>
		<link>http://www.standards-schmandards.com/2006/just-say-no/comment-page-1/#comment-2719</link>
		<dc:creator>Michael Hart</dc:creator>
		<pubDate>Mon, 12 Mar 2007 00:25:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.standards-schmandards.com/2006/just-say-no/#comment-2719</guid>
		<description>I’m a BLIND systems programmer and my work includes web development. 

As a user of adaptive technology, I don’t tend to go looking for these statements and most of us are aware of the accepted conventions for navigational assistance. 

However, new user’s will learn something from help/navigational information as will everyone else, so this should be provided, assumeing it is not redundant. Indeed I feel this information should be part of the more general “about our website” pages as opposed to the “accessibility” pages. 

I’ve seen the accessibility statement used to do everything but help users with disabilities, yes most of the information that should be here can just as correctly be put into the “about our website” pages but some things can’t, most notably the list of known accessibility issues and related helpful information as such things would unbalance the help pages. 

Websites should now be designed and implemented with the WCAG in mind, so including a statement of compliance is redundant information. Indeed this type of statement is of no practical benefit to anyone, unless work is underway on a legacy system (in which case this is helpfull). 

However this information does show commitment to good practises, so I don’t feel it’s a bad thing to have unless the statement is wrong.</description>
		<content:encoded><![CDATA[<p>I’m a BLIND systems programmer and my work includes web development. </p>
<p>As a user of adaptive technology, I don’t tend to go looking for these statements and most of us are aware of the accepted conventions for navigational assistance. </p>
<p>However, new user’s will learn something from help/navigational information as will everyone else, so this should be provided, assumeing it is not redundant. Indeed I feel this information should be part of the more general “about our website” pages as opposed to the “accessibility” pages. </p>
<p>I’ve seen the accessibility statement used to do everything but help users with disabilities, yes most of the information that should be here can just as correctly be put into the “about our website” pages but some things can’t, most notably the list of known accessibility issues and related helpful information as such things would unbalance the help pages. </p>
<p>Websites should now be designed and implemented with the WCAG in mind, so including a statement of compliance is redundant information. Indeed this type of statement is of no practical benefit to anyone, unless work is underway on a legacy system (in which case this is helpfull). </p>
<p>However this information does show commitment to good practises, so I don’t feel it’s a bad thing to have unless the statement is wrong.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike Elledge</title>
		<link>http://www.standards-schmandards.com/2006/just-say-no/comment-page-1/#comment-1079</link>
		<dc:creator>Mike Elledge</dc:creator>
		<pubDate>Fri, 01 Dec 2006 16:08:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.standards-schmandards.com/2006/just-say-no/#comment-1079</guid>
		<description>My two cents: there is no reason why there shouldn&#039;t be both a site map and an accessibility page on a site. They have different intentions. The problem with most accessibility pages is that they are rarely written for the people who need them, i.e., persons using adaptive technology. They can be helpful, if they include information about accesskeys, the presence of headings, skip links and the like, which tell persons using adaptive technology how to navigate through a site more easily.

I think the key is to create greater awareness about how to design effective and meaningful accessibility pages, so they become useful components of websites, rather than puffery. So, I take my hat off to all of you concerned about this issue. Spread the word!</description>
		<content:encoded><![CDATA[<p>My two cents: there is no reason why there shouldn&#8217;t be both a site map and an accessibility page on a site. They have different intentions. The problem with most accessibility pages is that they are rarely written for the people who need them, i.e., persons using adaptive technology. They can be helpful, if they include information about accesskeys, the presence of headings, skip links and the like, which tell persons using adaptive technology how to navigate through a site more easily.</p>
<p>I think the key is to create greater awareness about how to design effective and meaningful accessibility pages, so they become useful components of websites, rather than puffery. So, I take my hat off to all of you concerned about this issue. Spread the word!</p>
]]></content:encoded>
	</item>
</channel>
</rss>

