- From: Patrick H. Lauke <redux@splintered.co.uk>
- Date: Thu, 6 Apr 2017 21:06:15 +0100
- To: public-mobile-a11y-tf@w3.org
On 06/04/2017 17:31, David MacDonald wrote: > Ohhh... it's MUCH better now. Good on Alastair. It is much better for > WCAG than the original. > > - > Active controls in web pages have visible labels that match the > accessible name > > Screen reader users sometimes need extra text in their offscreen label, > which contains instructions, context etc. What about > > - > > If an active control has invisible and visible labels, the invisible > label contains the string of the text for its visible name, as part of, > or in addition to any text specific to its invisible label. Depending on how that's implemented specifically, it may result in that bit of text being announced twice, which is redundant. Say you have <button aria-describedby="foo">Visible label</button> <div class="offscreen-hidden" id="foo">Additional invisible text</div> then screen readers would generally announce the visible label text, followed by the offscreen hidden part. Same for something like <button>Visible label<span class="offscreen-hidden"> additional invisible text</span></button> Requiring authors to always include the visible text in the invisible extra text is possibly not the right approach then. If the intent is to ensure that SRs will also announce the visible label regardless, then probably a better way to phrase it would be that the visible label must always be part of the "accessible name" of the control (with reference to https://www.w3.org/TR/accname-aam-1.1/ ?) P -- Patrick H. Lauke www.splintered.co.uk | https://github.com/patrickhlauke http://flickr.com/photos/redux/ | http://redux.deviantart.com twitter: @patrick_h_lauke | skype: patrick_h_lauke
Received on Thursday, 6 April 2017 20:06:41 UTC