| Title | Mandatory text input field with error correction |
|---|---|
| Description | Document containing three mandatory text input fields. The first two fields (first name, last name) are already filled and set to read-only. The user is asked to fill the third field (customer code). If the user submits and no text is entered, the error is identified and presented to the user in text (DOM). |
| Creator | BenToWeb (Daniela.Ortner@…) |
| Rights | Copyright BenToWeb 2005-2007 |
| Language | English |
| Date | 2005-08-29 |
| Status | accepted QA |
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: 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: Form element - onclick event .
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 60, 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 60, column 82) the following success criterion: http://www.w3.org/TR/2006/WD-WCAG20-20060427/guidelines.html#minimize-error-identified.
The test case passes (line 61, 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.
After submission, the error is specified and presented to the user.
The test case passes (line 60, column 9) the following success criterion: http://www.w3.org/TR/2006/WD-WCAG20-20050630/#minimize-error-identified.
The test case passes (line 60, column 82) the following success criterion: http://www.w3.org/TR/2006/WD-WCAG20-20050630/#minimize-error-identified.
The test case passes (line 61, 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.
After submission, the error is specified and presented to the user.