<?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/"
	>

<channel>
	<title>Antanova Ltd. &#187; standards</title>
	<atom:link href="http://antanova.com/tags/standards/feed" rel="self" type="application/rss+xml" />
	<link>http://antanova.com</link>
	<description>We make excellent websites</description>
	<lastBuildDate>Tue, 30 Mar 2010 09:08:11 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>WCAG Cheatsheet</title>
		<link>http://antanova.com/blog/accessibility/wcag-cheatsheet</link>
		<comments>http://antanova.com/blog/accessibility/wcag-cheatsheet#comments</comments>
		<pubDate>Mon, 02 Jul 2007 19:41:00 +0000</pubDate>
		<dc:creator>Jason C</dc:creator>
				<category><![CDATA[Accessibility]]></category>
		<category><![CDATA[link]]></category>
		<category><![CDATA[standards]]></category>

		<guid isPermaLink="false">http://antanova.wordpress.com/2007/07/02/wcag-cheatsheet/</guid>
		<description><![CDATA[While making accessible websites is accepted practice by any web devloper worth his or her salt, sometimes we need help identifying exactly how to. The W3C&#8217;s WCAG are here to help us, and our clients.
Trouble is, they&#8217;re quite in-depth and long-winded. Thankfully now, though I found something on my travels that will help me tick [...]]]></description>
			<content:encoded><![CDATA[<p>While making accessible websites is accepted practice by any web devloper worth his or her salt, sometimes we need help identifying exactly how to. The <acronym title="World Wide Web Consortium">W3C</acronym>&#8217;s <acronym title="Web Content Accessibility Guidelines">WCAG</acronym> are here to help us, and our clients.</p>
<p>Trouble is, they&#8217;re quite in-depth and long-winded. Thankfully now, though I found something on my travels that will help me tick as many of the accessibility boxes as possible. Remembering of course that making websites accessible is much more than just  crossing off items from a list.</p>
<p>Here is is: the <a href="http://worksperfectly.net/wcag/">WCAG cheatsheet</a></p>
]]></content:encoded>
			<wfw:commentRss>http://antanova.com/blog/accessibility/wcag-cheatsheet/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
