| Title | Log-in page without error detection and suggestions for users |
|---|---|
| Description | Document containing one text input field for the user name and one password input field for the password. If log-in fails no error is shown. |
| 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 .
The document is intended to fail, because errors are not detected and no suggestions for correction are provided to the users.
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.
The expected input for the example form is: user name = test@test.org; password = test.
Accessibility expert.
“Rules” refer to success criteria in WCAG 2.0, checkpoints in WCAG 1.0 and similar requirements.
The test case fails the following success criterion at line 15, column 2: http://www.w3.org/TR/2007/WD-WCAG20-20070517/Overview.html#minimize-error-suggestions.
The test case fails the following success criterion at line 15, column 38: http://www.w3.org/TR/2007/WD-WCAG20-20070517/Overview.html#minimize-error-suggestions.
The test case fails the following success criterion at line 16, column 2: http://www.w3.org/TR/2007/WD-WCAG20-20070517/Overview.html#minimize-error-suggestions.
The test case fails the following success criterion at line 16, column 37: http://www.w3.org/TR/2007/WD-WCAG20-20070517/Overview.html#minimize-error-suggestions.
The error is not described to the user and no suggestions are provided.
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
The test case fails the following success criterion at line 21, column 6: http://www.w3.org/TR/2006/WD-WCAG20-20060427/guidelines.html#minimize-error-suggestions.
The test case fails the following success criterion at line 21, column 40: http://www.w3.org/TR/2006/WD-WCAG20-20060427/guidelines.html#minimize-error-suggestions.
The test case fails the following success criterion at line 22, column 6: http://www.w3.org/TR/2006/WD-WCAG20-20060427/guidelines.html#minimize-error-suggestions.
The test case fails the following success criterion at line 22, column 40: http://www.w3.org/TR/2006/WD-WCAG20-20060427/guidelines.html#minimize-error-suggestions.
The error is not described to the user and no suggestions are provided.
Online version: sc2.5.2_l2_001.
The test case fails the following success criterion at line 21, column 6: http://www.w3.org/TR/2006/WD-WCAG20-20050630/#minimize-error-suggestions.
The test case fails the following success criterion at line 21, column 40: http://www.w3.org/TR/2006/WD-WCAG20-20050630/#minimize-error-suggestions.
The test case fails the following success criterion at line 22, column 6: http://www.w3.org/TR/2006/WD-WCAG20-20050630/#minimize-error-suggestions.
The test case fails the following success criterion at line 22, column 40: http://www.w3.org/TR/2006/WD-WCAG20-20050630/#minimize-error-suggestions.
An error is not detected and no suggestions are provided.