W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > July to September 2002

RE: Accessible forms in XHTML

From: Andrew Johns <andrew.johns@jkd.co.uk>
Date: Wed, 17 Jul 2002 12:54:43 +0100
Message-ID: <FDFC0668A850D246BC4231715D94904E266C3B@uranus.jkd.co.uk>
To: <w3c-wai-ig@w3.org>

ah, yes, I KNEW there was a logical reason for it!! I remember coming across a similar problem, but I'd completely forgotten about it :D

Yes, this is likely to affect any situation where you want to return an array of results, whether it's radio buttons, checkboxes, etc, they all need to have the same name, which will cause problems with the <label for=""> and id attribute combination.  This would be for both javascript and for any server-side work scripting where you are expecting a comma-seperated string based on the user's selections.

That's cleared that up, but now your example leads me onto another question! :D

You use the following example:

<p>Are You Working?</p>

<label for="workingYes">Yes</label>
<input type="radio" id="workingYes" name="working" value="y" />

<label for="workingNo">No</label>
<input type="radio" id="workingNo" name="working" value="n" />

Is this acceptable to an AAA rating? I have used fieldset and legend when using radio and checkboxes, and then used styles to remove the borders, background colours, padding, margin, etc, so it looks reasonably close to the original.  I'm sure my CSS (and for that matter the fieldset and legend tags) probably fails in some browser or another, but overall this method seems more accessible IMO than the one you used?


Received on Wednesday, 17 July 2002 07:54:45 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:36:10 UTC