W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > April to June 2002

Re: place-holding characters in form elements

From: David Poehlman <poehlman1@comcast.net>
Date: Fri, 24 May 2002 07:06:32 -0400
To: Nick Kew <nick@webthing.com>, w3c-wai-ig@w3.org
Message-id: <002f01c20313$1042f240$91e03244@DAVIDPOEHLMAN>
and of course, if It never is sensed that onfocus has been triggered,
you still have to clear it manually but at least you know what format
the date should take.

----- Original Message -----
From: "Nick Kew" <nick@webthing.com>
To: <w3c-wai-ig@w3.org>
Sent: Thursday, May 23, 2002 7:01 AM
Subject: RE: place-holding characters in form elements


On Thu, 23 May 2002, Jukka Korpela wrote:

> > place-holding characters.
>
> (You mean Guideline 10.4. (It is at priority level 3.))
>
> > This is causing us some grief
>
> Many people share your opinions and views.

Myself included, FWIW.  IMNSHO, guidelines should always steer well
clear of advocating anything likely to be harmful (e.g. confusing)
either

> My advice is: Don't use place-holding characters. (They are sometimes
> claimed to give information about the kind of data that is expected,
but any
> need for such hints is caused by lack of adequate explanations and
labels
> before the fields.)

Agreed.

A technique I occasionally use is to populate a field with a help
string, and use an onfocus event to clear it the first time the
field gets focus.  But whether that is a good idea is more a matter
of usability than accessibility.

<input name="date" value="YYYY-MM-DD" onfocus="value=''">

shouldn't be too confusing, but can never be more than an ad-hoc usage.

--
Nick Kew

Available for contract work - Programming, Unix, Networking, Markup,
etc.
Received on Friday, 24 May 2002 07:07:02 GMT

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