| Title | No programmatic association between password field and label [new] |
|---|---|
| Description | A document containing a simple form with a text field for an e-mail address, a password field, a reset button and a submit button. The password control has no explicit label (label element); instead, the ‘label’ is provided as a text string positioned before the control.
(The e-mail field uses a label element to provide an explicit label.)
|
| Creator | BenToWeb (Christophe.Strobbe@…) |
| Rights | Copyright BenToWeb 2005-2007 |
| Language | English |
| Date | 2007-08-24 |
| Status | validated |
Technologies are markup languages or data formats. If the technology is a markup language, “features” refers to elements and attributes.
XHTML™ 1.0 The Extensible HyperText Markup Language (Second Edition)
Feature: form
(namespace: http://www.w3.org/1999/xhtml)
.
Technical specification:
The form element
.
Feature: input
(namespace: http://www.w3.org/1999/xhtml)
.
Technical specification:
The input element
.
Feature: input
(namespace: http://www.w3.org/1999/xhtml)
.
Technical specification:
Control types created with input
.
The test case is intended to fail because the association between the password control and its label is not explicit but based on physical location.
Accessibility expert.
“Rules” refer to success criteria in WCAG 2.0, checkpoints in WCAG 1.0 and similar requirements.
The test case fails the following success criterion : http://www.w3.org/TR/2007/WD-WCAG20-20070517/Overview.html#ensure-compat-rsv.
Assistive technology may make an incorrect guess regarding the label of the password control.
This test case maps to failure F68: Failure of SC 1.3.1 and 4.1.2 due to the association of label and user interface controls not being programmatically determinable.