David Dorward <dorward@yahoo.com> wrote:
[color=blue]
> I'm running a few tests to see how I can implement forms to conform
> with WCAG checkpoint 10.4 and be as accessible as possible while
> causing the least amount of irritation for visitors who don't
> benefit from place-holding text.[/color]
That checkpoint should be regarded as null, void, and harmful to
accessibility. This is more or less the consensus among accessibility
specialists that have discussed it on different fora, though people
usually formulate this more politely than I do now.
Note that the wording is:
"Until user agents handle empty controls correctly, include default,
place-holding characters in edit boxes and text areas."
The time has come when user agents handle empty controls correctly. If
there are still exceptions to this, the harm caused by dummy initial
content on all browsers surely overweighs them.
For one, <input ... value="Your name"> is not just stupid, it also
confuses people since it conflicts with the real use of initial values,
for setting _meaningul_ defaults that could well be accepted by the
user (like a user name picked up from a data base). Before anyone says
that nobody can be so stupid as to assume that he can just accept "Your
name" in the name field, let me remind everyone that accessibility is
not just for the blind. It's also a matter of being accessible to
people who have cognitive disabilities, for example.
--
Yucca,
http://www.cs.tut.fi/~jkorpela/
Pages about Web authoring:
http://www.cs.tut.fi/~jkorpela/www.html