RE: FAQ Re: Mixing Tables and Forms

Thanks for the update.

I am copying this to wai-tech-comments so I can cite it when I need it next. 
The 'forms in tables' question is a FAQ and is sure to come back.

Al

At 12:26 PM 2002-02-01 , you wrote:
>Hi Al,
>
>At the time of the Referenced GL list message, only Window-Eyes supported
>the title attribute in Input (and select and textarea) elements. How JAWS
>and HPR do as well.
>
>Jim
>jim@jimthatcher.com
>Accessibility Consulting
><http://jimthatcher.com/>http://jimthatcher.com
>512-306-0931
>
>-----Original Message-----
>From: w3c-wai-ig-request@w3.org
[<mailto:w3c-wai-ig-request@w3.org%5DOn>mailto:w3c-wai-ig-request@w3.org]On
>Behalf Of Al Gilman
>Sent: Thursday, January 31, 2002 7:25 AM
>To: RUST Randal; WAI (E-mail)
>Subject: FAQ Re: Mixing Tables and Forms
>
>
>Use the TITLE attribute on the INPUT elements and put a complete
>(standalone)
>prompt text in it.
>
>This would appear to be the best solution today in terms of what actually
>makes
>it through the layers of technolgy to the user.
>
>I owe this bit of knowledge to Jim Thatcher.
>
>See, for example,
>
>
<<http://lists.w3.org/Archives/Public/w3c-wai-gl/2001AprJun/0166.html>http:/
/lists.w3.org/Archives/Public/w3c-wai-gl/2001AprJun/0166.html>http:
>//lists.w3.org/Archives/Public/w3c-wai-gl/2001AprJun/0166.html
>
>Al
>
>PS:  I am not even saying don't do other things, but don't fail to do this.
>
>At 08:00 AM 2002-01-31 , RUST Randal wrote:
>>I have been tearing my hair out over this for two weeks now, and can't seem
>>to find a solution.
>>
>>Our client has a form that needs to be filled out and submitted over the
>>web.  This would be easy enough, except that the form is basically a
>complex
>>table with editable fields inside of it.  To top it off, there are two
>>levels of table headers. 
>>
>>Now I can code the table part with no problem, using scope and header
>>attributes, but I'm lost on the <input> fields that have to be included,
>>since I can't associate them with the <label> tag.
>>
>>The client requires Priority 1 compliance, but the reality is that they
>>don't really know what that means.  It's just fluff to them. 
>>
>>Has anyone run into something like this?  Any suggestions?  I can post an
>>example if need be.
>>
>>Thanks.
>>
>>Randal Rust
>>Senior Consultant
>>Covansys, Inc.
>>Columbus, OH
>>
>

Received on Friday, 1 February 2002 14:25:49 UTC