WebAIM - Web Accessibility In Mind

E-mail List Archives

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

for

From: Detlev Fischer
Date: Feb 20, 2016 5:42AM

All this doesn't quite answer my original question whether the use of label on elements other than those Steve listed could be confusing and should be discouraged. I take it nobody would see a failure of 1.3.1 for using 'label for=' on read-only text, disabled input, or a button that already has an accessible name via value - correct?

Sent from phone

> On 20 Feb 2016, at 09:37, Steve Faulkner < <EMAIL REMOVED> > wrote:
>
> On 20 February 2016 at 01:42, Jonathan Avila < <EMAIL REMOVED> >
> wrote:
>
>> HTML Accessibility API Mappings 1.0<
>> https://www.w3.org/TR/html-aam-1.0/#button-element> also indicates the
>> following which does not seem to include the label element:
>
> Yes you are correct that this is was the API spec currently says, that is
> my fault.
>
> I have filed an issue https://github.com/w3c/aria/issues/259
>
> --
>
> Regards
>
> SteveF
> Current Standards Work @W3C
> <http://www.paciellogroup.com/blog/2015/03/current-standards-work-at-w3c/>;
> > > >