- From: Scarlett Julian (ED) <Julian.Scarlett@sheffield.gov.uk>
- Date: Mon, 24 Nov 2003 10:24:49 -0000
- To: w3c-wai-ig@w3.org
>> A solution along the same lines might be to have a default
>>radio button
>> labelled 'not answered' and validate the form submission for the
>> ocurrence of these and prompt the respondee to fill them in.
>> Does anyone see any problems with that?
> From a usability stand point, I do, since one is checked no
> matter which one
> it is so it is assumed that it has been chosen when the form
> is submitted.
Form validation would check for the instance of the 'not answered' button and prompt the user to fill in that question. The form could not be submitted unless the user had chosen something other than the initial state. If the user has taken the selection away from the initial state (i.e. made a choice) then the form can be submitted. It's just a hack to get round the potential problem of UA behaviour not being predictable when no button is initially selected and I don't see any major usability problems *if* the question is a mandatory one. Even if the response is optional I think the solution works since the response ('not answered') is still valid. The form validation need only be made on mandatory fields.
--J.
The information in this email is confidential. The contents may not be disclosed or used by anyone other than the addressee. If you are not the addressee, please tell us by using the reply facility in your email software as soon as possible. Sheffield City Council cannot accept any responsibility for the accuracy or completeness of this message as it has been transmitted over a public network. If you suspect that the message may have been intercepted or amended please tell us as soon as possible.
Received on Monday, 24 November 2003 12:32:50 UTC