|Title||Mandatory text input field with error correction (date)|
|Rights||Copyright BenToWeb 2005-2007|
Technologies are markup languages or data formats. If the technology is a markup language, “features” refers to elements and attributes.
Technical specification: The INPUT element .
Technical specification: The LABEL element .
Technical specification: Form element - onclick event .
The document is intended to fail, because the input error is specified and presented to the user in text but screenreader users may not notice the error message that is presented below the form.
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.
“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: http://www.w3.org/TR/2006/WD-WCAG20-20060427/guidelines.html#minimize-error-identified.
Before submission, the error is specified and presented to the user. However, user testing with JAWS and HomePage Reader highlighted the following problem: after submission of the form without a real date, the focus remains on the submit button, so screenreader users may not notice the error message below the form.
This test case does not map to a WCAG 2.0 technique or failure. (The test case may map to "Providing client-side validation and adding error text via the DOM (future link)" in a future draft.)
The test case passes the following success criterion: http://www.w3.org/TR/2006/WD-WCAG20-20050630/#minimize-error-identified.
Before submission, the error is specified and presented to the user.