Comments on: Accessibility and Ajax: Progressive enhancement vs. side-by-side UIs http://www.pathf.com/blogs/2007/10/accessibility-a/ Running commentary about agile development, user experience design and Ajax. Mon, 01 Dec 2008 22:42:58 +0000 http://wordpress.org/?v=2.5.1 By: David Bolter http://www.pathf.com/blogs/2007/10/accessibility-a/#comment-276 David Bolter Thu, 11 Oct 2007 01:07:31 +0000 http://www.pathf.com/blogs/?p=228#comment-276 <p>Accessibility is being built into dojo; leveraging the new ARIA specification housed at the w3c. I think building accessibility into the toolkits and frameworks is a good start.</p> <p><a href="http://www.dojotoolkit.org/" rel="nofollow">http://www.dojotoolkit.org/</a></p> Accessibility is being built into dojo; leveraging the new ARIA specification housed at the w3c. I think building accessibility into the toolkits and frameworks is a good start.

http://www.dojotoolkit.org/

]]> By: bex http://www.pathf.com/blogs/2007/10/accessibility-a/#comment-275 bex Wed, 10 Oct 2007 21:44:16 +0000 http://www.pathf.com/blogs/?p=228#comment-275 <p>There's another option... Firevox. Its a Firefox based screen reader, which can probably fix a huge number of AJAX accessibility problems. More info:</p> <p><a href="http://bexhuff.com/2007/09/firevox-briging-accesibility-to-web-2-0" rel="nofollow">http://bexhuff.com/2007/09/firevox-briging-accesibility-to-web-2-0</a></p> There’s another option… Firevox. Its a Firefox based screen reader, which can probably fix a huge number of AJAX accessibility problems. More info:

http://bexhuff.com/2007/09/firevox-briging-accesibility-to-web-2-0

]]>