<?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.0 - where to start?</title>
	<atom:link href="http://www.rnib.org.uk/wacblog/wcag/wcag-20-where-to-start/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.rnib.org.uk/wacblog/wcag/wcag-20-where-to-start/</link>
	<description></description>
	<pubDate>Wed, 20 Aug 2008 13:19:06 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5</generator>
		<item>
		<title>By: Web Access Centre Blog :: &#8220;What’s new, WCAG 2.0, and current issues&#8221; by Shawn Henry from W3C WAI</title>
		<link>http://www.rnib.org.uk/wacblog/wcag/wcag-20-where-to-start/#comment-37679</link>
		<dc:creator>Web Access Centre Blog :: &#8220;What’s new, WCAG 2.0, and current issues&#8221; by Shawn Henry from W3C WAI</dc:creator>
		<pubDate>Thu, 27 Sep 2007 05:55:54 +0000</pubDate>
		<guid isPermaLink="false">http://www.rnib.org.uk/wacblog/wcag/wcag-20-where-to-start/#comment-37679</guid>
		<description>[...] (The other thing is, I just like seeing my name and Henny’s name together, isn’t it fun: Shawn Henry Henny Swan We’re working together on co-editing a document on how to transition your website from WCAG 1.0 to 2.0, and you might’ve seen Henny’s recent blog that’s related to that issue. So it’s fun just to see our names together on that.) [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] (The other thing is, I just like seeing my name and Henny’s name together, isn’t it fun: Shawn Henry Henny Swan We’re working together on co-editing a document on how to transition your website from WCAG 1.0 to 2.0, and you might’ve seen Henny’s recent blog that’s related to that issue. So it’s fun just to see our names together on that.) [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Henny</title>
		<link>http://www.rnib.org.uk/wacblog/wcag/wcag-20-where-to-start/#comment-25538</link>
		<dc:creator>Henny</dc:creator>
		<pubDate>Thu, 31 May 2007 10:41:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.rnib.org.uk/wacblog/wcag/wcag-20-where-to-start/#comment-25538</guid>
		<description>Thanks for letting us know that the summary of changes to WCAG 2.0 is now available Gregg. This is going to be very helpful when reviewing this draft and providing feedback.

I like the addition of "Check the sections you want to include on the page" when customising the  Quick Reference document too. It helps you really distill the page down when you want to just focus on specific areas such as techniques.</description>
		<content:encoded><![CDATA[<p>Thanks for letting us know that the summary of changes to WCAG 2.0 is now available Gregg. This is going to be very helpful when reviewing this draft and providing feedback.</p>
<p>I like the addition of &#8220;Check the sections you want to include on the page&#8221; when customising the  Quick Reference document too. It helps you really distill the page down when you want to just focus on specific areas such as techniques.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gregg Vanderheiden</title>
		<link>http://www.rnib.org.uk/wacblog/wcag/wcag-20-where-to-start/#comment-25484</link>
		<dc:creator>Gregg Vanderheiden</dc:creator>
		<pubDate>Thu, 31 May 2007 05:35:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.rnib.org.uk/wacblog/wcag/wcag-20-where-to-start/#comment-25484</guid>
		<description>A couple of documents that are helpful in getting started at looking over the newest draft

1)  A document that highlights the changes in WCAG 2.0 along with context is now available.  It is at http://www.w3.org/WAI/GL/2007/05/change-summary

The major overall changes are discussed up front along with rationale.  Then it goes through each success criterion that has changed and lists the changes.



2) The improved  Quick Reference now allows you more flexibility for including just the information you would like.

Use the customization feature at the top to have only the information you would like shown.  The Quick Reference will vary in length from just  3 pages on up depending on how much information you want included.   

http://www.w3.org/WAI/WCAG20/quickref/</description>
		<content:encoded><![CDATA[<p>A couple of documents that are helpful in getting started at looking over the newest draft</p>
<p>1)  A document that highlights the changes in WCAG 2.0 along with context is now available.  It is at <a href="http://www.w3.org/WAI/GL/2007/05/change-summary" rel="nofollow">http://www.w3.org/WAI/GL/2007/05/change-summary</a></p>
<p>The major overall changes are discussed up front along with rationale.  Then it goes through each success criterion that has changed and lists the changes.</p>
<p>2) The improved  Quick Reference now allows you more flexibility for including just the information you would like.</p>
<p>Use the customization feature at the top to have only the information you would like shown.  The Quick Reference will vary in length from just  3 pages on up depending on how much information you want included.   </p>
<p><a href="http://www.w3.org/WAI/WCAG20/quickref/" rel="nofollow">http://www.w3.org/WAI/WCAG20/quickref/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Henny</title>
		<link>http://www.rnib.org.uk/wacblog/wcag/wcag-20-where-to-start/#comment-24717</link>
		<dc:creator>Henny</dc:creator>
		<pubDate>Wed, 23 May 2007 10:28:59 +0000</pubDate>
		<guid isPermaLink="false">http://www.rnib.org.uk/wacblog/wcag/wcag-20-where-to-start/#comment-24717</guid>
		<description>Thanks for the feedback and glad you found the article useful. Sounds like you're pretty familiar with the revised WCAG 2.0 so if you also have any tips to share then go ahead!

I agree with you in that it looks like the WCAG WG have taken on board comments from last year and acted on them which is great. It's a lot simpler to follow now that wording has been revised and the concepts reviewed. I wonder if the degree of complexity that remains is something that is, to an extent, part and parcel of writing guidelines which do have to have a level of formality whatever the topic or content. The planned Application Notes from WAI should mitigate against confusion over hyperlinking. As I understand it, the Application Notes will be written so that it's topic based.  

At the time of writing I don't think there are any published lists for Accessibility Support of Web Technologies but I believe that WAI encourage people and organisations to publish and share their own based on criteria that have provided. This is written about in the &lt;a href="http://www.w3.org/WAI/GL/WCAG20/#conformance" rel="nofollow"&gt;conformance section of WCAG 2.0&lt;/a&gt;.</description>
		<content:encoded><![CDATA[<p>Thanks for the feedback and glad you found the article useful. Sounds like you&#8217;re pretty familiar with the revised WCAG 2.0 so if you also have any tips to share then go ahead!</p>
<p>I agree with you in that it looks like the WCAG WG have taken on board comments from last year and acted on them which is great. It&#8217;s a lot simpler to follow now that wording has been revised and the concepts reviewed. I wonder if the degree of complexity that remains is something that is, to an extent, part and parcel of writing guidelines which do have to have a level of formality whatever the topic or content. The planned Application Notes from WAI should mitigate against confusion over hyperlinking. As I understand it, the Application Notes will be written so that it&#8217;s topic based.  </p>
<p>At the time of writing I don&#8217;t think there are any published lists for Accessibility Support of Web Technologies but I believe that WAI encourage people and organisations to publish and share their own based on criteria that have provided. This is written about in the <a href="http://www.w3.org/WAI/GL/WCAG20/#conformance" rel="nofollow">conformance section of WCAG 2.0</a>.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: KLewis</title>
		<link>http://www.rnib.org.uk/wacblog/wcag/wcag-20-where-to-start/#comment-24607</link>
		<dc:creator>KLewis</dc:creator>
		<pubDate>Mon, 21 May 2007 15:43:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.rnib.org.uk/wacblog/wcag/wcag-20-where-to-start/#comment-24607</guid>
		<description>Great article. Very useful. I agree that there is a lot of good guidance in there. It's good to see some key changes have been made.

Replacing baselines is probably a good idea but the replacement is seemingly incomplete (no published lists) and most likely incomprehensible to many! With so much good, clear advice on how to meet the success criteria I'm surprised that this part is so messy. In fact I'm convinced it is just baselines under another name. It doesn't help that W3C insist on making every other word a hyperlink (how to remember where you've been?) so maybe I missed the idiots guide...?</description>
		<content:encoded><![CDATA[<p>Great article. Very useful. I agree that there is a lot of good guidance in there. It&#8217;s good to see some key changes have been made.</p>
<p>Replacing baselines is probably a good idea but the replacement is seemingly incomplete (no published lists) and most likely incomprehensible to many! With so much good, clear advice on how to meet the success criteria I&#8217;m surprised that this part is so messy. In fact I&#8217;m convinced it is just baselines under another name. It doesn&#8217;t help that W3C insist on making every other word a hyperlink (how to remember where you&#8217;ve been?) so maybe I missed the idiots guide&#8230;?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
