>Remote scripting's been around, but GMaps and Garrett's >article >whacked the mainstream designers over the head. AJAX >can stand for >whatever acronym you want. When designers say "AJAX", >they mean rich >interaction and a broken page request/response model >broken.
Actually AJAX can be done defensively quite easily: first code against standard HTML, build all your interaction on standard form/link methaphors, only then start to add better interactivity by adding AJAX features. It's not necessarily broken accessibility, it's mostly broken because people don't care to do the first step before the second ;-) But yes, it's something that can be seen in most texts about AJAX. And that's rather sad, because if people who write introductory texts don't even care for accessibility, all the work done to make designers aware of accessibility will go down the drain if AJAX hit's the market. On the other hand, there _are_ regulatories to enforce accessibility on web sites, so one can still hope that after the first highs on AJAX people will come back to sane minds and start to combine both. It's not really that hard, but it helps people with disabilities to still make use of your website ... bye, Georg
