| Title | Two mandatory password fields with error correction |
|---|---|
| Description | Document containing two password fields ('password' and 'confirm password'). If the user submits and nothing is entered or the entered passwords do not match, the error is identified and presented to the user in text (DOM). |
| Creator | BenToWeb (Reinhard.Ruemer@…) |
| Rights | Copyright BenToWeb 2004-2007 |
| Language | English |
| Date | 2005-08-29 |
| Status | validated |
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)
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 .
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)
The test case is intended to pass, because the input error is specified and presented to the user in text.
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.
Accessibility expert.
“Rules” refer to success criteria in WCAG 2.0, checkpoints in WCAG 1.0 and similar requirements.
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 87, column 41) 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 5) the following success criterion: http://www.w3.org/TR/2007/WD-WCAG20-20070517/Overview.html#minimize-error-identified.
The test case passes (line 88, column 49) the following success criterion: http://www.w3.org/TR/2007/WD-WCAG20-20070517/Overview.html#minimize-error-identified.
The test case passes (line 88, 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 89, 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.
After submission, the error is specified or presented to the user.
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
The test case fails the following success criterion at line 73, 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 74, 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 74, 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 75, 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 75, 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 76, column 76: http://www.w3.org/TR/2006/WD-WCAG20-20060427/guidelines.html#minimize-error-identified.
The test case fails the following success criterion at line 6, column 6: http://www.w3.org/TR/2006/WD-WCAG20-20060427/guidelines.html#minimize-error-identified.
After submission, the error is specified or presented to the user.
Online version: sc2.5.1_l1_030.
The test case fails the following success criterion at line 73, column 9: http://www.w3.org/TR/2006/WD-WCAG20-20050630/#minimize-error-identified.
The test case fails the following success criterion at line 74, column 45: http://www.w3.org/TR/2006/WD-WCAG20-20050630/#minimize-error-identified.
The test case fails the following success criterion at line 74, column 9: http://www.w3.org/TR/2006/WD-WCAG20-20050630/#minimize-error-identified.
The test case fails the following success criterion at line 75, column 53: http://www.w3.org/TR/2006/WD-WCAG20-20050630/#minimize-error-identified.
The test case fails the following success criterion at line 75, column 9: http://www.w3.org/TR/2006/WD-WCAG20-20050630/#minimize-error-identified.
The test case fails the following success criterion at line 76, column 76: http://www.w3.org/TR/2006/WD-WCAG20-20050630/#minimize-error-identified.
The test case fails the following success criterion at line 6, column 6: http://www.w3.org/TR/2006/WD-WCAG20-20050630/#minimize-error-identified.
After submission, the error is specified or presented to the user.