<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	xmlns:media="http://search.yahoo.com/mrss/"
	>

<channel>
	<title>Accessible Web 2.0</title>
	<atom:link href="http://accessibleweb.wordpress.com/feed/" rel="self" type="application/rss+xml" />
	<link>http://accessibleweb.wordpress.com</link>
	<description>web access for all</description>
	<lastBuildDate>Tue, 03 Feb 2009 06:42:47 +0000</lastBuildDate>
	<generator>http://wordpress.com/</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<cloud domain='accessibleweb.wordpress.com' port='80' path='/?rsscloud=notify' registerProcedure='' protocol='http-post' />
<image>
		<url>http://www.gravatar.com/blavatar/cd41e73387b434e128e747e5c46291bb?s=96&#038;d=http://s.wordpress.com/i/buttonw-com.png</url>
		<title>Accessible Web 2.0</title>
		<link>http://accessibleweb.wordpress.com</link>
	</image>
			<item>
		<title>WCAG 2.0 now live!</title>
		<link>http://accessibleweb.wordpress.com/2009/02/03/wcag-20-now-live/</link>
		<comments>http://accessibleweb.wordpress.com/2009/02/03/wcag-20-now-live/#comments</comments>
		<pubDate>Tue, 03 Feb 2009 06:42:47 +0000</pubDate>
		<dc:creator>accessibleweb</dc:creator>
				<category><![CDATA[WCAG 2.0]]></category>
		<category><![CDATA[accessibility]]></category>
		<category><![CDATA[accessibility guidelines]]></category>

		<guid isPermaLink="false">http://accessibleweb.wordpress.com/?p=7</guid>
		<description><![CDATA[The Web Content Accessibility Guidelines (WCAG) 2.0 became live in December 2008. The full WCAG 2.0 guidelines are available from the W3C website.
The new guidelines are divided into 4 main sections:
1. Perceivable
2. Operable
3. Understandable
4. Robust
Below is a very brief summary of what is included within the 4 WCAG sections.
WCAG 2.0
1. Perceivable
Web content can be seen and heard

1.1 Text alternatives [...]<img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=accessibleweb.wordpress.com&blog=1229125&post=7&subd=accessibleweb&ref=&feed=1" />]]></description>
			<content:encoded><![CDATA[<div class='snap_preview'><br /><p>The Web Content Accessibility Guidelines (WCAG) 2.0 became live in December 2008. The full <a href="http://www.w3.org/TR/WCAG20/">WCAG 2.0 guidelines</a> are available from the W3C website.</p>
<p>The new guidelines are divided into 4 main sections:</p>
<p>1. Perceivable<br />
2. Operable<br />
3. Understandable<br />
4. Robust</p>
<p>Below is a very brief summary of what is included within the 4 WCAG sections.</p>
<p><strong>WCAG 2.0</strong></p>
<p><strong>1. Perceivable</strong><br />
Web content can be seen and heard</p>
<ul>
<li>1.1 Text alternatives &#8211; Alt text for images, labels for form controls, identification of embedded multimedia.</li>
<li>1.2 Time-based Media – Transcript of online audio files (MP3s and podcasts), transcript for web video.  Captions for multimedia files.</li>
<li>1.3 Adaptable – Correct use of headings, tables and lists in the HTML code. Flexibility to change page layout without damaging it’s structure.</li>
<li>1.4 Distinguishable – Contrasting foreground and background colours. Colour is not used as the sole mechanism for displaying content or interaction.</li>
</ul>
<p><strong>2. Operable</strong><br />
The page is operable</p>
<ul>
<li>2.1 Keyboard accessible – The web page can be used via the keyboard</li>
<li>2.2 Enough time – Users have the ability to pause or cancel time based interactions.</li>
<li>2.3 Seizures – No flashing components that may cause a seizure</li>
<li>2.4 Navigable – Skip navigation option, descriptive page titles, clear link text meaning</li>
</ul>
<p><strong>3. Understandable</strong><br />
Page content and interface understandable</p>
<ul>
<li>3.1 Readable – Correct use of the html lang attribute and abbr tag.</li>
<li>3.2 Predictable – Consistent navigation, no major page events (such as pop ups) on changes to focus or interaction</li>
<li>3.3 Input assistance – Identify required fields in a controls label, provide cues or error alerts.</li>
</ul>
<p><strong>4. Robust</strong><br />
Can be used by multiple browsers or devices</p>
<ul>
<li>4.1 Compatible – Validate the pages</li>
</ul>
  <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gocomments/accessibleweb.wordpress.com/7/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/comments/accessibleweb.wordpress.com/7/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/godelicious/accessibleweb.wordpress.com/7/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/delicious/accessibleweb.wordpress.com/7/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gostumble/accessibleweb.wordpress.com/7/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/stumble/accessibleweb.wordpress.com/7/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/godigg/accessibleweb.wordpress.com/7/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/digg/accessibleweb.wordpress.com/7/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/goreddit/accessibleweb.wordpress.com/7/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/reddit/accessibleweb.wordpress.com/7/" /></a> <img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=accessibleweb.wordpress.com&blog=1229125&post=7&subd=accessibleweb&ref=&feed=1" /></div>]]></content:encoded>
			<wfw:commentRss>http://accessibleweb.wordpress.com/2009/02/03/wcag-20-now-live/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
	
		<media:content url="http://1.gravatar.com/avatar/d00a2effcab2318cc4eb4164cf9915d0?s=96&#38;d=identicon" medium="image">
			<media:title type="html">accessibleweb</media:title>
		</media:content>
	</item>
		<item>
		<title>Last Call Working Draft &#8211; Mark II</title>
		<link>http://accessibleweb.wordpress.com/2007/12/14/last-call-working-draft-mark-ii/</link>
		<comments>http://accessibleweb.wordpress.com/2007/12/14/last-call-working-draft-mark-ii/#comments</comments>
		<pubDate>Fri, 14 Dec 2007 17:18:04 +0000</pubDate>
		<dc:creator>accessibleweb</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[WCAG 2.0]]></category>
		<category><![CDATA[Web Accessibility Initiative]]></category>
		<category><![CDATA[guidelines]]></category>
		<category><![CDATA[Candidate Recommendation]]></category>
		<category><![CDATA[Last Call Working Draft]]></category>

		<guid isPermaLink="false">http://accessibleweb.wordpress.com/2007/12/14/last-call-working-draft-mark-ii/</guid>
		<description><![CDATA[The WCAG process gathers pace this week with a new call for review. The Last Call Working Draft represents the 2nd stage in the W3C document process.
Call for Review: WCAG 2.0 Last Call Working Draft
http://lists.w3.org/Archives/Public/w3c-wai-ig/2007OctDec/0060.html
This is the second time the document process has reached the Last Call Working Draft stage. The new deadline for comments is February 2008 and [...]<img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=accessibleweb.wordpress.com&blog=1229125&post=6&subd=accessibleweb&ref=&feed=1" />]]></description>
			<content:encoded><![CDATA[<div class='snap_preview'><br /><p>The WCAG process gathers pace this week with a new call for review. The <strong>Last Call Working Draft</strong> represents the <a href="http://accessibleweb.wordpress.com/2007/08/03/wcag-20-not-available-until-2008/" title="WCAG document process">2nd stage</a> in the W3C document process.</p>
<p><strong>Call for Review: WCAG 2.0 Last Call Working Draft<br />
</strong><a href="http://lists.w3.org/Archives/Public/w3c-wai-ig/2007OctDec/0060.html">http://lists.w3.org/Archives/Public/w3c-wai-ig/2007OctDec/0060.html</a></p>
<p>This is the second time the document process has reached the Last Call Working Draft stage. The new deadline for comments is February 2008 and will deal with the following points:</p>
<ul>
<li>Are the guidelines and Success Criteria clear?</li>
<li>Are the Success Criteria implementable and testable?</li>
<li>Does meeting the Success Criteria improve accessibility?</li>
</ul>
<p>The successful completion of this step will result in the document process reaching the Candidate Recommendation stage.</p>
<img alt="" border="0" src="http://feeds.wordpress.com/1.0/categories/accessibleweb.wordpress.com/6/" /> <img alt="" border="0" src="http://feeds.wordpress.com/1.0/tags/accessibleweb.wordpress.com/6/" /> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gocomments/accessibleweb.wordpress.com/6/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/comments/accessibleweb.wordpress.com/6/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/godelicious/accessibleweb.wordpress.com/6/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/delicious/accessibleweb.wordpress.com/6/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gostumble/accessibleweb.wordpress.com/6/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/stumble/accessibleweb.wordpress.com/6/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/godigg/accessibleweb.wordpress.com/6/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/digg/accessibleweb.wordpress.com/6/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/goreddit/accessibleweb.wordpress.com/6/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/reddit/accessibleweb.wordpress.com/6/" /></a> <img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=accessibleweb.wordpress.com&blog=1229125&post=6&subd=accessibleweb&ref=&feed=1" /></div>]]></content:encoded>
			<wfw:commentRss>http://accessibleweb.wordpress.com/2007/12/14/last-call-working-draft-mark-ii/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
	
		<media:content url="http://1.gravatar.com/avatar/d00a2effcab2318cc4eb4164cf9915d0?s=96&#38;d=identicon" medium="image">
			<media:title type="html">accessibleweb</media:title>
		</media:content>
	</item>
		<item>
		<title>WCAG 2.0 Not available until 2008</title>
		<link>http://accessibleweb.wordpress.com/2007/08/03/wcag-20-not-available-until-2008/</link>
		<comments>http://accessibleweb.wordpress.com/2007/08/03/wcag-20-not-available-until-2008/#comments</comments>
		<pubDate>Fri, 03 Aug 2007 14:14:15 +0000</pubDate>
		<dc:creator>accessibleweb</dc:creator>
				<category><![CDATA[WCAG 2.0]]></category>
		<category><![CDATA[Web Accessibility Initiative]]></category>
		<category><![CDATA[accessibility]]></category>
		<category><![CDATA[accessibility guidelines]]></category>

		<guid isPermaLink="false">http://accessibleweb.wordpress.com/2007/08/03/wcag-20-not-available-until-2008/</guid>
		<description><![CDATA[The Web Content Accessibility Guidelines 2.0 will not be made available this year.
When will WCAG 2.0 be available to use? The Web Accessibility Initiative predicts early 2008.
It had looked as though WCAG 2.0 would be available this year. However, with delays brought on by the W3C document process, the availability of the document has been pushed back.
 The [...]<img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=accessibleweb.wordpress.com&blog=1229125&post=5&subd=accessibleweb&ref=&feed=1" />]]></description>
			<content:encoded><![CDATA[<div class='snap_preview'><br /><p>The Web Content Accessibility Guidelines 2.0 will not be made available this year.</p>
<p><a href="http://www.w3.org/WAI/WCAG20/wcag2faq.html#done" title="When will WCAG 2.0 be done?">When will WCAG 2.0 be available to use?</a> The Web Accessibility Initiative predicts early 2008.</p>
<p>It had looked as though <acronym title="Web Content Accessibility Guidelines">WCAG</acronym> 2.0 would be available this year. However, with delays brought on by the W3C document process, the availability of the document has been pushed back.</p>
<p> The W3C document process comprises a number of stages:</p>
<ol>
<li>Working Draft</li>
<li>Last Call Working Draft</li>
<li>Candidate Recommendation</li>
<li>Proposed Recommendation</li>
<li>W3C Recommendation (Web Standard)</li>
</ol>
<p>In addition to WCAG 2.0, a number of supporting documents are produced, such as &#8220;Working group notes&#8221; and &#8220;<acronym title="Web Accessibility Initiative">WAI</acronym> Resources&#8221;.</p>
<p>Although the supporting documents are not subject to the scrutiny of the W3C document process, they will offer developers the technical know-how required to provide accessible content.</p>
<img alt="" border="0" src="http://feeds.wordpress.com/1.0/categories/accessibleweb.wordpress.com/5/" /> <img alt="" border="0" src="http://feeds.wordpress.com/1.0/tags/accessibleweb.wordpress.com/5/" /> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gocomments/accessibleweb.wordpress.com/5/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/comments/accessibleweb.wordpress.com/5/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/godelicious/accessibleweb.wordpress.com/5/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/delicious/accessibleweb.wordpress.com/5/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gostumble/accessibleweb.wordpress.com/5/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/stumble/accessibleweb.wordpress.com/5/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/godigg/accessibleweb.wordpress.com/5/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/digg/accessibleweb.wordpress.com/5/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/goreddit/accessibleweb.wordpress.com/5/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/reddit/accessibleweb.wordpress.com/5/" /></a> <img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=accessibleweb.wordpress.com&blog=1229125&post=5&subd=accessibleweb&ref=&feed=1" /></div>]]></content:encoded>
			<wfw:commentRss>http://accessibleweb.wordpress.com/2007/08/03/wcag-20-not-available-until-2008/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
	
		<media:content url="http://1.gravatar.com/avatar/d00a2effcab2318cc4eb4164cf9915d0?s=96&#38;d=identicon" medium="image">
			<media:title type="html">accessibleweb</media:title>
		</media:content>
	</item>
		<item>
		<title>How are the Web Content Accessibility Guidelines 2.0 developing?</title>
		<link>http://accessibleweb.wordpress.com/2007/07/04/how-are-the-web-content-accessibility-guidelines-20-developing/</link>
		<comments>http://accessibleweb.wordpress.com/2007/07/04/how-are-the-web-content-accessibility-guidelines-20-developing/#comments</comments>
		<pubDate>Wed, 04 Jul 2007 22:03:35 +0000</pubDate>
		<dc:creator>accessibleweb</dc:creator>
				<category><![CDATA[WCAG 2.0]]></category>
		<category><![CDATA[guidelines]]></category>

		<guid isPermaLink="false">http://accessibleweb.wordpress.com/2007/07/04/how-are-the-web-content-accessibility-guidelines-20-developing/</guid>
		<description><![CDATA[An insight to the development of WCAG 2.0 is provided by Judy Brewer (Director of the Web Accessibility Initiative) during a recent interview.
For developers, some positive observations include the reduction of constraints faced whilst creating accessible content. The provision of support materials will also be welcomed.
For people with disabilities, access to a broader range of web technologies is promised.
Interview extracts [...]<img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=accessibleweb.wordpress.com&blog=1229125&post=4&subd=accessibleweb&ref=&feed=1" />]]></description>
			<content:encoded><![CDATA[<div class='snap_preview'><br /><p>An insight to the development of WCAG 2.0 is provided by <a href="http://www.w3.org/People/Brewer/" title="Judy Brewer">Judy Brewer</a> (Director of the Web Accessibility Initiative) during a recent interview.</p>
<p>For developers, some positive observations include the reduction of constraints faced whilst creating accessible content. The provision of support materials will also be welcomed.</p>
<p>For people with disabilities, access to a broader range of web technologies is promised.</p>
<p>Interview extracts are available from the <a href="http://www.webstandards.org/learn/articles/askw3c/may2007/" title="Interview with Judy Brewer">webstandards.org</a> website.</p>
<img alt="" border="0" src="http://feeds.wordpress.com/1.0/categories/accessibleweb.wordpress.com/4/" /> <img alt="" border="0" src="http://feeds.wordpress.com/1.0/tags/accessibleweb.wordpress.com/4/" /> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gocomments/accessibleweb.wordpress.com/4/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/comments/accessibleweb.wordpress.com/4/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/godelicious/accessibleweb.wordpress.com/4/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/delicious/accessibleweb.wordpress.com/4/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gostumble/accessibleweb.wordpress.com/4/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/stumble/accessibleweb.wordpress.com/4/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/godigg/accessibleweb.wordpress.com/4/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/digg/accessibleweb.wordpress.com/4/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/goreddit/accessibleweb.wordpress.com/4/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/reddit/accessibleweb.wordpress.com/4/" /></a> <img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=accessibleweb.wordpress.com&blog=1229125&post=4&subd=accessibleweb&ref=&feed=1" /></div>]]></content:encoded>
			<wfw:commentRss>http://accessibleweb.wordpress.com/2007/07/04/how-are-the-web-content-accessibility-guidelines-20-developing/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
	
		<media:content url="http://1.gravatar.com/avatar/d00a2effcab2318cc4eb4164cf9915d0?s=96&#38;d=identicon" medium="image">
			<media:title type="html">accessibleweb</media:title>
		</media:content>
	</item>
		<item>
		<title>Accessibility Guidelines 2.0 Working Draft Published</title>
		<link>http://accessibleweb.wordpress.com/2007/06/12/accessibility-guidelines-20-working-draft-published/</link>
		<comments>http://accessibleweb.wordpress.com/2007/06/12/accessibility-guidelines-20-working-draft-published/#comments</comments>
		<pubDate>Tue, 12 Jun 2007 22:46:56 +0000</pubDate>
		<dc:creator>accessibleweb</dc:creator>
				<category><![CDATA[WCAG 2.0]]></category>

		<guid isPermaLink="false">http://accessibleweb.wordpress.com/2007/06/12/accessibility-guidelines-20-working-draft-published/</guid>
		<description><![CDATA[The updated Web Content Accessibility Guidelines 2.0 Working Draft was made available at W3C on May 17th 2007 - http://www.w3.org/TR/WCAG20/
       <img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=accessibleweb.wordpress.com&blog=1229125&post=3&subd=accessibleweb&ref=&feed=1" />]]></description>
			<content:encoded><![CDATA[<div class='snap_preview'><br /><p>The updated Web Content Accessibility Guidelines 2.0 Working Draft was made available at W3C on May 17th 2007 - <a target="_blank" href="http://www.w3.org/TR/WCAG20/">http://www.w3.org/TR/WCAG20/</a></p>
<img alt="" border="0" src="http://feeds.wordpress.com/1.0/categories/accessibleweb.wordpress.com/3/" /> <img alt="" border="0" src="http://feeds.wordpress.com/1.0/tags/accessibleweb.wordpress.com/3/" /> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gocomments/accessibleweb.wordpress.com/3/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/comments/accessibleweb.wordpress.com/3/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/godelicious/accessibleweb.wordpress.com/3/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/delicious/accessibleweb.wordpress.com/3/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gostumble/accessibleweb.wordpress.com/3/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/stumble/accessibleweb.wordpress.com/3/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/godigg/accessibleweb.wordpress.com/3/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/digg/accessibleweb.wordpress.com/3/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/goreddit/accessibleweb.wordpress.com/3/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/reddit/accessibleweb.wordpress.com/3/" /></a> <img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=accessibleweb.wordpress.com&blog=1229125&post=3&subd=accessibleweb&ref=&feed=1" /></div>]]></content:encoded>
			<wfw:commentRss>http://accessibleweb.wordpress.com/2007/06/12/accessibility-guidelines-20-working-draft-published/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
	
		<media:content url="http://1.gravatar.com/avatar/d00a2effcab2318cc4eb4164cf9915d0?s=96&#38;d=identicon" medium="image">
			<media:title type="html">accessibleweb</media:title>
		</media:content>
	</item>
	</channel>
</rss>