Mandatory text input field with error correction (mail address) Developed by W3C/WAI's Evaluation and Repair Tools Working Group (ERT WG). We invite comments and discussion. Please address your feedback to public-wai-ert-tests@w3.org, a mailing list with a public archive. en Copyright © 1994-2008 W3C® (MIT, ERCIM, Keio), All Rights Reserved. W3Cliability, trademark, document use and software licensing rules apply. Your interactions with this site are in accordance with our public and Member privacy statements. $Date: 2009/04/29 09:08:23 $ unconfirmed $Revision: 1.14 $ XHTML™ 1.0 The Extensible HyperText Markup Language (Second Edition) The INPUT element The LABEL element Intrinsic events: onclick Standard ECMA-262 : ECMAScript Language Specification, 3rd edition (December 1999) Document containing two mandatory text input fields (first name, last name) that are already filled and set to read-only. In addition, it contains one text input field for a mail address with mandatory input. If the user submits and no text is entered or the mail address is invalid, the error is identified and described to the user in text (DOM).

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.

 ../testfiles/sc3.3.1_l1_033.html 1.1 86 5 /h:html/h:body/h:form/h:div/h:label 86 65 /h:html/h:body/h:form/h:div/h:input 87 73 /h:html/h:body/h:form/h:div/h:div/h:input/@onclick 7 2 /h:html/h:head/h:script[2]

After submission, the error is specified and 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.