<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.1" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Today&#8217;s AJAX and DHTML Best Practices</title>
	<link>http://www.access-matters.com/2006/10/09/todays-ajax-and-dhtml-best-practices/</link>
	<description>Seeking Best Accessibility Practices</description>
	<pubDate>Mon, 12 May 2008 22:16:20 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.1</generator>

	<item>
		<title>By: dotjay</title>
		<link>http://www.access-matters.com/2006/10/09/todays-ajax-and-dhtml-best-practices/#comment-7956</link>
		<author>dotjay</author>
		<pubDate>Wed, 11 Oct 2006 13:31:20 +0000</pubDate>
		<guid>http://www.access-matters.com/2006/10/09/todays-ajax-and-dhtml-best-practices/#comment-7956</guid>
					<description>What we need then, is some lovely big company to take on board the ideas we have and try to build a degradable system.

I can't see inaccessible AJAX going away, so could an Accessible DHTML system be built on top of a traditional accessible application, perhaps degrading to inaccessible AJAX functionality if Accessible DHTML is not available (all but Firefox?)...

Even then, if AJAX sits on top of a traditional accessible application, then providing an option for users to switch off AJAX functionality should maintain accessibility.</description>
		<content:encoded><![CDATA[<p>What we need then, is some lovely big company to take on board the ideas we have and try to build a degradable system.</p>
<p>I can&#8217;t see inaccessible AJAX going away, so could an Accessible DHTML system be built on top of a traditional accessible application, perhaps degrading to inaccessible AJAX functionality if Accessible DHTML is not available (all but Firefox?)&#8230;</p>
<p>Even then, if AJAX sits on top of a traditional accessible application, then providing an option for users to switch off AJAX functionality should maintain accessibility.</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: John Foliot</title>
		<link>http://www.access-matters.com/2006/10/09/todays-ajax-and-dhtml-best-practices/#comment-7987</link>
		<author>John Foliot</author>
		<pubDate>Thu, 12 Oct 2006 01:44:01 +0000</pubDate>
		<guid>http://www.access-matters.com/2006/10/09/todays-ajax-and-dhtml-best-practices/#comment-7987</guid>
					<description>Too scary... we obviously were reading minds, as we both posted on the same day on the same subject.  I've "upped" you by 8 articles [grin] in: "10 "Must Read" articles on AJAX, Accessibility and Web 2 technology (Plus 3 more for some light at the end of the tunnel relief...)": &lt;a href="http://soap.stanford.edu/show.php?contentid=65" rel="nofollow"&gt;http://soap.stanford.edu/show.php?contentid=65&lt;/a&gt;

While I agree that access for the visually impaired user is effectively a good benchmark, readers should also consider that the absolute reliance on JavaScript creates an issue that can impact on all users, as the &lt;a href="http://soap.stanford.edu/show.php?contentid=65#ajax2" rel="nofollow"&gt;second cautionary article&lt;/a&gt; in my piece aptly illustrates. 

I look forward to reading your suggestions and Best Practices in your up-coming series.

JF</description>
		<content:encoded><![CDATA[<p>Too scary&#8230; we obviously were reading minds, as we both posted on the same day on the same subject.  I&#8217;ve &#8220;upped&#8221; you by 8 articles [grin] in: &#8220;10 &#8220;Must Read&#8221; articles on AJAX, Accessibility and Web 2 technology (Plus 3 more for some light at the end of the tunnel relief&#8230;)&#8221;: <a href="http://soap.stanford.edu/show.php?contentid=65" rel="nofollow">http://soap.stanford.edu/show.php?contentid=65</a></p>
<p>While I agree that access for the visually impaired user is effectively a good benchmark, readers should also consider that the absolute reliance on JavaScript creates an issue that can impact on all users, as the <a href="http://soap.stanford.edu/show.php?contentid=65#ajax2" rel="nofollow">second cautionary article</a> in my piece aptly illustrates. </p>
<p>I look forward to reading your suggestions and Best Practices in your up-coming series.</p>
<p>JF</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Ajaxian &#187; Accessible Ajax Best Practices</title>
		<link>http://www.access-matters.com/2006/10/09/todays-ajax-and-dhtml-best-practices/#comment-8021</link>
		<author>Ajaxian &#187; Accessible Ajax Best Practices</author>
		<pubDate>Thu, 12 Oct 2006 15:01:17 +0000</pubDate>
		<guid>http://www.access-matters.com/2006/10/09/todays-ajax-and-dhtml-best-practices/#comment-8021</guid>
					<description>[...] Access Matters has wrapped up an article on Today’s AJAX and DHTML Best Practices:  This article builds a sturdy three legged stool which we can stand upon to see farther. Before getting started, I want to set the stage by defining a benchmark. Accessibility’s worst case scenarios are for blind people. The blind are the hardest to accommodate. Some might think that too much attention is paid the blind when there are so many other disabilities, let alone so many more people when the wide range is counted, but the facts are that the others are easier to accommodate. Ensuring good access for the blind is the hardest challenge and therefore the benchmark. [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] Access Matters has wrapped up an article on Today’s AJAX and DHTML Best Practices:  This article builds a sturdy three legged stool which we can stand upon to see farther. Before getting started, I want to set the stage by defining a benchmark. Accessibility’s worst case scenarios are for blind people. The blind are the hardest to accommodate. Some might think that too much attention is paid the blind when there are so many other disabilities, let alone so many more people when the wide range is counted, but the facts are that the others are easier to accommodate. Ensuring good access for the blind is the hardest challenge and therefore the benchmark. [&#8230;]</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: links for 2006-10-13 at Blue Sky On Mars</title>
		<link>http://www.access-matters.com/2006/10/09/todays-ajax-and-dhtml-best-practices/#comment-8071</link>
		<author>links for 2006-10-13 at Blue Sky On Mars</author>
		<pubDate>Fri, 13 Oct 2006 09:23:33 +0000</pubDate>
		<guid>http://www.access-matters.com/2006/10/09/todays-ajax-and-dhtml-best-practices/#comment-8071</guid>
					<description>[...] Access Matters » Blog Archive » Today’s AJAX and DHTML Best Practices (tags: accessibility AJAX javascript webdesign) [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] Access Matters » Blog Archive » Today’s AJAX and DHTML Best Practices (tags: accessibility AJAX javascript webdesign) [&#8230;]</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Diko</title>
		<link>http://www.access-matters.com/2006/10/09/todays-ajax-and-dhtml-best-practices/#comment-8091</link>
		<author>Diko</author>
		<pubDate>Fri, 13 Oct 2006 17:10:26 +0000</pubDate>
		<guid>http://www.access-matters.com/2006/10/09/todays-ajax-and-dhtml-best-practices/#comment-8091</guid>
					<description>I'd love to see this article on eioba.com</description>
		<content:encoded><![CDATA[<p>I&#8217;d love to see this article on eioba.com</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Blogging Web 2.0 Technology &#124; Learning &#124; Networking Tips &#124; Web Design &#124; Information Website SEO &#187; Today’s AJAX and DHTML Best Practices</title>
		<link>http://www.access-matters.com/2006/10/09/todays-ajax-and-dhtml-best-practices/#comment-8112</link>
		<author>Blogging Web 2.0 Technology &#124; Learning &#124; Networking Tips &#124; Web Design &#124; Information Website SEO &#187; Today’s AJAX and DHTML Best Practices</author>
		<pubDate>Fri, 13 Oct 2006 22:06:10 +0000</pubDate>
		<guid>http://www.access-matters.com/2006/10/09/todays-ajax-and-dhtml-best-practices/#comment-8112</guid>
					<description>[...] http://www.access-matters.com/2006/10/09/todays-ajax-and-dhtml-best-practices/ [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] <a href="http://www.access-matters.com/2006/10/09/todays-ajax-and-dhtml-best-practices/" rel="nofollow">http://www.access-matters.com/2006/10/09/todays-ajax-and-dhtml-best-practices/</a> [&#8230;]</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Accessible Ajax Best Practices &#171; Orta Çağ</title>
		<link>http://www.access-matters.com/2006/10/09/todays-ajax-and-dhtml-best-practices/#comment-8124</link>
		<author>Accessible Ajax Best Practices &#171; Orta Çağ</author>
		<pubDate>Sat, 14 Oct 2006 03:12:49 +0000</pubDate>
		<guid>http://www.access-matters.com/2006/10/09/todays-ajax-and-dhtml-best-practices/#comment-8124</guid>
					<description>[...] Access Matters has wrapped up an article on Today’s AJAX and DHTML Best Practices: This article builds a sturdy three legged stool which we can stand upon to see farther. Before getting started, I want to set the stage by defining a benchmark. Accessibility’s worst case scenarios are for blind people. The blind are the hardest to accommodate. Some might think that too much attention is paid the blind when there are so many other disabilities, let alone so many more people when the wide range is counted, but the facts are that the others are easier to accommodate. Ensuring good access for the blind is the hardest challenge and therefore the benchmark. [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] Access Matters has wrapped up an article on Today’s AJAX and DHTML Best Practices: This article builds a sturdy three legged stool which we can stand upon to see farther. Before getting started, I want to set the stage by defining a benchmark. Accessibility’s worst case scenarios are for blind people. The blind are the hardest to accommodate. Some might think that too much attention is paid the blind when there are so many other disabilities, let alone so many more people when the wide range is counted, but the facts are that the others are easier to accommodate. Ensuring good access for the blind is the hardest challenge and therefore the benchmark. [&#8230;]</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: nortypig</title>
		<link>http://www.access-matters.com/2006/10/09/todays-ajax-and-dhtml-best-practices/#comment-8313</link>
		<author>nortypig</author>
		<pubDate>Tue, 17 Oct 2006 21:47:55 +0000</pubDate>
		<guid>http://www.access-matters.com/2006/10/09/todays-ajax-and-dhtml-best-practices/#comment-8313</guid>
					<description>This looks to be another interesting series of articles, although I am a bit wary of AJAX simply because people have shown such bad form with JavaScript all on its lonesome to date. A real estate portal recently posted about the wonders of AJAX in its upcoming new design with drag and drop this and that - which really, to my uneducated eye, sounded like reboxed DHTML done badly with the justification of a buzzword.

I think in the end we need to use the same criteria as always and if techniques can be developed to degrade well for non JS users, work on older screen readers (how many pensioners out there can afford the latest Jaws for example), then great stuff and I'll look at using it in solutions.

Also, while the blind may be a benchmark, I'm not entirely sold on any solution which may benefit them at the expense of other groups. It will be interesting to follow the series and find ways around some of these issues though. Nice article, especially the Leg 3 part, while technologies are changing slowly its about getting things working now to make AJAX a viable accessible solution. Which is really common sense.</description>
		<content:encoded><![CDATA[<p>This looks to be another interesting series of articles, although I am a bit wary of AJAX simply because people have shown such bad form with JavaScript all on its lonesome to date. A real estate portal recently posted about the wonders of AJAX in its upcoming new design with drag and drop this and that - which really, to my uneducated eye, sounded like reboxed DHTML done badly with the justification of a buzzword.</p>
<p>I think in the end we need to use the same criteria as always and if techniques can be developed to degrade well for non JS users, work on older screen readers (how many pensioners out there can afford the latest Jaws for example), then great stuff and I&#8217;ll look at using it in solutions.</p>
<p>Also, while the blind may be a benchmark, I&#8217;m not entirely sold on any solution which may benefit them at the expense of other groups. It will be interesting to follow the series and find ways around some of these issues though. Nice article, especially the Leg 3 part, while technologies are changing slowly its about getting things working now to make AJAX a viable accessible solution. Which is really common sense.</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Access Matters &#187; Blog Archive &#187; Quiz: AJAX - automatically move focus?</title>
		<link>http://www.access-matters.com/2006/10/09/todays-ajax-and-dhtml-best-practices/#comment-8909</link>
		<author>Access Matters &#187; Blog Archive &#187; Quiz: AJAX - automatically move focus?</author>
		<pubDate>Wed, 25 Oct 2006 11:40:39 +0000</pubDate>
		<guid>http://www.access-matters.com/2006/10/09/todays-ajax-and-dhtml-best-practices/#comment-8909</guid>
					<description>[...] Three articles came to light in &#8220;Today&#8217;s AJAX and DHTML Best Practices.&#8221; Two of the articles went to some length to find ways to move focus as part of an AJAX event. They sought to take the visitor from the trigger event to the results in one smooth, easy move. For those of us who are sighted, we are all familiar with &#8220;the yellow fade&#8221; that catches our eye and focuses our attention on the element that has changed or is changing. Should we do the same for users of assistive technology? Should we try to get the screen readers to jump to the updated content? Both Gez and James attempted exactly that in their articles, with varying degrees of success. On the other hand, Becky advised against trying to move focus. Do not automatically shift focus on the page when an update occurs. Changing focus without warning can be distracting for some users, especially if there is no easy mechanism to return to the previous position. [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] Three articles came to light in &#8220;Today&#8217;s AJAX and DHTML Best Practices.&#8221; Two of the articles went to some length to find ways to move focus as part of an AJAX event. They sought to take the visitor from the trigger event to the results in one smooth, easy move. For those of us who are sighted, we are all familiar with &#8220;the yellow fade&#8221; that catches our eye and focuses our attention on the element that has changed or is changing. Should we do the same for users of assistive technology? Should we try to get the screen readers to jump to the updated content? Both Gez and James attempted exactly that in their articles, with varying degrees of success. On the other hand, Becky advised against trying to move focus. Do not automatically shift focus on the page when an update occurs. Changing focus without warning can be distracting for some users, especially if there is no easy mechanism to return to the previous position. [&#8230;]</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: çeviri</title>
		<link>http://www.access-matters.com/2006/10/09/todays-ajax-and-dhtml-best-practices/#comment-47443</link>
		<author>çeviri</author>
		<pubDate>Sun, 08 Jul 2007 22:05:05 +0000</pubDate>
		<guid>http://www.access-matters.com/2006/10/09/todays-ajax-and-dhtml-best-practices/#comment-47443</guid>
					<description>Access Matters » Blog Archive » Today’s AJAX and DHTML Best Practices (tags: accessibility AJAX javascript webdesign)</description>
		<content:encoded><![CDATA[<p>Access Matters » Blog Archive » Today’s AJAX and DHTML Best Practices (tags: accessibility AJAX javascript webdesign)</p>
]]></content:encoded>
				</item>
</channel>
</rss>
