RE: Table Headers and Labels

• From: RUST Randal <RRust@COVANSYS.com>
• Date: Wed, 31 Jul 2002 07:43:31 -0400
• To: "'Jukka Korpela'" <jukka.korpela@tieke.fi>, "WAI (E-mail)" <w3c-wai-ig@w3.org>
• Message-ID: <37925254B67DD311876C009027B0FF92027FC58D@cbscolex01.cbsinc.com>

Thanks, Jukka.  This helps clarify a lot of things.  

>I'm afraid I don't quite understand the intended structure. Is 
>your example intended to have really just _one_ row?

No, it would have multiple rows.

>In that case, I wouldn't use a table like that, with column headers;
rather, I'd put each field and the
>associated label on one row, or just on one _line_ (without using a table
at all).

This is essentially what I have decided to do.  Now my markup looks like
this:

		<fieldset>
		<legend>Child Name</legend>
			<div class="row">
				<span class="label">Attendance:</span>
				<label for="childNameAsScheduled">As
Scheduled</label>
				<input type="radio"
id="childNameAsScheduled" name="childNameAttendance" value="s" />
				<label
for="childNameExceptions">Exceptions</label>
				<input type="radio" id="childNameExceptions"
name="childNameAttendance" value="e" />
			</div>
			<div class="row">
				<label for="childNameExceptionCode"><span
class="label">Exception Code:</span></label>
				<select id="childNameExceptionCode">
					<option value="codeID">Code
1</option>
					<option value="codeID">Code
2</option>
				</select>				
			</div>
		</fieldset>

Each child is made distinct by a new FIELDSET with a LEGEND.

Randal

Received on Wednesday, 31 July 2002 07:40:19 UTC