I think it’s worth noting that adding AJAX capabilities, whether it involves writing javascript, using ICEFaces, using BINDOWS, etc., if you’re developing software for the federal and/or most state governments and even civilian/commercial firms, the fancy AJAX capabilities can render your program unacceptable at best and in violation of the law at worst
http://www.901am.com/2007/court-rules-against-target-on-website-accessibility-lawsuit.html
http://www.dralegal.org/cases/private_business/nfb_v_target.php
I suspect the cost to Target to fix their software was pretty extensive.
Don’t get me wrong, I’m crazy about all the AJAX capability I can get my hands on, but be cautious, know what you’re developing and who you’re developing it for from the outset. It’s much easier to grow a 508 compliant system than it is to convert a non-compliant system.
I’m also sympathetic to the the visually andhearing impaired.
I’ve written the ICEFaces people and they responded quickly that 508 compliance is at the forefront of their thinking. They have a couple of spreadsheets (which I didn’t fully grasp) that outline what parts of ICEFace will and will not pass muster in the 508 world. If you’re developing 508 compliant software and want to know what parts of ICEFaces you can use now, and what is planned for the future, I’d get over to http://www.icefaces.org pronto.