- From: Charles McCathieNevile <charles@w3.org>
- Date: Thu, 31 Jan 2002 10:35:20 -0500 (EST)
- To: RUST Randal <RRust@COVANSYS.com>
- cc: "WAI (E-mail)" <w3c-wai-ig@w3.org>
Yep. Another possiblity (it is an "until user agents" checkpoint in WCAG 1.0 is to include text in the input itself, for textfields: <input type="text" value="0hours" ... so in lynx you get 0hours_______________ as a text input line. You probably should also use some helpful information, laid out to come before the input or after it, in a reasonably regular way, and identified with a label element. THis will help people who are using the system visually and are unlikely to see the title attribute value, and will work on systems that do implement accoridng to specification. <label for="#hoursAttended">Hours attended <input... /></label> or in a table <td><label for="#hoursAttended">Hours attended</td><td><input... (perhaps the first cell in the column is a heading, scoped for the two cell row...) cheers Chaals On Thu, 31 Jan 2002, RUST Randal wrote: Unfortunately, the page that is referenced by the URL given in Jim Thatcher's example is no longer there, so I'm not sure how the code is supposed to be written. Is the following correct? ---------- <input type="text" id="hoursAttended" name="hoursAttended" title="Input the number of hours the child attended this month." /> ---------- Thanks, Randal -- 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 January 2002 10:35:22 UTC