I had to ask around, and the consensus was that they are not compliant. I think that the problem is that anything that changes the focus for the user is frowned upon. I'm not sure if it's a technical one, like the screen-readers would have a problem with it, or if it's a more "general" usability no-no.
I'll try to research it a bit further and let you know (our 508 guru already left), but I my rule of thumb is to steer clear of it. On a side note, I prefer to keep it server side any way, as I have heard figures ranging from 5 to 20 percent of browser have JS disabled. Also, it keeps malicious users from entering bad data, and if they are there to do so, they would most certainly disable all the client side validation. So if you are going to do server side to protect your app/data anyway, why even invest the extra work in JS... My 2 cents. Matthew P. Smith Web Developer, Object Oriented Naval Education & Training Professional Development & Technology Center (NETPDTC) (850)452-1001 ext. 1245 [EMAIL PROTECTED] -----Original Message----- From: Carlisle, Eric [mailto:[EMAIL PROTECTED]] Sent: Friday, December 13, 2002 2:31 PM To: CF-Talk Subject: OT: Form validation & 508 compliancy I realize that sometimes it's better to use client side validation on forms... Sometimes server side... Sometimes both. Are there any rules of thumb to using client side (JavaScript) validation on 508 compliant forms? Thanks :-) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Archives: http://www.houseoffusion.com/cf_lists/index.cfm?forumid=4 Subscription: http://www.houseoffusion.com/cf_lists/index.cfm?method=subscribe&forumid=4 FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Get the mailserver that powers this list at http://www.coolfusion.com
