RE: Aria-labelledby for form controls- examples

Great overview. However, content of the chapter

>> 10. Caution when using title

makes clear that there are no best practices available that cover all major Browser-AT combinations flawlessly.

Yes there are workarounds (include the name/label text info also in the title string) but this sheds light on the poor implementations and the pull-ups one has to do to deliver the entire info on focus.

In my opinion, at least, an option to display the tooltip/title on request by a keyboard shortcut is mandatory to implement for each and every browser out there.

Regards
Stefan

-----Original Message-----
From: Sailesh Panchang [mailto:spanchang02@yahoo.com] 
Sent: Mittwoch, 11. September 2013 16:53
To: w3c-wai-gl@w3.org; james nurthen
Subject: Re: Aria-labelledby for form controls- examples

     On 9/10/2013
 7:54 AM, Sailesh Panchang
       wrote:
Please review:
 Aria-labelledby for form controls
 http://mars.dequecloud.com/demo/form-markup.htm#tech5
     
     JN: I believe this is no different from http://www.w3.org/WAI/GL/wiki/Using_aria-labelledby_to_concatenate_a_label_from_several_text_nodes#Example_2:_A_simple_data_table_with_text_inputs
     Is there anything I am missing that the example in the
 current      technique doesn't have?
 Sailesh 09/11: 
The survey page for 'aria-labelledby for controls' had no techniques. It was marked 'TDB'.
That's why I sent these examples.
If there  were examples already available, they should have been on that survey page, no?

 http://mars.dequecloud.com/demo/form-markup.htm#tech7
     
     JN: We certainly need a role=group technique to cover
 this use case.
     Would someone like to volunteer to write this?
Sailesh 09/11:
There's one already  submitted in May 2013. 
I had submitted a few techniques including one for the role=group as an alternative for fieldset-legend
http://lists.w3.org/Archives/Public/public-wcag2-techs/2013May/
There's a problem with the technique submission form which I had conveyed to Andrew and code had not got submitted alright.
So a Word doc was sent to Andrew with my recent submissions / comments  a few weeks ago. See attached.
A few times, I requested that these be reviewed.     
           
 http://mars.dequecloud.com/demo/form-markup.htm#tech9
     
     JN: I think this example needs modification and then
 could fit      nicely into the Using        aria-labelledby to concatencate multiple text nodes
 case.
 As it stands there is no indication to AT that checking
 the checkbox      does a compare operation so the labelledby needs to
 point to the header and the checkbox label and not just the header.
Sailesh 09/11:
Well the aria-labelledby works fine for the checkbox and conveys its purpose clearly.
There is also an explicit label 'check to compare' which is read when one arrows down (out of forms mode). 
Certainly instruction that you can compare 2 or 4 items will be conveyed somewhere at the start / end of the form.
That does not  have to be conveyed by every checkbox.
Based on your argument, every form control's label needs to convey which form it belongs to and what will be accomplished by submitting the form. 
i.e. on a login form the label for username will need to convey that it will be submitted as part of the login process.
If every checkbox were to convey that once checked it will be used for comparison,  that will be a lot of verbosity and a lot of problem. 
When you have a list of emails displayed  on a Web page, one can check them and delete or move or mark as spam etc. The checkbox's label does not convey this.
Thanks and regards,
Sailesh
     
 
     Regards,
 
     James
 
     
     
       
 
 Secondly in the matter of aria-labelledby for non text
 content:
 - The first example has no alt
 - The second one: seldom  is there text taht says '4 out
 of 5' for *rating it is only the image.
 But, yes, the  example is a good one if it is indeed marked
 up that way with multiple star images and text alongside. 
 
 About use of role=headings:
 It appears it is more of a remediation technique to be used
 only when HTML h<n> cannot be used like for h7 as
 illustrated?
 Need to think of more used cases I guess.
 
 Thanks,
 Sailesh

Received on Thursday, 12 September 2013 07:51:13 UTC