- From: Sailesh Panchang <sailesh.panchang@deque.com>
- Date: Mon, 8 Dec 2008 10:03:34 -0500
- To: <public-comments-wcag20@w3.org>
G167: Using an adjacent button to label the purpose of a field G167 is documented as a sufficient technique for SC3.3.2 - Labels or Instructions. As I understand this technique, it is alright for a text input field, (say for search-phrase), not to have a label or title to explicitly identify the purpose of the field so long as the search button placed after it is properly labeled. Is this interpretation correct? So a screen reader user is expected to tab to next control, exercise judgment to determine if the label associated with that control can be related to the earlier control? The note that requires compliance with 4.1.2 is not clear. Perhaps an HTML example might help. Thanks, Sailesh Panchang Accessibility Services Manager (Web and Software) Deque Systems Inc. (www.deque.com) 11130 Sunrise Valley Drive, Suite #140, Reston VA 20191 Phone: 703-225-0380 (ext 105) E-mail: sailesh.panchang@deque.com
Received on Monday, 8 December 2008 15:01:31 UTC