<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.0.4" -->
<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>Fri, 12 Mar 2010 05:04:07 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0.4</generator>

	<item>
		<title>by: tatil otelleri</title>
		<link>http://www.access-matters.com/2006/10/09/todays-ajax-and-dhtml-best-practices/#comment-184846</link>
		<pubDate>Sat, 06 Mar 2010 13:51:35 +0000</pubDate>
		<guid>http://www.access-matters.com/2006/10/09/todays-ajax-and-dhtml-best-practices/#comment-184846</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>
	<item>
		<title>by: Bob Easton</title>
		<link>http://www.access-matters.com/2006/10/09/todays-ajax-and-dhtml-best-practices/#comment-164882</link>
		<pubDate>Tue, 21 Oct 2008 22:34:45 +0000</pubDate>
		<guid>http://www.access-matters.com/2006/10/09/todays-ajax-and-dhtml-best-practices/#comment-164882</guid>
					<description>blacklight,
You missed the point. This blog is about making things accessible for people with disabilities.

1.) How can a blind person use a drag and drop dialog? If you can't see a mouse pointer, how do you use it?

2.) How can a person who is incapable of using a mouse operate a drag and drop dialog? Is there a keyboard interface to your wonderful script?

You probably didn't THINK much before deciding to use this blog to advertise your work.</description>
		<content:encoded><![CDATA[<p>blacklight,<br />
You missed the point. This blog is about making things accessible for people with disabilities.</p>
<p>1.) How can a blind person use a drag and drop dialog? If you can&#8217;t see a mouse pointer, how do you use it?</p>
<p>2.) How can a person who is incapable of using a mouse operate a drag and drop dialog? Is there a keyboard interface to your wonderful script?</p>
<p>You probably didn&#8217;t THINK much before deciding to use this blog to advertise your work.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: blacklight</title>
		<link>http://www.access-matters.com/2006/10/09/todays-ajax-and-dhtml-best-practices/#comment-163668</link>
		<pubDate>Thu, 16 Oct 2008 04:18:48 +0000</pubDate>
		<guid>http://www.access-matters.com/2006/10/09/todays-ajax-and-dhtml-best-practices/#comment-163668</guid>
					<description>One of the strengths of javascript is the way it can be functional (think c) and object oriented (c++) at the same time.  It also treats every object and its members as a key/value associative array (think hash or map).  It is great to use in debugging, because you can iterate through all the members of an object.

A good example of that is this &lt;a href='http://zedwood.com/article/104/javascript_-_drag_and_drop_dialog_box' rel="nofollow"&gt;Drag and Drop DHTML Dialog&lt;/a&gt;.  Its pretty cool.  It is a total crowse-browser compatible drag and drop interface.  An example is given with a simple dialog box.  But it is written in object oriented javascript, which makes easy to reuse (namespace collisions etc).
---------------------------------------------------</description>
		<content:encoded><![CDATA[<p>One of the strengths of javascript is the way it can be functional (think c) and object oriented (c++) at the same time.  It also treats every object and its members as a key/value associative array (think hash or map).  It is great to use in debugging, because you can iterate through all the members of an object.</p>
<p>A good example of that is this <a href='http://zedwood.com/article/104/javascript_-_drag_and_drop_dialog_box' rel="nofollow">Drag and Drop DHTML Dialog</a>.  Its pretty cool.  It is a total crowse-browser compatible drag and drop interface.  An example is given with a simple dialog box.  But it is written in object oriented javascript, which makes easy to reuse (namespace collisions etc).<br />
&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;
</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>
		<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>
	<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>
		<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: nortypig</title>
		<link>http://www.access-matters.com/2006/10/09/todays-ajax-and-dhtml-best-practices/#comment-8313</link>
		<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: 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>
		<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: 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>
		<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: Diko</title>
		<link>http://www.access-matters.com/2006/10/09/todays-ajax-and-dhtml-best-practices/#comment-8091</link>
		<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: 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>
		<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>
</channel>
</rss>
