E-mail List Archives
Re: using "label for=" on things other than inputs
From: Steve Faulkner
Date: Feb 23, 2016 7:51AM
- Next message: Jonathan Avila: "Re: using "label for=" on things other than inputs"
- Previous message: Sailesh Panchang: "Re: using "label for=" on things other than inputs"
- Next message in Thread: Jonathan Avila: "Re: using "label for=" on things other than inputs"
- Previous message in Thread: Sailesh Panchang: "Re: using "label for=" on things other than inputs"
- View all messages in this Thread
On 23 February 2016 at 14:43, Sailesh Panchang < <EMAIL REMOVED> >
wrote:
> The HTML5 specs also say, "button element represents a button labeled
> by its contents".
> So is there a need for one to use a label element to label a button
> really given other AT-supported methods to label a button / push
> button type input element are available?
>
Hi Sailesh, I am not and have not argued that using a label is either
necessary or recommended.
my interest is in whether what is defined in the spec for UA
implementations is actually implemented and what effect it has on the
accessible name calculation.
As stated previously, what i found in some quick testing is that use of
label on a button indeed results in the label text being used for the
button accessible name.
--
Regards
SteveF
Current Standards Work @W3C
<http://www.paciellogroup.com/blog/2015/03/current-standards-work-at-w3c/>
- Next message: Jonathan Avila: "Re: using "label for=" on things other than inputs"
- Previous message: Sailesh Panchang: "Re: using "label for=" on things other than inputs"
- Next message in Thread: Jonathan Avila: "Re: using "label for=" on things other than inputs"
- Previous message in Thread: Sailesh Panchang: "Re: using "label for=" on things other than inputs"
- View all messages in this Thread