WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: using "label for=" on things other than inputs

for

From: Jonathan Avila
Date: Feb 23, 2016 7:56AM

> Jon, In your example:
<label for="a1"> Foreground <button id="a1">Color</button></label> With implicit labelling, there is no need for for-id, right?

Correct, although implicit labels without matching for/id are not supported by some technologies such as Dragon and perhaps Talkback on Android. So this wraps both and contains the explicit association those AT need.

> Also if "Foreground" is meant to function as a visible label like the button content, "Color", why not have the word "Foreground within button content? Visually too one may only identify "color" to be the button's name really.

This would likely be done to make sure the button widths are equal or space reasons. In some cases repeating text on each button actually makes it more difficult for people looking at the buttons. For example, say you had an add button and it corresponded with some other text in a row and you didn't want to duplicate the text.

Jonathan

Jonathan Avila
Chief Accessibility Officer
SSB BART Group
<EMAIL REMOVED>
703.637.8957 (o)
Follow us: Facebook | Twitter | LinkedIn | Blog | Newsletter