Test Case sc3.3.2_l2_004: Text input fields for date with suggestions for correction.

Formal Metadata

Formal Metadata
TitleText input fields for date with suggestions for correction.
DescriptionDocument containing two fields (first name, last name) that are already filled an set to read-only and 3 text input fields for entering the date. If the date is invalid, suggestions for correction are made (JavaScript).
CreatorBenToWeb (Reinhard.Ruemer@…)
RightsCopyright BenToWeb 2004-2007
LanguageEnglish
Date2005-08-29
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: onclick (namespace: http://www.w3.org/1999/xhtml) .

Technical specification: Input element - onclick event .

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 .

Standard ECMA-262 : ECMAScript Language Specification, 3rd edition (December 1999)

Standard ECMA-262 : ECMAScript Language Specification, 3rd edition (December 1999)

Test Data

Purpose

The document is intended to pass because suggestions for corrections are provided.

Expert Guidance

Javascript must be enabled for the test files to work as intended. For the design of accessible forms it is particularly important to verify appropriateness with assistive technologies like screen readers and ensure proper navigation for users who can access the form by keyboard only. Therefore the expert user is advised to evaluate the form also in this respect. Beyond this it should be mentioned that in order to ensure accessibility of a form presented on a website, it might be necessary to validate the design by the target user group.

Test Modes

Accessibility expert.

Test Files

Test file.

TCDL Data

sc3.3.2_l2_004 (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 (line 126, column 7) the following success criterion: http://www.w3.org/TR/2007/WD-WCAG20-20070517/Overview.html#minimize-error-suggestions.

The test case passes (line 128, column 3) the following success criterion: http://www.w3.org/TR/2007/WD-WCAG20-20070517/Overview.html#minimize-error-suggestions.

The test case passes (line 126, column 36) the following success criterion: http://www.w3.org/TR/2007/WD-WCAG20-20070517/Overview.html#minimize-error-suggestions.

The test case passes (line 129, column 6) the following success criterion: http://www.w3.org/TR/2007/WD-WCAG20-20070517/Overview.html#minimize-error-suggestions.

The test case passes (line 126, column 64) the following success criterion: http://www.w3.org/TR/2007/WD-WCAG20-20070517/Overview.html#minimize-error-suggestions.

The test case passes (line 130, column 6) the following success criterion: http://www.w3.org/TR/2007/WD-WCAG20-20070517/Overview.html#minimize-error-suggestions.

The test case passes (line 131, column 58) the following success criterion: http://www.w3.org/TR/2007/WD-WCAG20-20070517/Overview.html#minimize-error-suggestions.

Functional Outcome

User is provided with suggestions for correcting the error.

Technical Comment

This test case maps to technique G83: Providing text descriptions to identify required fields that were not completed

This test case maps to technique G84: Providing a text description when the user provides information that is not in the list of allowed values

This test case maps to technique G85: Providing a text description when user input falls outside the required format or values

This test case maps to technique G139: Creating a mechanism that allows users to jump to errors

This test case maps to technique SCR18: Providing client-side validation and alert (Scripting)

Secondary Rules

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

The test case passes (line 126, column 14) the following success criterion: http://www.w3.org/TR/2006/WD-WCAG20-20060427/guidelines.html#minimize-error-suggestions.

The test case passes (line 128, column 10) the following success criterion: http://www.w3.org/TR/2006/WD-WCAG20-20060427/guidelines.html#minimize-error-suggestions.

The test case passes (line 129, column 10) the following success criterion: http://www.w3.org/TR/2006/WD-WCAG20-20060427/guidelines.html#minimize-error-suggestions.

The test case passes (line 130, column 10) the following success criterion: http://www.w3.org/TR/2006/WD-WCAG20-20060427/guidelines.html#minimize-error-suggestions.

The test case passes (line 131, column 64) the following success criterion: http://www.w3.org/TR/2006/WD-WCAG20-20060427/guidelines.html#minimize-error-suggestions.

Functional Outcome

User is provided with suggestions for correcting the error.

Technical Comment

Online version: sc2.5.2_l2_004.

Secondary Rule (WCAG 2.0 - June 2005 Working Draft)

The test case passes (line 126, column 14) the following success criterion: http://www.w3.org/TR/2006/WD-WCAG20-20050630/#minimize-error-suggestions.

The test case passes (line 128, column 10) the following success criterion: http://www.w3.org/TR/2006/WD-WCAG20-20050630/#minimize-error-suggestions.

The test case passes (line 129, column 10) the following success criterion: http://www.w3.org/TR/2006/WD-WCAG20-20050630/#minimize-error-suggestions.

The test case passes (line 130, column 10) the following success criterion: http://www.w3.org/TR/2006/WD-WCAG20-20050630/#minimize-error-suggestions.

The test case passes (line 131, column 64) the following success criterion: http://www.w3.org/TR/2006/WD-WCAG20-20050630/#minimize-error-suggestions.

Functional Outcome

User is provided with suggestions for correcting the error.