<?xml version="1.0" encoding="utf-8" ?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
	<title>Design&gt;Web Design&gt;Accessibility&gt;Ajax</title>	<link>http://tc.eserver.org/dir/Design/Web-Design/Accessibility/Ajax</link>
	<description>A listing of the most recently indexed works about Design and Web Design and Accessibility and Ajax in the field of technical communication.</description>
	<language>en-us</language>
	<copyright>Copyright (c) 2005-08 by the EServer. All rights reserved.</copyright>
	<managingEditor>tclib-editorial@eserver.org (TC Library Editorial Board)</managingEditor>
	<webMaster>webmaster@eserver.org (Geoffrey Sauer)</webMaster>
	<image>
		<url>http://tc.eserver.org/images/newlogo.gif</url>
		<title>Design&gt;Web Design&gt;Accessibility&gt;Ajax</title>
		<link>http://tc.eserver.org/dir/Design/Web-Design/Accessibility/Ajax</link>
	</image>
	<item>
		<title>AJAX Aids Accessibility?</title>
		<link>http://tc.eserver.org/33853.html</link>
		<guid>http://tc.eserver.org/33853.html</guid>
		<description>Yes, if you do it right, using Ajax techniques can improve accessibility. Surprised? You shouldn’t be. Ajax is like most techniques and technologies on the web—they are what you make of them.</description>
	</item>
	<item>
		<title>Stop Using Ajax!</title>
		<link>http://tc.eserver.org/32527.html</link>
		<guid>http://tc.eserver.org/32527.html</guid>
		<description>We got things like browser wars, browser-specific DHTML, and table-based layouts. These were things that got in the way of the original vision, because people wanted rich content when the technology wasn’t ready. And now it’s happening again.</description>
	</item>
	<item>
		<title>AJAX Accessibility for Websites</title>
		<link>http://tc.eserver.org/31058.html</link>
		<guid>http://tc.eserver.org/31058.html</guid>
		<description>Discover the accessibility problems caused by AJAX and how it can be used to enhance web accessibility.</description>
	</item>
	<item>
		<title>The AxsJAX Framework for ARIA</title>
		<link>http://tc.eserver.org/30471.html</link>
		<guid>http://tc.eserver.org/30471.html</guid>
		<description>Charles L. Chen  and T. V Raman have developed a common JavaScript framework to enhance the accessibility of AJAX-based applications. The framework is called AxsJAX, pronounced, &apos;Access JAX.&apos;</description>
	</item>
	<item>
		<title>Accessible Web 2.0 Applications with WAI-ARIA</title>
		<link>http://tc.eserver.org/28701.html</link>
		<guid>http://tc.eserver.org/28701.html</guid>
		<description>Our web applications can suffer from inaccessibility problems due to inherent markup limitations. Martin Kliehm helps us sort through the WAI specs for Accessible Rich Internet Applications (ARIA) to increase usability.</description>
	</item>
	<item>
		<title>Making Ajax Work with Screen Readers</title>
		<link>http://tc.eserver.org/27670.html</link>
		<guid>http://tc.eserver.org/27670.html</guid>
		<description>The accessibility community is understandably concerned about the accessibility of client-side scripting, in particular using Asynchronous JavaScript and XML (Ajax) to produce Rich Internet Applications. Steve Faulkner of Vision Australia  and founder member of the Web Accessibility Tools Consortium  (WAT-C) and myself on behalf of The Paciello Group (TPG)  have collaborated in an effort to come up with techniques to make Ajax and other client-side scripting techniques accessible to assistive technology.</description>
	</item>
	<item>
		<title>AJAX and Screenreaders: When Can it Work?</title>
		<link>http://tc.eserver.org/27408.html</link>
		<guid>http://tc.eserver.org/27408.html</guid>
		<description>We&apos;ve all heard a great deal of buzz about AJAX in the last few months, and with this talk has come a legion of articles, tips, presentations and practical APIs designed to explore the possibilities and try to arrive at best-practice techniques. But, for all of the excitement and hype, still very little has been said on the subject of AJAX and accessibility.</description>
	</item>
	<item>
		<title>Accessibility of AJAX Applications</title>
		<link>http://tc.eserver.org/26788.html</link>
		<guid>http://tc.eserver.org/26788.html</guid>
		<description>AJAX is a smorgasbord of web technologies put together to allow dynamic client-server interactions to occur in web applications without requiring pages to reload or refresh. AJAX stands for Asynchronous JavaScript And XML. AJAX itself is not a technology--it is a combination of technologies used in a certain way.</description>
	</item>
	<item>
		<title>Usability and Accessibility with AJAX</title>
		<link>http://tc.eserver.org/26789.html</link>
		<guid>http://tc.eserver.org/26789.html</guid>
		<description>The Ajax express train rumbles on, threatening to crush anything in its path. Recent discussion has turned to those critical elements of good web development, usability and accessibility. Accessibility is a major issue with Ajax, mainly because anything that relies on JavaScript to function is inaccessible pretty much by default. There are two solutions: either provide a fall-back system where the site remains useful without its Ajax enhancements, or provide a whole separate interface that works without scripting.</description>
	</item>
	<atom:link href="http://tc.eserver.org/dir/Design/Web-Design/Accessibility/Ajax.xml" rel="self" type="application/rss+xml"/>
</channel>
</rss>