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

RE: A new one: label vs. Scope

From: Charles McCathieNevile <charles@w3.org>
Date: Tue, 23 Apr 2002 12:32:34 -0400 (EDT)
To: Mike Scott <mscott2@msfw.com>
cc: <w3c-wai-ig@w3.org>
Message-ID: <Pine.LNX.4.30.0204231229120.31859-100000@tux.w3.org>
Agreed about what needs to happen, and pleased to hear that the software is
getting there.

One of the problems is that this is a developing field, and ufortunately
software producers can't just make things instantly happen "becuase they

And yes, it seems that it is OK to nest fieldsets.

I think that in fact what is more promising is Xforms, which seperates
significantly the choices being made from the way they are presented - you
can have one form defined for collecting informaton and choose afterwards on
a case by case basis whether it is easier as a dropdown menu, a set of radio
buttons, or text entry. Of course this too needs to be implemented in the



On Tue, 23 Apr 2002, Mike Scott wrote:

  Good point Charles.

  Once we give the assistive technologies (and the users with assistive
  technologies) a little more time to catch up, fieldset and legend will
  solve many of these forms-related issues. (JAWS 4.02 and HPR 3.02 are
  actually doing a pretty good job with fieldset already.)

  I don't think even fieldset is going to help us in the "tabular
  form"-type examples -- but maybe it's not really an issue for HTML, but
  rather a matter of getting the screen readers to merge their "forms" and
  "tables" reading modes...


  p.s. just wondering (no practical example in mind) -- is it valid to
  "nest" fieldsets?
Received on Tuesday, 23 April 2002 12:32:36 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 13 October 2015 16:21:18 UTC