Re: Implicit labels

Because it has no FOR/ID attribute value connections. Also called wrapped because <label> is wrapped around <input></label>.

Paul J. Adam
Accessibility Evangelist 
www.deque.com

> On Aug 22, 2016, at 12:17 PM, Mike Elledge <melledge@yahoo.com> wrote:
> 
> Hi Paul and Siri--
> 
> Why is the example considered an implicit label?
> 
> Mike
> 
> 
> On Monday, August 22, 2016 12:26 PM, Paul J. Adam <paul.adam@deque.com> wrote:
> 
> 
> I would say that’s outdated information. I don’t know of any screen readers that don’t support wrapped labels. 
> 
> Maybe there’s a bug with Dragon but it should be fixed if so. 
> 
> Paul J. Adam
> Accessibility Evangelist 
> www.deque.com <http://www.deque.com/>
>> On Aug 22, 2016, at 11:05 AM, Balusani, Shirisha <sirib@uillinois.edu <mailto:sirib@uillinois.edu>> wrote:
>> 
>> To be more clear:
>>  
>> The HTML and XHTML specifications allow both implicit and explicit labels. However, some assistive technologies do not correctly handle implicit labels (for example, <label>First name <input type="text" name="firstname"></label>).
>> Is that still true or is it outdated information?
>>  
>> _____________________________________________
>> From: Balusani, Shirisha 
>> Sent: Monday, August 22, 2016 10:58 AM
>> To: w3c-wai-ig@w3.org <mailto:w3c-wai-ig@w3.org>
>> Subject: Implicit labels
>>  
>>  
>> Is implicit labelling is supported by all screen readers in all browsers?
>>  
>> Do we have to use for and id along with the implicit labels to make sure that the element tied to label is read by all AT users?
>>  
>> Thanks
>> Siri
> 
> 
>