<?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"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: How Many Blind, Deaf, Cripples Visit Your Website?</title>
	<atom:link href="http://www.fogofeternity.com/2009/11/how-many-blind-deaf-cripples-visit-your-website/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.fogofeternity.com/2009/11/how-many-blind-deaf-cripples-visit-your-website/</link>
	<description>we make great websites</description>
	<lastBuildDate>Mon, 08 Feb 2010 05:41:16 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Robin Cannon</title>
		<link>http://www.fogofeternity.com/2009/11/how-many-blind-deaf-cripples-visit-your-website/comment-page-1/#comment-20150</link>
		<dc:creator>Robin Cannon</dc:creator>
		<pubDate>Tue, 08 Dec 2009 16:15:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.fogofeternity.com/?p=937#comment-20150</guid>
		<description>Definitely. Things like font size changes can really mess up a site. 

It&#039;s not difficult to make an accessible site, because most of it is just good practice. What I&#039;m trying to highlight in the post is how a wider view of accessibility is more important than ticking off boxes. Many designers might ensure that a site can be accessed by screen reader, for example, but while that makes the site accessible to a *tiny* minority of visitors, have the overlooked wider aspects of design and usability?</description>
		<content:encoded><![CDATA[<p>Definitely. Things like font size changes can really mess up a site. </p>
<p>It&#8217;s not difficult to make an accessible site, because most of it is just good practice. What I&#8217;m trying to highlight in the post is how a wider view of accessibility is more important than ticking off boxes. Many designers might ensure that a site can be accessed by screen reader, for example, but while that makes the site accessible to a *tiny* minority of visitors, have the overlooked wider aspects of design and usability?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Griffin</title>
		<link>http://www.fogofeternity.com/2009/11/how-many-blind-deaf-cripples-visit-your-website/comment-page-1/#comment-19978</link>
		<dc:creator>Griffin</dc:creator>
		<pubDate>Fri, 04 Dec 2009 08:55:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.fogofeternity.com/?p=937#comment-19978</guid>
		<description>I make my sites accessible because it&#039;s very fast, easy and increases the likelihood that someone will buy from me (or click ads etc).  For me, double-checking that font increases won&#039;t break the theme (much), and making a screen-reader stylesheet takes almost no time.

You would think that with what I&#039;m selling (websites), it would make even less sense to worry about accessibility, but you&#039;d be surprisingly wrong.  It&#039;s not so much that people use screen readers on my site, but that people increase the font size manually.  Even on major sites, that will break the site&#039;s layout, so it&#039;s important to pay attention to that.</description>
		<content:encoded><![CDATA[<p>I make my sites accessible because it&#8217;s very fast, easy and increases the likelihood that someone will buy from me (or click ads etc).  For me, double-checking that font increases won&#8217;t break the theme (much), and making a screen-reader stylesheet takes almost no time.</p>
<p>You would think that with what I&#8217;m selling (websites), it would make even less sense to worry about accessibility, but you&#8217;d be surprisingly wrong.  It&#8217;s not so much that people use screen readers on my site, but that people increase the font size manually.  Even on major sites, that will break the site&#8217;s layout, so it&#8217;s important to pay attention to that.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
