- From: Al Gilman <asgilman@iamdigex.net>
- Date: Thu, 31 Jan 2002 08:25:28 -0500
- To: RUST Randal <RRust@COVANSYS.com>, "WAI (E-mail)" <w3c-wai-ig@w3.org>
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 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 Thursday, 31 January 2002 08:25:31 UTC