W3C home > Mailing lists > Public > w3c-wai-ua@w3.org > April to June 1999

Re: FW: Techniques 5.5.3 & 5.5.4

From: mark novak <menovak@facstaff.wisc.edu>
Date: Wed, 7 Apr 1999 16:03:30 -0500
Message-Id: <v03007815b3317852261e@[128.104.23.196]>
To: "Denis Anson" <danson@miseri.edu>, "WAI UA Group" <w3c-wai-ua@w3.org>

>5.5.3 [Priority 1]
>Allow the user to search for a form control based on its text content.
>Because a form control does not have a standard label, it can be important
>to allow a person with a disability to locate controls based on the text
>that has been entered.  For example, a user might have entered information
>about his/her name and address into a form, and on reviewing the
>information, discover a typographical error.  The form control for the
>user's street address may be labeled "Street," "Address," "Address1" or even
>"Street Address."  The ability to search based on these labels would not
>allow the user to locate such an entry with facility unless the s/he had
>memorized all labels during the process of filling out the form.  However,
>if the user could search for "Pine," as content in a form control, the focus
>would be moved directly to the entry where the apartment number had been
>mis-typed.
>5.5.4 [Priority 1]
>Allow the user to search for a form control based on its attribute values.
>In a long form, the user should be able to search for form entries on a page
>by the labels on those forms.  For example, a form may require entry of
>information that is related to the user, but separated on the form.
>Searching on form labels would allow the user to find out if the form
>required information that might be pasted in, while that information is
>readily available to the user.  Similarly, many forms distinguish between
>required and optional information.  This distinction is typically made based
>on some attribute of the form label.  Allowing the user to search for form
>control attributes would allow the user to select required information
>without the need of paging through all optional entries.
>
>When the time comes, I will argue that both of these are at most Priority 2
>items, since you can tab through the page to find this information, so it is
>not impossible to use an agent that doesn't allow direct searching.
>However, it can be significantly harder for a visually impaired person, so
>it is a priority 2 issue.



Per our teleconf. call earlier today, I agree with Denis that these should
be priority 2

mark
Received on Wednesday, 7 April 1999 17:11:54 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 27 October 2009 06:48:57 GMT