WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Implicit labeling dropped from WCAG?

for

From: Steve Faulkner
Date: May 6, 2016 7:06AM

A general comment, referring to this method as 'implicit' may infer
something that is untrue. In terms of exposing the accessible name to
accessibility APIs either method works. i.e. an input's accessible name is
provided and exposed by the browser. The IE issue was a bug and got fixed,
the dragon issue is an ongoing major bug in dragon not using the
standardised accessibility APIs

--

Regards

SteveF
Current Standards Work @W3C
<http://www.paciellogroup.com/blog/2015/03/current-standards-work-at-w3c/>;

On 5 May 2016 at 23:55, Birkir R. Gunnarsson < <EMAIL REMOVED> >
wrote:

> Me and a few colleagues ran into an issue with Voiceover on iOS 9 and
> implicitly labeled radiobuttons.
> For those who do not know, implicit labeling is when you wrap the form
> field to be labeled along with the label text in a label tag, like so:
> <label><input type="text" size="30">Please enter your name.</label>
>
> This is valid use of the label tag per HTML5 specification.
> But there used to be a WCAG technique that recommended implicit labeling.
> That technique is apparently deprecated.
> Does this mean that WCAG no longer recommends implicit labeling of form
> fields?
> If so, why?
> If anybody knows the background on this, I'd be curious.
> -B
>
> --
> Work hard. Have fun. Make history.
> > > > >