Hello >From a usability standpoint showing a checkbox that cannot be unchecked renders the checkbox obsolete. The consquence is not to show a checkbox at all. If you need an uncheckable checkbox because of licence aggreements or something like that. Or privacydeclaration type checkbox. Make it checkable but check on the server side if it is checked. If not render an error message to the client telling them why you can't process the form/data because the checkbox is unchecked. That way it is still up to the user to decide what he wants to do. Another alternative is to build a button that has to be pressed to continue which does the same as the checkbox.
The important thing is: 1. Don't take away the users freedom of choice (checking / not checking) 2. Make the user feels he is in control (even though he isn't ;) ) 3. Only put up control elements that actually enable the user to take control Basically all three points are the same. I suggest to read up on usability issues. Just do a google on usability and software. Cause usability is one of the things most of the webprogrammers get wrong... It's not important what your intention is rather what the user intents to do! Please remember this is my opinion so take it or leave it. ;) Regards Stefan
