Test Case sc4.1.2_l1_201: Name, role and value for text input and radio buttons [new]

Formal Metadata

Formal Metadata
TitleName, role and value for text input and radio buttons [new]
DescriptionA document containing a simple form with a text input field and a set of radio buttons. The text input field has a label. The radio buttons have labels and are grouped in a fieldset that has a legend. All the user interface components are created with standard XHTML without scripting.
CreatorBenToWeb (Christophe.Strobbe@…)
RightsCopyright BenToWeb 2005-2007
LanguageEnglish
Date2007-08-24
Statusvalidated

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: 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: label (namespace: http://www.w3.org/1999/xhtml) .

Technical specification: The label element .

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

Technical specification: Adding structure to forms: the fieldset and legend elements .

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

Technical specification: Adding structure to forms: the fieldset and legend elements .

Cascading Style Sheets, level 2: CSS2 Specification

Cascading Style Sheets, level 2: CSS2 Specification

Test Data

Purpose

The test case is intended to pass because the proper markup for input fields, labels and fieldsets is used so that the name, role and value of each user interface component can be determined.

Test Modes

Automatic evaluation.

Test Files

Test file.

TCDL Data

sc4.1.2_l1_201 (XML).

Rules

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

Primary Rules

The test case passes the following success criterion: http://www.w3.org/TR/2007/WD-WCAG20-20070517/Overview.html#ensure-compat-rsv.

Functional Outcome

Users of assistive technology can determine the name, role and value of each user interface component.

Technical Comment

This test case maps to technique G108: Using markup features to expose the name and role, allow user-settable properties to be directly set, and provide notification of changes and to technique H44: Using label elements to associate text labels with form controls.