Test Case sc3.3.1_l1_009: Two mandatory password fields wihout error correction

Formal Metadata

Formal Metadata
TitleTwo mandatory password fields wihout error correction
DescriptionDocument containing two password fields ('password' and 'confirm password'). If the user submits and nothing is entered or the entered passwords do not match, no error is identified and presented to the user in text.
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: div (namespace: http://www.w3.org/1999/xhtml) .

Technical specification: Grouping elements: the DIV and SPAN elements .

Test Data

Purpose

The document is intended to fail, because the input error is not identified and described to the user in text.

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

sc3.3.1_l1_009 (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 at line 14, column 5: http://www.w3.org/TR/2007/WD-WCAG20-20070517/Overview.html#minimize-error-identified.

The test case fails the following success criterion at line 15, column 41: http://www.w3.org/TR/2007/WD-WCAG20-20070517/Overview.html#minimize-error-identified.

The test case fails the following success criterion at line 15, column 5: http://www.w3.org/TR/2007/WD-WCAG20-20070517/Overview.html#minimize-error-identified.

The test case fails the following success criterion at line 16, column 49: http://www.w3.org/TR/2007/WD-WCAG20-20070517/Overview.html#minimize-error-identified.

The test case fails the following success criterion at line 16, column 5: http://www.w3.org/TR/2007/WD-WCAG20-20070517/Overview.html#minimize-error-identified.

Functional Outcome

After submission, the error is not specified or 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 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 fails the following success criterion at line 22, column 9: http://www.w3.org/TR/2006/WD-WCAG20-20060427/guidelines.html#minimize-error-identified.

The test case fails the following success criterion at line 23, column 45: http://www.w3.org/TR/2006/WD-WCAG20-20060427/guidelines.html#minimize-error-identified.

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

The test case fails the following success criterion at line 24, column 53: http://www.w3.org/TR/2006/WD-WCAG20-20060427/guidelines.html#minimize-error-identified.

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

Functional Outcome

After submission, the error is not specified or presented to the user.

Technical Comment

Online version: sc2.5.1_l1_009.

Secondary Rule (WCAG 2.0 - June 2005 Working Draft)

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

The test case fails the following success criterion at line 23, column 45: http://www.w3.org/TR/2006/WD-WCAG20-20050630/#minimize-error-identified.

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

The test case fails the following success criterion at line 24, column 53: http://www.w3.org/TR/2006/WD-WCAG20-20050630/#minimize-error-identified.

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

Functional Outcome

After submission, the error is not specified or presented to the user.