Re: The two speech SCs

The intent of this SC is to help Speech engines such as Dragon where they
try to say "press start" button, but the offscreen label is "begin" so
nothing happens.

<button aria-label="begin"> Start</button>

I know it's a dumb thing to code like that, but it happens enough that
Dragon users get frustrated.

I don't think of aria-describedby as a label, I think of it as helper text.
(ACCDESCRIPTION vs ACCNAME) It would not be triggered by Dragon. So in your
example, if the speech user said "Additional invisible text" nothing would
happen. They would say "Visible Label" and it would accurately say the name.

However, I think your concern points out that we'll need to manage that in
the understanding, to well explain the intent, and to make it clear it is
not for screen readers and link to best practices for offscreen helper text
using aria-describedby etc...

Cheers,
David MacDonald



*Can**Adapt* *Solutions Inc.*

Tel:  613.235.4902

LinkedIn
<http://www.linkedin.com/in/davidmacdonald100>

twitter.com/davidmacd

GitHub <https://github.com/DavidMacDonald>

www.Can-Adapt.com <http://www.can-adapt.com/>



*  Adapting the web to all users*
*            Including those with disabilities*

If you are not the intended recipient, please review our privacy policy
<http://www.davidmacd.com/disclaimer.html>

On Thu, Apr 6, 2017 at 4:06 PM, Patrick H. Lauke <redux@splintered.co.uk>
wrote:

> 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
>
>