W3C home > Mailing lists > Public > w3c-wai-gl@w3.org > July to September 2013

RE: Aria-labelledby for form controls- examples

From: Schnabel, Stefan <stefan.schnabel@sap.com>
Date: Fri, 13 Sep 2013 06:50:42 +0000
To: David MacDonald <david100@sympatico.ca>, Sailesh Panchang <spanchang02@yahoo.com>
CC: james nurthen <james.nurthen@oracle.com>, "w3c-wai-gl@w3.org" <w3c-wai-gl@w3.org>
Message-ID: <323C3CDA661E2E489F372903A1B2A79448A7C23E@DEWDFEMB10C.global.corp.sap>
IMHO, as a general pattern, all examples should strive for covering as many disabilities as possible. If there are alternatives, the one which covers the most should be rated as prime.

For instance, it is fine to use aria-label for a text field with no visible label, but this does not help non-blind people detecting the label. 
Therefore I encourage considering the usage of <title> attribute at first instance.

Dexterity is really a good point, also when it comes to web content on mobile devices. Having the classic <label for> will enlarge the touchable area also.

Regards
Stefan

-----Original Message-----
From: David MacDonald [mailto:david100@sympatico.ca] 
Sent: Donnerstag, 12. September 2013 23:56
To: Sailesh Panchang
Cc: james nurthen; w3c-wai-gl@w3.org
Subject: Re: Aria-labelledby for form controls- examples


I'm out of town training this week and so just skimming the discussion...
But I think we should discuss the bidirectional referencing of <label for> and labelledby... During my teaching today a programmer approached me and discussed the advantages of <label for> in that it if a user clicks on the label in any modern browser the puts focus in the form field... And this helps people with dexterity problems, even it the aria labelledby gets the accessible name.

So it would be something like this example...

http://rawgithub.com/w3c/aria-in-html/master/index.html#aria-labelledby-and-aria-describedby

I notice this is what Steve Faulkner did in the using aria in html5 note...

Cheers
David MacDonald 
>From my iPad 

On 2013-09-12, at 12:16 PM, Sailesh Panchang <spanchang02@yahoo.com> wrote:

> Hello James,
> The third issue about the checkbox:
> Before the example, there is a paragraph which explains  why the checkbox needs a specific identifier.
> The 'check to compare' serves little or no purpose, I'd say even visually,  but it is part of the UI. 
> But I'll reiterate as a VI user  that  It is text that can be safely be ignored by AT to avoid cluttering verbosity. So I believe the aria-labelledby markup is good as is. 
> Agree?
> Ref: http://mars.dequecloud.com/demo/form-markup.htm#tech9
> 
> About role=group write-up:
> What I have already submitted is a specific technique for grouping related form controls generally usable when one is constrained by design to use fieldset-legend technique. So please review  / discuss and consider for incorporating into techniques.
> As I wrote it, it will be good if others can comment.
> Also review other changes / comments :
> See
> http://lists.w3.org/Archives/Public/public-wcag2-techs/2013May/
> http://lists.w3.org/Archives/Public/public-wcag2-techs/2013Aug/0000.html
> Thanks,
> Sailesh
> 
> --------------------------------------------
> On Wed, 9/11/13, james nurthen <james.nurthen@oracle.com> wrote:
> 
> Subject: Re: Aria-labelledby for form controls- examples
> To: "Sailesh Panchang" <spanchang02@yahoo.com>
> Cc: w3c-wai-gl@w3.org
> Date: Wednesday, September 11, 2013, 1:17 PM
> 
> 
> On 9/11/2013 7:52 AM, Sailesh Panchang wrote:
>>        On 9/10/2013
>>    7:54 AM, Sailesh Panchang
>>          wrote:
>> Please review:
>>    Aria-labelledby for form controls
> 
Received on Friday, 13 September 2013 06:51:11 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 24 March 2022 21:07:54 UTC