<?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: What if we didn&#8217;t lump all &#8220;accessibility&#8221; requirements together?</title>
	<atom:link href="http://ajaxian.com/archives/what-if-we-didnt-lump-all-accessibility-requirements-together/feed" rel="self" type="application/rss+xml" />
	<link>http://ajaxian.com/archives/what-if-we-didnt-lump-all-accessibility-requirements-together</link>
	<description>Cleaning up the web with Ajax</description>
	<lastBuildDate>Thu, 17 May 2012 07:43:39 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
	<item>
		<title>By: Joeri</title>
		<link>http://ajaxian.com/archives/what-if-we-didnt-lump-all-accessibility-requirements-together/comment-page-1#comment-267571</link>
		<dc:creator>Joeri</dc:creator>
		<pubDate>Mon, 22 Sep 2008 12:35:30 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/?p=4561#comment-267571</guid>
		<description>I think it&#039;s inevitable that you build more than one front-end to cater to different markets. Building a single front-end that scales from a low-end cell phone all the way to a full-blown desktop-equivalent ajax interface is pretty much impossible, either purely from a technical POV, or from a cost/benefit POV.
.
Looking at gmail they have at least 4 different front-ends: standard (and standard + chat), basic, html mobile, and java mobile.
.
Each of these is tuned to a particular audience. I think that approach makes the most sense.</description>
		<content:encoded><![CDATA[<p>I think it&#8217;s inevitable that you build more than one front-end to cater to different markets. Building a single front-end that scales from a low-end cell phone all the way to a full-blown desktop-equivalent ajax interface is pretty much impossible, either purely from a technical POV, or from a cost/benefit POV.<br />
.<br />
Looking at gmail they have at least 4 different front-ends: standard (and standard + chat), basic, html mobile, and java mobile.<br />
.<br />
Each of these is tuned to a particular audience. I think that approach makes the most sense.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

