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

Re: 10.4 Re: Checkpoints 10.4 and 10.5

From: Steven McCaffrey <SMCCAFFR@MAIL.NYSED.GOV>
Date: Thu, 31 May 2001 11:15:06 -0400
Message-Id: <sb1627cd.020@MAIL.NYSED.GOV>
To: <charles@w3.org>
Cc: <poehlman1@home.com>, <w3c-wai-ig@w3.org>, <graham_oliver@yahoo.com>
Hello Charles:

     Good question.  I don't want to generalize, so let me just give an example that does work.  The example in section 11.2 of the 
HTML Techniques for Web Content Accessibility Guidelines 1.0 works fine.  I hear
"First name colon edit"
then I hit tab and hear:
"Last name colon edit"
which is fine.
The snipet for the first name is:

   <LABEL for="firstname">First name: </LABEL>
   <INPUT type="text" id="firstname" tabindex="1">

Note my comments above are not about grouping form controls which is the main point of 11.2.  I am just commenting on the label element.


Steve


>>> Charles McCathieNevile <charles@w3.org> 05/31/01 09:50AM >>>
If they have labels (using the label element) does this improve things?

Charles McCN

On Thu, 31 May 2001, Steven McCaffrey wrote:

  Hi Charles:


       I'm using JFW 3.31.  I will just hear "edit".

  Steve

  >>> Charles McCathieNevile <charles@w3.org> 05/31/01 08:43AM >>>
  Thanks Steven, Dave.

  Can you please explain what software you're using, and what happens?

  cheers

  Chaals

  On Thu, 31 May 2001, Steven McCaffrey wrote:
    Hello:
         I agree with David in that it is still an issue.  The consequence is
    that I will hear only "Edit" but will not know what type of information is requested.

    Steve McCaffrey
    Information Technology Services
    NYSED
    >>> "David Poehlman" <poehlman1@home.com> 05/31/01 07:49AM >>>
    it is still an issue although many have solved it.  even though you have
    to rub the text out, it is best to have something telling you where to
    write because some renderings still confuse labels with edit boxes.

    ----- Original Message -----
  ...

    the rationale for this one was that there were assistive technology and
    browser combinations that would skip over empty form controls. I am not
    certain, but I believe that this is no longer an issue. I will ask the
    Web Content Accessibility Guidelines group to address this question as
    fast as possible.



-- 
Charles McCathieNevile    http://www.w3.org/People/Charles  phone: +61 409 134 136
W3C Web Accessibility Initiative     http://www.w3.org/WAI    fax: +1 617 258 5999
Location: 21 Mitchell street FOOTSCRAY Vic 3011, Australia
(or W3C INRIA, Route des Lucioles, BP 93, 06902 Sophia Antipolis Cedex, France)
Received on Thursday, 31 May 2001 11:18:32 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 19 July 2011 18:13:55 GMT