W3C home > Mailing lists > Public > w3c-wai-gl@w3.org > July to September 2001

Re: the emperor's clothes (or lack thereof)

From: Al Gilman <asgilman@iamdigex.net>
Date: Mon, 10 Sep 2001 21:20:52 -0400
Message-Id: <Version.32.20010910155743.04145220@pop.iamdigex.net>
Message-Id: <Version.32.20010910155743.04145220@pop.iamdigex.net>
To: "gregory j. rosmaita" <oedipus@hicom.net>, <w3c-wai-gl@w3.org>
At 03:16 PM 2001-09-10 , gregory j. rosmaita wrote:
>GJR: which is the point of public review - wasn't kelly's concern adequately
>addressed via the response archived at (long URI warning):


True confessions, when I read the two assertions up front:

- this is technology-specific
- it's basically in there

both of which I felt were a) important and b) untrue, I stopped reading.

Yes, the edit in that post eliminates the chance to say "nowhere can I

But it's not an adequate response because the rewrite still hides a major
as if it were minor.

The injunction to "label form controls" is not only not
technology-specific, it
is just-right abstraction.  It is abstract because it applies to interactive
widgets found in web media from left and right.  It is appropriately focused
because form controls have their own class-specific requirements and
Talking about labels in general is diffuse and weak.  Talking about the
requirement to have labels for form controls is important to say because that
is so often where the process breaks down, and tends to break irreparably.

The generalized discussion of "use structure and labels ..." misses the
essential before:after relationship that is at the heart of this rule.  Use
labels that let the user know before they activate the control what will
after they activate the control.  This is the essence inherited from the ten
commandments of UI usability.  And the time separation or sequence is
to capturing what is required.

That is why I felt I should come back and reiterate the flow of reasoning I
felt had been mostly missed, while it is essential to getting across this
critical injunction for web accessibility.

It's not just a "for instance" of "use labels."  It's a "for instance" of
advance warning" as well.  Of course it is a example of both of those.  But it
is the second which lends it its proper importance.  Which is, like, at the
head of the class.

Received on Monday, 10 September 2001 20:57:24 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 16 January 2018 15:33:38 UTC