Test Case sc1.3.1_l1_040: Password field with visually positioned label (no explicit label)

Formal Metadata

Formal Metadata
TitlePassword field with visually positioned label (no explicit label)
DescriptionA document with a simple form that contains only a password field. Next to the input is the label element for the field; there is no explicit association between input and label by means of for and id attributes.
CreatorBenToWeb (evlach@…)
RightsCopyright BenToWeb 2004-2007
LanguageEnglish
Date2005-08-29
Statusaccepted QA

Technologies and Features

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)

XHTML™ 1.0 The Extensible HyperText Markup Language (Second Edition)

Feature: input (namespace: http://www.w3.org/1999/xhtml) .

Technical specification: The input element .

Feature: label (namespace: http://www.w3.org/1999/xhtml) .

Technical specification: The label element .

Test Data

Purpose

The test case is intended to fail because the association between label and input is based on visual proximity instead of being explicit.

Test Modes

Automatic evaluation.

Test Files

Test file.

TCDL Data

sc1.3.1_l1_040 (XML).

Rules

“Rules” refer to success criteria in WCAG 2.0, checkpoints in WCAG 1.0 and similar requirements.

Primary Rules

The test case fails the following success criterion at line 11, column 1: http://www.w3.org/TR/2007/WD-WCAG20-20070517/Overview.html#content-structure-separation-programmatic.

The test case fails the following success criterion at line 12, column 48: http://www.w3.org/TR/2007/WD-WCAG20-20070517/Overview.html#content-structure-separation-programmatic.

Functional Outcome

Assistive technology will need to determine the assocation between input and label on the basis of visual proximity.

Technical Comment

The input element has no explicitly associated label.

The 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.

Secondary Rules

Secondary Rule (WCAG 2.0 - April 2006 Working Draft (Last Call))

The test case fails the following success criterion at line 11, column 45: http://www.w3.org/TR/2006/WD-WCAG20-20060427/guidelines.html#content-structure-separation-programmatic.

The test case fails the following success criterion at line 12, column 48: http://www.w3.org/TR/2006/WD-WCAG20-20060427/guidelines.html#content-structure-separation-programmatic.

Functional Outcome

Assistive technology will need to determine the assocation between input and label on the basis of visual proximity.

Technical Comment

The input element has no explicitly associated label.

Online version: sc1.3.1_l1_040.

Secondary Rule (WCAG 2.0 - June 2005 Working Draft)

The test case fails the following success criterion at line 11, column 45: http://www.w3.org/TR/2006/WD-WCAG20-20050630/#content-structure-separation-programmatic.

The test case fails the following success criterion at line 12, column 48: http://www.w3.org/TR/2006/WD-WCAG20-20050630/#content-structure-separation-programmatic.

Functional Outcome

Assistive technology will need to determine the assocation between input and label on the basis of visual proximity.

Technical Comment

The input element has no explicitly associated label.