WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Adding a label to search box

for

From: Joshue O Connor
Date: Apr 14, 2006 3:40AM


> Comparing like for like, a
>> form input without label but with a title attribute (which has been
>> proven in testing to be announced by screen readers even in default
>> settings) is certainly more accessible than the same input without label
>> and without title attribute.

I have been reading through this (interesting) thread and realised that there is a disconnect here.
Probably just in my head but I thought I'd share :)

IMO the title attribute should be treated in a consistent
manner by user agents. How many developers realise that the title attribute when applied
to a link will usually *not* be read out, but *will* be read out when found in a form.
I didn't know this. Its confusing and adds another dimension of difficulty for a budding
developer who is trying to understand how best to serve diverse user requirements that
they will not be familiar with.

In the context of links. the additional information should be applied by an attribute with a different name.
As Jukka suggested "info" of similar makes sense. Doing this would make it easier to distinguish between
the two, and apply them correctly, as needed.

There is also an issue with <label>. In the discussion I found myself wondering:
Are we talking about informative text applied using <label>,
or the application of <label for="foo"> to associate form controls?

Again maybe these elements should have different names to distinguish them and make it
easier to apply them correctly?

One for the HTML list I'm sure.

Josh

Joshue O Connor

Senior Accessibility Consultant

**Centre for Inclusive Technology (CFIT)* *
National Council for the Blind of Ireland

Website:http://www.cfit.ie
E-Mail: <EMAIL REMOVED> Tel: +353 1 8821915

Patrick H. Lauke wrote:
> Jukka K. Korpela wrote:
>
>> It is inappropriate to expect that all people automatically recognize
>> a box followed by a button or an image as a search form.
>
>
> But what if the button, immediately following the text input, is clearly
> labelled as "search"?
>
>> Now that's something where title attributes may really sound useful,
>> but is it just an illusion? I think the real problem is that radio
>> buttons aren't really a good way to set up such menus. Even when
>> people see the page, they have difficulties in remembering whether
>> "agree" was on the left or on the right,
>
>
> They *may* have difficulties, depending on the length of the form /
> number of items the user is asked to rate in this manner.
>
>> Which one is easier (and faster): to select a radio button among, say,
>> five buttons by clicking on it (or by other means), or to type a digit
>> from 1 to 5?
>
>
> Personally, if it's a form where the majority of interaction can be done
> via mouse, I find radio buttons easier and faster. A dropdown/select may
> be a good alternative though.
>
>>> All of these are made accessible to someone who cannot see the screen
>>> by adding title attrbutes to the input elements;
>>
>>
>> Are you sure? You seem to think of the attribute as some kind of magic.
>
>
> It seems more like a statement of fact to me. Comparing like for like, a
> form input without label but with a title attribute (which has been
> proven in testing to be announced by screen readers even in default
> settings) is certainly more accessible than the same input without label
> and without title attribute.
>
> P