Re: Label Association with Input Field Question

Yep, was afraid of that. Thanks for the feedback, guys!
Mike
 

    On Tuesday, June 7, 2016 2:24 PM, John Foliot <john.foliot@deque.com> wrote:
 

 #yiv1064204237 #yiv1064204237 -- _filtered #yiv1064204237 {font-family:Helvetica;panose-1:2 11 6 4 2 2 2 2 2 4;} _filtered #yiv1064204237 {panose-1:2 4 5 3 5 4 6 3 2 4;} _filtered #yiv1064204237 {font-family:Calibri;panose-1:2 15 5 2 2 2 4 3 2 4;} _filtered #yiv1064204237 {font-family:Tahoma;panose-1:2 11 6 4 3 5 4 4 2 4;}#yiv1064204237 #yiv1064204237 p.yiv1064204237MsoNormal, #yiv1064204237 li.yiv1064204237MsoNormal, #yiv1064204237 div.yiv1064204237MsoNormal {margin:0in;margin-bottom:.0001pt;font-size:12.0pt;}#yiv1064204237 a:link, #yiv1064204237 span.yiv1064204237MsoHyperlink {color:#0563C1;text-decoration:underline;}#yiv1064204237 a:visited, #yiv1064204237 span.yiv1064204237MsoHyperlinkFollowed {color:#954F72;text-decoration:underline;}#yiv1064204237 span.yiv1064204237EmailStyle17 {color:windowtext;}#yiv1064204237 span.yiv1064204237EmailStyle18 {color:#1F497D;}#yiv1064204237 .yiv1064204237MsoChpDefault {font-size:10.0pt;} _filtered #yiv1064204237 {margin:1.0in 1.0in 1.0in 1.0in;}#yiv1064204237 div.yiv1064204237WordSection1 {}#yiv1064204237 Yep, +1 to Jonathan here – he is 100% correct.   Each input within the form requires an accessible name per the specification, although I think you’ve identified a likely edge-case where compliance may actually have some impact on usability for some users (i.e. screen reader users). However the requirement for the accessible name being conveyed to the Accessibility APIs is for more than just screen readers – for example speech input – and so your text input needs to be labeled somehow.   JF  From: Jonathan Avila [mailto:jon.avila@ssbbartgroup.com] 
Sent: Tuesday, June 7, 2016 1:14 PM
To: WCAG WG <w3c-wai-gl@w3.org>
Subject: RE: Label Association with Input Field Question  Mike, in my opinion you need an aria-label, aria-labelledby, label, or title for the input – having the search role on a parent element or a placeholder is not sufficient.  Jonathan  Jonathan AvilaChief Accessibility Officer
SSB BART Group 
jon.avila@ssbbartgroup.com703.637.8957 (Office) 
Visit us online: Website | Twitter | Facebook | Linkedin | BlogCheck out our Digital Accessibility Webinars!  From: Mike Elledge [mailto:melledge@yahoo.com] 
Sent: Tuesday, June 07, 2016 2:09 PM
To: WCAG WG
Subject: Label Association with Input Field Question  Hi All--  Is it compliant to use an aria role in place of a label for a search field?   This is the code:     <form role="search" class="inLine search" >
    <input type="text" />
    <input type="submit" value="Search" />
  </form>  I want to identify search as a region, but avoid the redundancy of aria-label or a "search" label hidden off-screen. The submit button identifies the purpose visually, and screen readers announce it aurally.  I've considered adding a placeholder attribute, but the consensus is that it is not compliant since it doesn't create an association between the label and input field (even though it is reflected that way in the DOM).  What do you think, is this appropriate?  Thanks!  Mike