Test Case sc2.5.1_l1_025: Mandatory text input field with error correction (date)

Formal Metadata

Formal Metadata
TitleMandatory text input field with error correction (date)
DescriptionDocument containing two mandatory text input fields (first name, last name) that are already filled and set to read-only. In addition, it contains one text input field for entering the date of birth with mandatory input. If the user submits and no date is entered or the date is invalid, the error is identified and described to the user in text below the form (JavaScript).
CreatorBenToWeb (johannes.koch@…)
RightsCopyright BenToWeb 2005-2007
LanguageEnglish
Date2006-12-21
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 .

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

Technical specification: Form element - onclick event .

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 fail, because the input error is specified and presented to the user in text but screenreader users may not notice the error message that is presented below the form.

Expert Guidance

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

sc2.5.1_l1_025 (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: http://www.w3.org/TR/2006/WD-WCAG20-20060427/guidelines.html#minimize-error-identified.

Functional Outcome

Before submission, the error is specified and presented to the user. However, user testing with JAWS and HomePage Reader highlighted the following problem: after submission of the form without a real date, the focus remains on the submit button, so screenreader users may not notice the error message below the form.

Technical Comment

This test case does not map to a WCAG 2.0 technique or failure. (The test case may map to "Providing client-side validation and adding error text via the DOM (future link)" in a future draft.)

Secondary Rules

Secondary Rule (WCAG 2.0 - June 2005 Working Draft)

The test case passes the following success criterion: http://www.w3.org/TR/2006/WD-WCAG20-20050630/#minimize-error-identified.

Functional Outcome

Before submission, the error is specified and presented to the user.