Test Case sc3.3.2_l2_002: Log-in page with error detection and suggestions for users

Formal Metadata

Formal Metadata
TitleLog-in page with error detection and suggestions for users
DescriptionDocument containing one text input field for the user name and one password input field for the password. If log-in fails the error is shown and suggestions for correction are provided. (The expected input for the form is: user name = test@test.org; password = test.)
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 .

Test Data

Purpose

The document is intended to pass because if an error is detected suggestions for correction are provided.

Expert Guidance

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. 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_002 (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 17, 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 18, 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 24, 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 25, column 3) the following success criterion: http://www.w3.org/TR/2007/WD-WCAG20-20070517/Overview.html#minimize-error-suggestions.

Functional Outcome

Suggestions for correction are provided to the users.

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 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 47, column 6) the following success criterion: http://www.w3.org/TR/2006/WD-WCAG20-20060427/guidelines.html#minimize-error-suggestions.

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

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

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

Functional Outcome

Suggestions for correction are provided to the users.

Technical Comment

Online version: sc2.5.2_l2_002.

Secondary Rule (WCAG 2.0 - June 2005 Working Draft)

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

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

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

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

Functional Outcome

Suggestions for correction are provided to the users.