Test Case sc3.3.1_l1_033: Mandatory text input field with error correction (mail address)

Formal Metadata

Formal Metadata
TitleMandatory text input field with error correction (mail address)
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 a mail address with mandatory input. If the user submits and no text is entered or the mail address is invalid, the error is identified and described to the user in text (DOM).
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: 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: script (namespace: http://www.w3.org/1999/xhtml) .

Technical specification: http://www.w3.org/TR/1999/REC-html401-19991224/struct/objects.html#edef-SCRIPT.

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

Technical specification: Intrinsic events: onclick .

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

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

Test Data

Purpose

The test case is intended to pass, because the input error is specified and presented to the user in text.

A valid email address consists of the name of the recipient followed by the @-sign and then followed by a domain adress. For example test@test.org is a valid email address.

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. In Mozilla Firefox, when activating the error links, the focus is not set on the input fields. This is due to the interpretation of Firefox of internal links, which only shifts the focus of the viewport.

Test Modes

Accessibility expert.

Test Files

Test file.

TCDL Data

sc3.3.1_l1_033 (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 86, column 5) the following success criterion: http://www.w3.org/TR/2007/WD-WCAG20-20070517/Overview.html#minimize-error-identified.

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

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

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

Functional Outcome

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

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 G85: Providing a text description when user input falls outside the required format or values.

This test case maps to technique SCR18: Providing client-side validation and alert.

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

Secondary Rules

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

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

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

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

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

Functional Outcome

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

Technical Comment

Online version: sc2.5.1_l1_033.

Secondary Rule (WCAG 2.0 - June 2005 Working Draft)

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

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

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

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

Functional Outcome

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