RE: proposed change: links inside label elements

> From: Reinier Kaper [mailto:rp.kaper@gmail.com] 
> Sent: Monday, January 13, 2014 11:49 AM
> 
> Hi Steve,
> 
> Yes as long as not the whole label becomes an anchor, it's still fully
> functional.
> 
> Maybe disallowing that case is a good idea, but I don't really see the
> advantage of doing that, unless there's solid data that suggests that
> this happens a lot and interferes with (for example) AT and screen-
> readers.

This is the part I am curious about.

How is it read in the screen readers? Is the anchor lost in the verbalization of the label?

I am also even more curious how users with mobility impairments are affected. IME, mobility-impaired users often have enough trouble clicking a small button, icon or hyperlink. Having one embedded in another (such as hyperlinks within sliders on home pages) causes frustration when the click is off-target and the slide changes when the user wanted to click the link (or the user wanted to change the slide and the link is activated).

I expect mobility, not vision, is the impairment most likely to be negatively affected by this pattern.

So who here has experience with mobility impairments and can weigh in?



> Kind regards,
> Reinier Kaper
> 
> On 13 January 2014 11:42, Steve Faulkner <faulkner.steve@gmail.com> 
> wrote:
> checked the code you provided:
> 
> 
> <label> 
>   <input type="checkbox" /> 
>   I agree to the <a href="tos.html"> terms of service</a>  for using
> this product.
> </label> 
> for the non link text the control can still be activated, so maybe
> only needs to restrict case where label text is wholly contained with
> a link:
> 
> 
> <label> 
>   <input type="checkbox" /> 
> <a href="tos.html"> I agree to the terms of service for using this
> product.
> </label> </a> 
> 
> 
> 
> --
> 
> Regards
> 
> SteveF
> HTML 5.1

Received on Monday, 13 January 2014 17:19:26 UTC