<?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; Accessibility</title>
	<atom:link href="http://antanova.com/category/blog/accessibility/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>I ordered the sauce</title>
		<link>http://antanova.com/blog/accessibility/i-ordered-the-sauce</link>
		<comments>http://antanova.com/blog/accessibility/i-ordered-the-sauce#comments</comments>
		<pubDate>Tue, 05 Feb 2008 14:50:00 +0000</pubDate>
		<dc:creator>Jason C</dc:creator>
				<category><![CDATA[Accessibility]]></category>
		<category><![CDATA[client]]></category>
		<category><![CDATA[html]]></category>

		<guid isPermaLink="false">http://antanova.wordpress.com/2008/02/05/i-ordered-the-sauce/</guid>
		<description><![CDATA[Having just deployed the latest release of design agency Outburst’s website, I was again thinking about the order of source in html, and how I would put the content first in that site. I could use absolute positioning, but I don’t think that would work in cases where the font size had been increased by [...]]]></description>
			<content:encoded><![CDATA[<p>Having just deployed the latest release of design agency <a href="http://www.outburstcreative.com/">Outburst</a>’s website, I was again thinking about the order of source in html, and how I would put the content first in that site. I could use absolute positioning, but I don’t think that would work in cases where the font size had been increased by the user, or where the user’s display has a resolution greater than the default 96 dpi.</p>
<p>In a spare moment, I did a quick search and found an old but pretty <a href="http://www.usability.com.au/resources/ozewai2005/">informative presentation</a> and <a href="http://www.usability.com.au/resources/source-order.cfm">article</a> on exactly that, where they’d done a little bit of user testing. It’s so hard to find that kind of hard information I thought I’d pop a link up here.</p>
<p><a href="http://www.usability.com.au/resources/ozewai2005/">http://www.usability.com.au/resources/ozewai2005/</a></p>
]]></content:encoded>
			<wfw:commentRss>http://antanova.com/blog/accessibility/i-ordered-the-sauce/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<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>
		<item>
		<title>Blooming marvellous</title>
		<link>http://antanova.com/blog/accessibility/blooming-marvellous</link>
		<comments>http://antanova.com/blog/accessibility/blooming-marvellous#comments</comments>
		<pubDate>Thu, 21 Sep 2006 08:50:00 +0000</pubDate>
		<dc:creator>Jason C</dc:creator>
				<category><![CDATA[Accessibility]]></category>

		<guid isPermaLink="false">http://antanova.wordpress.com/2006/09/21/blooming-marvellous/</guid>
		<description><![CDATA[At last, the BSI has seen sense, and will hopefully help clear the muddy waters of website accessibility. I mentioned in my earlier post “Accessibility&#8230; for a price” that there were guidelines for website commissioners called “PAS78”, but that the only way to obtain them was to buy them. Now, like some rare bloom that [...]]]></description>
			<content:encoded><![CDATA[<p>At last, the BSI has seen sense, and will hopefully help clear the muddy waters of website accessibility. I mentioned in my earlier post “<a href="http://antanova.blogspot.com/2006/03/accessibility-for-price.html">Accessibility&#8230; for a price</a>” that there were guidelines for website commissioners called “PAS78”, but that the only way to obtain them was to buy them. Now, like some rare bloom that flowers once a decade, sense has blossomed and <a href="http://www.drc-gb.org/library/website_accessibility_guidance/pas_78.aspx">the guidelines are available to download</a> for free.</p>
<p>So I&#8217;m going to sip the sweet nectar. Stick around and I&#8217;ll let you know how it tastes.</p>
]]></content:encoded>
			<wfw:commentRss>http://antanova.com/blog/accessibility/blooming-marvellous/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Accessibility&#8230; for a price</title>
		<link>http://antanova.com/blog/accessibility/accessibility-for-a-price</link>
		<comments>http://antanova.com/blog/accessibility/accessibility-for-a-price#comments</comments>
		<pubDate>Thu, 16 Mar 2006 18:13:00 +0000</pubDate>
		<dc:creator>Jason C</dc:creator>
				<category><![CDATA[Accessibility]]></category>

		<guid isPermaLink="false">http://antanova.wordpress.com/2006/03/16/accessibility-for-a-price/</guid>
		<description><![CDATA[First the good news: the RNIB in conjunction with the BSI have released new guidelines (called PAS 78) to help website commissioners and developers make their sites accessible. Which is a Very Good Thing.
So, I know what you&#8217;re thinking. &#8220;Where can I get it?&#8221; &#8220;What&#8217;s the URL?&#8221;. You can&#8217;t! You just can&#8217;t! They&#8217;re making accessibility [...]]]></description>
			<content:encoded><![CDATA[<p>First the good news: the <a href="http://www.rnib.org.uk/">RNIB</a> in conjunction with the <a href="http://www.bsi-global.com/">BSI</a> have released <a href="http://www.rnib.org.uk/xpedio/groups/public/documents/publicwebsite/public_pr080306.hcsp">new guidelines</a> (called PAS 78) to help website commissioners and developers make their sites accessible. Which is a Very Good Thing.</p>
<p>So, I know what you&#8217;re thinking. &#8220;Where can I get it?&#8221; &#8220;What&#8217;s the URL?&#8221;. You can&#8217;t! You just can&#8217;t! They&#8217;re making accessibility guidelines &#8220;inaccessible&#8221;. You have to <a href="http://www.bsi-global.com/ICT/PAS78/index.xalter">buy them</a> for £30 from BSI. And that&#8217;s BS, if you ask me.</p>
<p>Come on guys, do everyone a favour and release them on your site. For nothing. Everyone needs to see those guidelines. Remember, the web&#8217;s not just built by professionals. So help guide all the amateurs and make the web a more accessible place for <em>everyone</em>.</p>
]]></content:encoded>
			<wfw:commentRss>http://antanova.com/blog/accessibility/accessibility-for-a-price/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
