W3C home > Mailing lists > Public > public-comments-wcag20@w3.org > July 2010

WCAG2 Techniques draft doc H65- use of title attribute

From: Sailesh Panchang <spanchang02@yahoo.com>
Date: Sat, 10 Jul 2010 21:17:12 -0700 (PDT)
Message-ID: <17675.87637.qm@web111721.mail.gq1.yahoo.com>
To: public-comments-wcag20@w3.org
Hello Editorial Committeee,

Two points about H65:
1. In example 3 I saw the value attribute for the Search INPUT repeats the value of the title.
The edit box will contain these words (like default text). Unless a user deletes that content or a JavaScript function deletes it as the user types in the search phrase, the search results may not contain desired results / may fail. Using the value attribute in this manner is not a technique recommended to convey purpose. The value will only display when form is first loaded (unless controlled by JS).
2. Another situation where a title attribute is necessary is when a form is in a data table and the form controls need to be associated with the row and column header cells  simultaneously. Here it is not possible to have a one to one relation between a LABEL and a form control.
Example: A survey form with column headers in first row: Question, Agree, Undecided, Disagree.  (i.e. 4 columns)
Rows that follow contain a question and a radio button in each cell corresponding to answer choice in the three columns.
The title attribute for every radio button may be a concatenation of the answer choice (column header) and the text of the question (row header) with a hyphen or colon (for instance)  as a separator.
Note: Without a title (or off-screen LABEL) it is difficult for non-visual users to pause and interrogate  for corresponding row/column header values using their assistive technology  as one tabs through the form. 
Sailesh Panchang (MS, ASQ-CSQE)
Centreville VA 20120 Phone: 571-344-1765)

Received on Sunday, 11 July 2010 04:17:51 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:14:54 UTC