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

Re: [techs] Fasttrack Tests - #57

From: Chris Ridpath <chris.ridpath@utoronto.ca>
Date: Wed, 2 Feb 2005 13:37:42 -0500
Message-ID: <038201c50956$477514e0$e29a968e@WILDDOG>
To: <jim@jimthatcher.com>, <Becky_Gibson@notesdev.ibm.com>
Cc: "'WAI WCAG List'" <w3c-wai-gl@w3.org>
> I totally agree Becky
The group has agreed with you too.

Test 57 will be modified to allow 3 methods of labeling a form control:
- using the FOR/ID attributes
- TITLE attribute on the INPUT element
- wrapping the INPUT element with a LABEL element

I'll modify tests 118, 119, 120 and 121 so they allow that too.

I'll also fix up that typo with the mixed FOR/ID values.


  ----- Original Message ----- 
  From: Jim Thatcher 
  To: Becky_Gibson@notesdev.ibm.com ; chris.ridpath@utoronto.ca 
  Cc: 'WAI WCAG List' 
  Sent: Wednesday, February 02, 2005 11:52 AM
  Subject: RE: [techs] Fasttrack Tests - #57

  I totally agree Becky; that issue slipped from my concern. Somehow, using the LABEL as container of INPUT plus prompting text was seen as not "explicit" in WCAG discussions. But it is explicit and it is correct HTML. It causes (last I looked) some screen reader problems but the screen reader developers can fix that in time. I still recommend for/id but the LABEL container should be OK!

  Also good catch on the "typo" that so many of us missed!


  Accessibility Consulting: http://jimthatcher.com/


  -----Original Message-----
  From: w3c-wai-gl-request@w3.org [mailto:w3c-wai-gl-request@w3.org] On Behalf Of Becky_Gibson@notesdev.ibm.com
  Sent: Wednesday, February 02, 2005 6:03 AM
  To: chris.ridpath@utoronto.ca
  Cc: WAI WCAG List
  Subject: Re: [techs] Fasttrack Tests - #57

  57 - INPUT, type of "text", has an explicit label

  I have some concerns about requiring the <label> tag to have the for attribute to tie it to the <input> field.  This seems like an "until user agents" requirement since HTML specifies that the <label> tag can wrap the <input> field.  While screen readers work better with the explicit linking of the <input> field to the <label> I don't think the screen reader implementation should force our tests - the screen readers should follow the spec and support both techniques.   

  Also, the text in the procedure text is backwards: 
  The INPUT element has a FOR attribute value that matches the ID attribute value of a LABEL element. 

  should be: 
  The LABEL element has a FOR attribute value that matches the ID attribute value of a INPUT element. 

  I hate to argue against what is a good practice, good test and recommended procedure but have concerns with letting screen reader behavior dictate our tests.  Home Page Reader now supports <labels> that wrap <input> fields and I think the latest version of JAWS may, as well. 

  Becky Gibson
  Web Accessibility Architect
  IBM Emerging Internet Technologies
  5 Technology Park Drive
  Westford, MA 01886
  Voice: 978 399-6101; t/l 333-6101
  Email: gibsonb@us.ibm.com
Received on Wednesday, 2 February 2005 18:38:27 UTC

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