Some resources that might help you, Sudhindra: http://tinyurl.com/6xv6d6 http://xtech06.usefulinc.com/schedule/paper/29 http://webbackplane.com/thought/pbe http://adactio.com/journal/959 http://tinyurl.com/2xtugr http://www.sitepoint.com/article/simply-javascript/ http://tinyurl.com/3sx7jj
Nicholas is right. Accessibility is all about progressive enhancement, and once the proper habits are developed it makes a lot of sense. It's like dressing in layers, each of which can be added or removed as needed. The problem with a lot of rich interaction is that some designers leap forward to the next new technology before building an adequate foundation in HTML and CSS, both of which are simple and straightforward, but also powerful in their own way. They jump right in and build a site that relies heavily on AJAX or Flash, and only later wonder why some people complain that they can't access essential content. The Tower of Babel comes to mind as an apt metaphor. For the sake of accessibility, everything should be done at the lowest possible level. If there's a way to structure and style it appropriately in HTML/CSS, do that first and add the rich interaction later. Otherwise you may find yourself needing to retrofit for accessibility, and that's just as messy as stripping off the icing to rebuild a cake. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Posted from the new ixda.org http://www.ixda.org/discuss?post=32646 ________________________________________________________________ Welcome to the Interaction Design Association (IxDA)! To post to this list ....... [EMAIL PROTECTED] Unsubscribe ................ http://www.ixda.org/unsubscribe List Guidelines ............ http://www.ixda.org/guidelines List Help .................. http://www.ixda.org/help
