<?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"
	>
<channel>
	<title>Comments on: WCAG 2 Requirements at Risk</title>
	<atom:link href="http://www.sitepoint.com/blogs/2008/05/04/wcag-2-requirements-at-risk/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.sitepoint.com/blogs/2008/05/04/wcag-2-requirements-at-risk/</link>
	<description></description>
	<pubDate>Mon, 08 Sep 2008 04:04:52 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5</generator>
		<item>
		<title>By: Ricky Onsman</title>
		<link>http://www.sitepoint.com/blogs/2008/05/04/wcag-2-requirements-at-risk/#comment-719539</link>
		<dc:creator>Ricky Onsman</dc:creator>
		<pubDate>Sat, 10 May 2008 04:24:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/?p=2463#comment-719539</guid>
		<description>I've been looking at the At Risk requirements over the past week or so and I'm going to have a shot at implementing as many as I can (I have a prospective project that might be particularly suitable), but I wonder whether many people get why it matters.

After all, if 1.2.6 becomes Advisory, doesn't it just mean that either no-one cares or it's impractical? Or maybe that text equivalents do the job better than sign language? Bear in mind that you don't then have to worry about &lt;em&gt;which&lt;/em&gt; sign language to use, let alone the technical difficulties of applying sign language interpretations to existing video and then &lt;strong&gt;how&lt;/strong&gt; to stick them on a web page.

I suspect that, like many aspects of accessibility in life, a lot of people see these kind of requirements as PC-gone-mad, catering to every tiny minority, bleeding heart, small l-liberal, etc etc.

Maybe we need to help people to understand why this matters to everyone. 

Then maybe the really clever ones can rise to the challenge of making the web truly accessible, to the point where universal access is simply taken for granted. Maybe we'll even have the web set an example that the rest of the perceived world can follow.

I'll be posting stuff here as I can, and I hope this can be one place where we can offer some practical ideas on how and why.</description>
		<content:encoded><![CDATA[<p>I&#8217;ve been looking at the At Risk requirements over the past week or so and I&#8217;m going to have a shot at implementing as many as I can (I have a prospective project that might be particularly suitable), but I wonder whether many people get why it matters.</p>
<p>After all, if 1.2.6 becomes Advisory, doesn&#8217;t it just mean that either no-one cares or it&#8217;s impractical? Or maybe that text equivalents do the job better than sign language? Bear in mind that you don&#8217;t then have to worry about <em>which</em> sign language to use, let alone the technical difficulties of applying sign language interpretations to existing video and then <strong>how</strong> to stick them on a web page.</p>
<p>I suspect that, like many aspects of accessibility in life, a lot of people see these kind of requirements as PC-gone-mad, catering to every tiny minority, bleeding heart, small l-liberal, etc etc.</p>
<p>Maybe we need to help people to understand why this matters to everyone. </p>
<p>Then maybe the really clever ones can rise to the challenge of making the web truly accessible, to the point where universal access is simply taken for granted. Maybe we&#8217;ll even have the web set an example that the rest of the perceived world can follow.</p>
<p>I&#8217;ll be posting stuff here as I can, and I hope this can be one place where we can offer some practical ideas on how and why.</p>]]></content:encoded>
	</item>
</channel>
</rss>
