WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Buttons and label tags

for

From: reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:references;
Date: Feb 10, 2005 4:51AM

On Thu, 10 Feb 2005 13:16:17 +0200 (EET), jkorpela wrote:

> Why button? A link would be a more natural approach. Is there any reason
> not to make the address itself a link? Links are generally more flexible
> and more accessible than buttons. Buttons should normally be used for
> actions that submit some data to some processing or involve an action
> like ordering something.
>

Personally I think the button works quite well, apart from the obvious
limitations. I don't think a link on the name of the store would be
intuitive enough. It's hard to say without seeing an example.
Unfortunately it is a secure site so I can't give out a URL.

>
> If they are on the same line, on which there is nothing else, the
> association is rather evident.
>

My issue with this is with people using speech browsers. If they tab
to the first link i.e. the map button and then tab again to the next
map button, it is quite awkward for them to know which relates to
which.

> > Can I use a label to do this?
>
> In principle you could, if the button is an element.
> But it seems that the button itself is an unnecessary complication.
>

Sorry I should have been clear by my use of the word button. It is not
a form element but rather an image (shaped as a button) with a href,
hence it has alt text and would therefore appear in a list of links.
So I still have a dilemma of associating each href with its
appropriate result.

Regards,
Kieran.