<?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: The Web Standards Curriculum from Opera</title>
	<atom:link href="http://www.rnib.org.uk/wacblog/news/the-web-standards-curriculum-from-opera/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.rnib.org.uk/wacblog/news/the-web-standards-curriculum-from-opera/</link>
	<description></description>
	<pubDate>Thu,  4 Dec 2008 18:09:25 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5</generator>
		<item>
		<title>By: Chris Mills</title>
		<link>http://www.rnib.org.uk/wacblog/news/the-web-standards-curriculum-from-opera/#comment-84971</link>
		<dc:creator>Chris Mills</dc:creator>
		<pubDate>Tue, 08 Jul 2008 13:32:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.rnib.org.uk/wacblog/?p=190#comment-84971</guid>
		<description>@KLewis - ah ha! This is a good spot ;-)

Well, what can I say? I have tried my hardest to make accesibility inherent throughout all the articles, and later on (they'll be released in the next article batch around the end of July) I'm including 2 accesibility articles that explain rather nicely the other factors behind accessibility. I'd put them up now, but I'm still waiting for a couple of the linking articles that come before them.</description>
		<content:encoded><![CDATA[<p>@KLewis - ah ha! This is a good spot ;-)</p>
<p>Well, what can I say? I have tried my hardest to make accesibility inherent throughout all the articles, and later on (they&#8217;ll be released in the next article batch around the end of July) I&#8217;m including 2 accesibility articles that explain rather nicely the other factors behind accessibility. I&#8217;d put them up now, but I&#8217;m still waiting for a couple of the linking articles that come before them.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: KLewis</title>
		<link>http://www.rnib.org.uk/wacblog/news/the-web-standards-curriculum-from-opera/#comment-84970</link>
		<dc:creator>KLewis</dc:creator>
		<pubDate>Tue, 08 Jul 2008 13:20:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.rnib.org.uk/wacblog/?p=190#comment-84970</guid>
		<description>It looks like a great resource and I plan to have a thorough look. The introduction is full of suitably enthusiastic language but it makes one sweeping statement that is relevant to accessibility: 

Essentially is says that by using web standards "you’ll be able to make your web sites usable by this significant group of the web audience with no extra effort."

This just reinforces a myth I often am confronted with that code is all that matters in accessibility. Presumably there's an opportunity to feedback on the site. Maybe it's a clever hook to get people reading :-)</description>
		<content:encoded><![CDATA[<p>It looks like a great resource and I plan to have a thorough look. The introduction is full of suitably enthusiastic language but it makes one sweeping statement that is relevant to accessibility: </p>
<p>Essentially is says that by using web standards &#8220;you’ll be able to make your web sites usable by this significant group of the web audience with no extra effort.&#8221;</p>
<p>This just reinforces a myth I often am confronted with that code is all that matters in accessibility. Presumably there&#8217;s an opportunity to feedback on the site. Maybe it&#8217;s a clever hook to get people reading :-)</p>
]]></content:encoded>
	</item>
</channel>
</rss>
