All,
Thank you very much for your responses to my Section 508 question.
They have been most helpful.
Eric
-Original Message-
From: Dave Watts [mailto:[EMAIL PROTECTED]]
Sent: Friday, December 13, 2002 5:25 PM
To: CF-Talk
Subject: RE: Form validation & 508 compliancy
> I reali
> I realize that sometimes it's better to use client side
> validation on forms... Sometimes server side... Sometimes
> both.
Rather than answering your Section 508 question, I'll simply state that you
should always use server-side validation, whether you also use client-side
validation or not.
ment & Technology Center
(NETPDTC)
(850)452-1001 ext. 1245
[EMAIL PROTECTED]
-Original Message-
From: Scott Brady [mailto:[EMAIL PROTECTED]]
Sent: Friday, December 13, 2002 4:15 PM
To: CF-Talk
Subject: RE: Form validation & 508 compliancy
>So if you are going to do server s
>So if you are going to do server side to protect your app/data anyway, why
>even invest the extra work in JS...
Because as a User I prefer client-side validation to save me some trips to the server,
if possible.
For the 90% of users with it enabled, it can be user-friendly.
Of course, you shou
The only issue with JavaScript is whether the feedback from it is readily
available to the user. So a rollover/dropdown menu isn't directly
accessible, but if you have the same links available elsewhere on the page
then you're fine. With client side form validation, you typically put up an
alert bo
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
6 matches
Mail list logo
