<p>Two of the <a href="http://kosmar.de/wp-content/web20map.png">Web2.0 buzzwords</a> are Accessibility and Usability. They both should be implemented in the websites of this new age of web. Now another buzzword, this one technical: <span class="caps">AJAX</span>. This technique to update only some parts of the website without reloading it all has allowed developers to increase the usability of their websites making them faster and improving the user interface to make them resemble desktop applications.</p>

<p>But at what cost? Most of this websites are not correctly loaded on mobile phones or <i>javascriptless </i> browsers. But there are a few that do the <span class="caps">AJAX</span> degradation well or pick the easy way (my favorite) and create a basic <span class="caps">HTML</span> version. I believe this last one is more effective because the user interface using Javascript with <span class="caps">AJAX</span> has a different structure than simple <span class="caps">HTML</span> and they should be made independently.</p>

<p>But for those who don&#8217;t like making another full website for the minority of browsers, there is now a framework for injecting &#8220;accessibility using <span class="caps">AJAX</span> techniques&#8221;. It&#8217;s called <a href="http://code.google.com/p/google-axsjax/">AxsJAX</a>, it is being opensourced by Google (It is being used on Google Reader) and you can find out more about this on <a href="http://ifacethoughts.net/2007/11/18/ajax-for-accessibility/">ifacethoughts</a>.</p>