Understanding Accessibility

Guideline 10. Use interim solutions.

Checkpoint 10.2 - Until user agents support explicit associations between labels and form controls, for all form controls with implicitly associated labels, ensure that the label is properly positioned

How do I do it?

Give each form element a label - this makes it easier for motor impaired people to select it as it increases the selection area.

html

<tr>
<td>
<label for="email"> Email Address:</label></td>
<td><input name="email" type="text" id="email" size="40"></td>
</tr>

Xhtml

<tr>
<td>
<label for="email"> Email Address:</label></td>
<td><input name="email" type="text" id="email" size="40" /></td>
</tr>

Labels for forms which are not correctly placed can be confusing for screen reader users, as they may not know which label is associated with which form element. Labels should appear on the same or preceding line to the element.

More information on how to add labels to different form elements is available at http://www.ilikecake.net/html/html_10_forms.htm

How do I check that it meets the WCAG criteria?

Pages which have form elements must be checked manually for compliance. Where pages do not comply with the above, they will be deemed to have failed the check. This check does not require that the label be explicitly associated with the form element (for example, using the ‘for’ attribute).

guideline 1 - 2 - 3 - 4 - 5 - 6 - 7 - 8 - 9 - 10 - 11 - 12 - 13 - 14