E-mail List Archives

You are here: Home > Community > E-mail List Archives > View Message

Re: Form fields in a sentence

From: Patrick H. Lauke
Date: Sep 7, 2023 11:10AM

Next message: Nick Bromley: "Re: Providing accessible names with "</a></li> <li><strong>Previous message:</strong> <a href="mail_message?id=49409">Mark Magennis: "Re: Providing accessible names with <title>"</a></li> <li><strong>Next message in Thread:</strong> <a href="mail_message?id=49412">glen walker: "Re: Form fields in a sentence"</a></li> <li><strong>Previous message in Thread:</strong> <a href="mail_message?id=49406">Mark Magennis: "Re: Form fields in a sentence"</a></li> <li><a href="mail_thread?thread=10861">View all messages in this Thread</a></li> </ul> <hr> On 07/09/2023 16:46, Mark Magennis wrote:<br /> > Suppose I have a page where two text input fields are presented within a sentence of text (and I can't tell the designer to do this a different way). For example, suppose the sentence was like this, where the fields are shown as "[input]":<br /> > <br /> > My favourite country is [input] and favourite sport is [input].<br /> > <br /> > It seems to me that appropriate names for these two fields would be "favourite country" and "favourite sport".<br /> > <br /> > Could the intervening text, "My favourite country is" and "and favourite sport is", be given aria-hidden="true", leaving just the two fields exposed to AT? Would there be any downside to doing this? Or is it important that the visible text is exposed? Or alternatively, should just "My", "is", "and", and "is" have aria-hidden so that the text labels exposed to AT are identical to the field names?<br /> <br /> Non-SR users are able to read the whole thing (once filled in) as a <br /> completely formed sentence. The same should be possible for SR users, so <br /> I wouldn't hide it from them.<br /> <br /> > Another question is, if I make "favourite country" and "favourite sport" bold to support voice activation users, would that pass WCAG SC 2.5.3 Label in Name in your opinion?<br /> <br /> I'd say so, yes. And if those words weren't bold, I'd actually have a <br /> hard time deciding for definitive what the pass/fail cut-off point there <br /> would be (as the SC is eminently vague for things that don't fall under <br /> a fairly limited "there's a visible label" scenario).<br /> <br /> P<br /> -- <br /> Patrick H. Lauke<br /> <br /> https://www.splintered.co.uk/ | https://github.com/patrickhlauke<br /> https://flickr.com/photos/redux/ | https://www.deviantart.com/redux<br /> https://mastodon.social/@patrick_h_lauke | skype: patrick_h_lauke <hr> <ul> <li><strong>Next message:</strong> <a href="mail_message?id=49411">Nick Bromley: "Re: Providing accessible names with <title>"</a></li> <li><strong>Previous message:</strong> <a href="mail_message?id=49409">Mark Magennis: "Re: Providing accessible names with <title>"</a></li> <li><strong>Next message in Thread:</strong> <a href="mail_message?id=49412">glen walker: "Re: Form fields in a sentence"</a></li> <li><strong>Previous message in Thread:</strong> <a href="mail_message?id=49406">Mark Magennis: "Re: Form fields in a sentence"</a></li> <li><a href="mail_thread?thread=10861&id=49410#49410">View all messages in this Thread</a></li> </ul> </div> </article>  <aside id="articlemeta"> </aside> </main> <footer> <div id="footerresources"> <div class="footerblock"> <h2 id="copyright">©2024 WebAIM</h2> <p id="contact">Institute for Disability Research, Policy, and Practice<br> Utah State University<br> 6807 Old Main Hill<br> Logan, UT 84322-6807<br> <a class="phone" href="tel:4357977024">435.797.7024</a></p> <div id="checkpage"> <h2>Check Your Accessibility</h2> <form action="https://wave.webaim.org/report" novalidate> <label for="waveurl">Web site address:</label> <input type="url" id="waveurl" name="url" title="Web site address"> <input type="submit" value="WAVE"> </form> </div> </div> <div class="footerblock"> <h2 id="blog">From the Blog</h2> <ul><li><a href="/blog/severity-ratings/">Using Severity Ratings to Prioritize Web Accessibility Remediation</a></li><li><a href="/blog/25-tips/">25 Accessibility Tips to Celebrate 25 Years</a></li><li><a href="/blog/celebrating-webaims-25th-anniversary/">Celebrating WebAIM's 25th Anniversary</a></li><li><a href="/blog/introducing-ncademi/">Introducing NCADEMI: The National Center on Accessible Digital Educational Materials & Instruction </a></li></ul> </div> <div class="footerblock"> <h2 id="popular">Popular Resources</h2> <ul> <li><a href="/training/virtual">WebAIM Training</a></li> <li><a href="/standards/wcag/checklist">WCAG 2 Checklist</a></li> <li><a href="/newsletter">WebAIM Monthly Newsletter</a></li> <li><a href="/resources/contrastchecker">Color Contrast Checker</a></li> <li><a href="/resources/designers/">Web Accessibility for Designers</a></li> <li><a href="http://wave.webaim.org/">WAVE Web Accessibility Evaluation Tool</a></li> </ul> </div> <div id="footerlinks"> <ul> <li><a id="footercontact" href="/contact">Contact</a></li> <li><a id="footerabout" href="/about">About</a></li> <li><a id="footerrss" href="/community/rss">RSS Feeds</a></li> <li><a id="footertwit" href="http://twitter.com/webaim">Twitter</a></li> <li><a id="footercopyright" href="/copyright">Copyright & Terms of Use</a></li> </ul> </div> <div class="clear"></div> </div> </footer> </body> </html>