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

RE: Tests 186, 187, 188, 189,

From: Andrew Kirkpatrick <akirkpatrick@macromedia.com>
Date: Wed, 10 Aug 2005 07:39:45 -0700
Message-ID: <DC9D05204B1E16419D62C12561C9322103D8FCEA@p01exm01.macromedia.com>
To: "David MacDonald" <befree@magma.ca>, <wendy@w3.org>, "WCAG WG mailing list" <w3c-wai-gl@w3.org>, "Michael Cooper" <michaelc@watchfire.com>, "Ben Caldwell" <caldwell@trace.wisc.edu>, "Chris Ridpath" <chris.ridpath@utoronto.ca>
I'm a recent addition to this list, generally attending to
Macromedia-related issues.  This is not an issue that is specific to
Macromedia but I feel compelled to add my two cents.
 
 LABEL must not contain INPUT.
<http://www.w3.org/WAI/GL/WCAG20/tests/test186.html>   
 
I wholeheartedly disagree with this.  This is valid HTML/XHTML and I
have yet to find an issue with any of the user agents so long as the
for/id attributes are also used, as they should be. On many forms this
is in fact desireable since the label element takes CSS styling nicely
so that a developer can put label {display:block;} into the CSS and have
a very clean, neat, valid HTML file that works well with user agents
also.  I don't think that a valid practice should be prohibited.
 
 INPUT element must have only one associated LABEL.
<http://www.w3.org/WAI/GL/WCAG20/tests/test187.html>   
 
Why?  Because there is poor user agent support for this currently?  This
is also a valid practice, explicitly allowed by the HTML recommendation.
I don't think that this is a good rule because it limits future
improvements in user agents that might otherwise support multiple
labels.
 
An interesting thing is that in the passing test file, once you enter
forms mode in JAWS, you must enter something into the field in order to
back out of the page.  You can't back out of the page (using the back
button) if you enter and exit forms mode without putting something in
the field. Because it backs into the form field and then cannot back out
of it. This I think is a bug in JAWS. 
 
I tried this also and didn't get this behavior. It would be a JAWS bug,
I agree.  What version were you using?
 
Thanks,
AWK



Andrew Kirkpatrick
Principal Accessibility Engineer, Macromedia
akirkpatrick@macromedia.com
  

   
Received on Wednesday, 10 August 2005 14:40:37 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:47:39 GMT