I think the hardest part for many web developers to grasp, including myself, is how web accessibility is handled in web apps. Just hearing the term "web accessibility" makes it sound like a massive task when it may be as simple as placing text in ALT or TITLE tags. Since I've never coded for this personally, I can't say whats involved but I will be looking further into this as I'm sure that my clients, one day, will be affected by this.
From an Ajax perspective, though, I'm not sure of what the implications are and with the dynamic nature of Ajax-enabled apps, I'm sure that there are additional challenges that we'll face. Rey... Morbus Iff wrote: >>I completely and totally disagree with the court in this case. At what point > > No, your personal blog doesn't need to be accessible because it does not > have a commercial brick and mortar store. Much like government agencies > have to follow accessibility in the real world (and are /required/ to do > the same on the Web with US 508), commercial entities have the same > basic requirements (wheelchair ramp). These laws extending to their > commercial entities on the web is not a huge leap to make. > > >>I just think that we're taking things like this a little too far, IMO. >> >><!----------------//------ >>andy matthews >>web developer >>certified advanced coldfusion programmer >>ICGLink, Inc. >>[EMAIL PROTECTED] >>615.370.1530 x737 >>--------------//---------> > > > It's "<!-- ", not "<!----- ...", and signatures should be four lines > maximum, delimited by "-- \n", not the monstrosity you're using. > _______________________________________________ jQuery mailing list [email protected] http://jquery.com/discuss/
