W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > January to March 2003

Re: Form text field default & validation

From: David Poehlman <poehlman1@comcast.net>
Date: Mon, 31 Mar 2003 14:50:28 -0500
To: "Jukka K. Korpela" <jkorpela@cs.tut.fi>, w3c-wai-ig@w3.org
Message-id: <000401c2f7be$c8653cc0$6501a8c0@handsontech>

I wouldn't jump on that too fast but than I don't know about all user
agents.  I suspect though that there are still situations where it might be
applicable.


----- Original Message -----
From: "Jukka K. Korpela" <jkorpela@cs.tut.fi>
To: <w3c-wai-ig@w3.org>
Sent: Monday, March 31, 2003 2:40 PM
Subject: Re: Form text field default & validation



On Mon, 31 Mar 2003, Donna m87 wrote:

> Accessibility demands that a text area field contain default text.

No, that's generally considered as not applicable any more. In other
words, when the WCAG 1.0 guidelines say
"Until user agents handle empty controls correctly, include default,
place-holding characters in edit boxes and text areas."
  (at http://www.w3.org/TR/WCAG10/#tech-place-holders )
this is to read so that it is no more relevant, since user agents handle
empty controls correctly.

> How can I include default information in the text field AND validate
> that same text field?

Simply don't include any "dummy" default text as a placeholder.
But if there is a meaningful default value that helps the user, it should
be included. In that case, it should be acceptable input and there should
be no reason to check against it. (But in general, it is possible to check
that a form field value is different from a its initial value, at least by
explicitly comparing it against a fixed value.)

--
Jukka "Yucca" Korpela, http://www.cs.tut.fi/~jkorpela/
Received on Monday, 31 March 2003 14:54:43 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 19 July 2011 18:14:08 GMT