W3C home > Mailing lists > Public > public-wai-cc@w3.org > February 2021

Re: Clarifying speech recognition vs. voice recognition in Style Guide

From: Ralph Swick <swick@w3.org>
Date: Wed, 3 Feb 2021 08:39:22 -0500
To: Shawn Henry <shawn@w3.org>
Cc: "kim@redstartsystems.com" <kim@redstartsystems.com>, "EOWG (E-mail)" <w3c-wai-eo@w3.org>, WAI Coordination Call <public-wai-cc@w3.org>, Katie Haritos-Shea <ryladog@gmail.com>
Message-ID: <a07f3f1d-4137-04bc-760e-611ec3eae31c@w3.org>


On 2021-02-02 05:58 PM, Shawn Henry wrote:
> Hi Katie,
> 
> Thanks for the input.
> 
> I don't see a need to differentiate non-accessibility tech in this 
> context. Maybe I'm missing something?
> 
> afaik, Most of those systems use "speech recognition" to recognize 
> words. Only a few might use "voice recognition" to identify the speaker. 
> And speech output is different.
> 
> I've updated the info to make the scope more clear:
>      https://www.w3.org/WAI/EO/wiki/Style#speech-recognition
> 
> Does that help clarify? Or, am I still not getting the point?

The sentence I currently see is

   ""voice recognition" is different — it's about identifying who the 
speaker is, not the words they're saying."

I believe this sentence would be more accurate if it were to say "... 
not necessarily the words they're saying."

The Wikipedia disambiguation page is helpful in this regard:

   https://en.wikipedia.org/wiki/Voice_recognition

It suggests the distinction made by the current sentence is "speaker 
recognition" vs. "speech recognition".  This English usage might be more 
subtle that is necessary in the WAI context, but if this is indeed what 
is meant in the WAI Style guide then I suggest it would be useful to 
adopt the Wikipedia phrasing  ala "it's about recognizing the speaker, 
not necessarily the words they are using."

-Ralph

> Best,
> ~Shawn
> 
> 
> On 02-Feb-21 3:50 PM, Katie Haritos-Shea wrote:
>> Yeah, but what about non-accessibility related speech recognition 
>> software, such as what is part of SIRI, Cortana, etc. and any voice 
>> enabled UI - who use both of the systems that were originally AT - 
>> voice recognition and screen reading speech software? How do we 
>> differentiate there?
>>
>> ** katie **
>>
>> *Katie Haritos-Shea****
>> **Principal ICT Accessibility Architect*
>>
>> *
>> **Senior Product Manager/Compliance/Accessibility **SME**,
>> **Core Merchant Framework UX, Clover*
>>
>> *
>> **W3C Advisory Committee Member and Representative for Knowbility *
>>
>> *
>> *
>>
>> *WCAG/Section 508/ADA/AODA/QA/FinServ/FinTech/Privacy,****IAAP 
>> CPACC+WAS = **CPWA* 
>> <http://www.accessibilityassociation.org/cpwacertificants>
>>
>> *Cell: **703-371-5545 <tel:703-371-5545>**|****_ryladog@gmail.com 
>> <mailto:ryladog@gmail.com>_**|**Seneca, SC **|****LinkedIn Profile 
>> <http://www.linkedin.com/in/katieharitosshea/>*
>>
>>
>> People may forget exactly what it was that you said or did, but they 
>> will never forget how you made them feel.......
>>
>> Our scars remind us of where we have been........they do not have to 
>> dictate where we are going.
>>
>>
>>
>>
>>
>>
>> On Tue, Feb 2, 2021 at 4:37 PM Andrew Arch <andrew@intopia.digital> 
>> wrote:
>>
>>     Agree completely Shawn, and good for WAI to make the clear 
>> distinction.____
>>
>>     __ __
>>
>>     ‘voice recognition’ is being used increasingly for security to 
>> identify the individual based on their voice ‘print’.____
>>
>>     __ __
>>
>>     Andrew____
>>
>>     ______________
>>
>>     Andrew Arch
>>     Intopia____
>>
>>     __ __
>>
>>     __ __
>>
>>     __ __
>>
>>     *From:*Kim Patch <kim@redstartsystems.com 
>> <mailto:kim@redstartsystems.com>>
>>     *Sent:* Wednesday, 3 February 2021 5:00 AM
>>     *To:* Joshue O Connor <joconnor@w3.org <mailto:joconnor@w3.org>>; 
>> Bakken, Brent <Brent.Bakken@Pearson.com>
>>     *Cc:* Shawn Henry <shawn@w3.org <mailto:shawn@w3.org>>; EOWG 
>> (E-mail) <w3c-wai-eo@w3.org <mailto:w3c-wai-eo@w3.org>>; WAI 
>> Coordination Call <public-wai-cc@w3.org <mailto:public-wai-cc@w3.org>>
>>     *Subject:* Re: Clarifying speech recognition vs. voice recognition 
>> in Style Guide____
>>
>>     __ __
>>
>>     Yes, that's the right distinction.
>>
>>     I also agree that it's important that we get on the same page 
>> about this. I've seen them conflated many times – I think we can help 
>> by making sure to be clear about the distinction.
>>
>>     Cheers,
>>     Kim____
>>
>>     On 2/2/2021 12:29 PM, Joshue O Connor wrote:____
>>
>>         Hi all,
>>
>>         Interesting point and an important distinction.
>>
>>         In the wild the two will be conflated IMO, for better or 
>> worse. It could be one of those things that the sooner the 'experts' 
>> get on the same page about, the better.
>>
>>         I'm curious what Kim thinks?
>>
>>         Thanks
>>
>>         Josh
>>
>>
>>         ____
>>
>>             Bakken, Brent <mailto:Brent.Bakken@Pearson.com>____
>>
>>             Tuesday 2 February 2021 17:07____
>>
>>             I would agree with this distinction.
>>
>>             -----Original Message-----
>>             From: Shawn Henry <shawn@w3.org> <mailto:shawn@w3.org>
>>             Sent: Tuesday, February 2, 2021 8:44 AM
>>             To: EOWG (E-mail) <w3c-wai-eo@w3.org> 
>> <mailto:w3c-wai-eo@w3.org>; WAI Coordination Call 
>> <public-wai-cc@w3.org> <mailto:public-wai-cc@w3.org>
>>             Cc: Kim Patch <kim@redstartsystems.com> 
>> <mailto:kim@redstartsystems.com>
>>             Subject: Clarifying speech recognition vs. voice 
>> recognition in Style Guide
>>
>>             Hi folks,
>>
>>             Here is a draft update to the WAI Style Guide[1]:
>>
>>             "speech recognition" is for speech-to-text (SST), and 
>> usually what we're talking about for accessibility.
>>             "voice recognition" is different; it's about identifying 
>> the speaker, not what they're saying.
>>
>>             (For background, search the Web for "speech recognition 
>> voice recognition difference")
>>
>>             Please let me know if you disagree or have edit suggestions.
>>
>>             Thanks!
>>             ~Shawn
>>
>>             [1] currently at the end of 
>> https://urldefense.proofpoint.com/v2/url?u=https-3A__www.w3.org_WAI_EO_wiki_Style-23other-5Fwords-5Fand-5Fphrases&d=DwICaQ&c=0YLnzTkWOdJlub_y7qAx8Q&r=v-L6X-ScaY5UKb-F-_zcuXdbPw2UYK_gaTG8R5d9h7U&m=lT0RkzKPWViwYA0MZWTXqn8uDXjrBrrbQtLkZhkL4MM&s=B9oYblo0mWxzn9VV3FGaJexvPlU9zTrsI41fDM4ORb8&e= 
>> <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.w3.org_WAI_EO_wiki_Style-23other-5Fwords-5Fand-5Fphrases&d=DwICaQ&c=0YLnzTkWOdJlub_y7qAx8Q&r=v-L6X-ScaY5UKb-F-_zcuXdbPw2UYK_gaTG8R5d9h7U&m=lT0RkzKPWViwYA0MZWTXqn8uDXjrBrrbQtLkZhkL4MM&s=B9oYblo0mWxzn9VV3FGaJexvPlU9zTrsI41fDM4ORb8&e=> 
>> ____
>>
>>             Shawn Henry <mailto:shawn@w3.org>____
>>
>>             Tuesday 2 February 2021 14:43____
>>
>>             Hi folks,
>>
>>             Here is a draft update to the WAI Style Guide[1]:
>>
>>             "speech recognition" is for speech-to-text (SST), and 
>> usually what we're talking about for accessibility.
>>             "voice recognition" is different; it's about identifying 
>> the speaker, not what they're saying.
>>
>>             (For background, search the Web for "speech recognition 
>> voice recognition difference")
>>
>>             Please let me know if you disagree or have edit suggestions.
>>
>>             Thanks!
>>             ~Shawn
>>
>>             [1] currently at the end of 
>> https://www.w3.org/WAI/EO/wiki/Style#other_words_and_phrases 
>> <https://www.w3.org/WAI/EO/wiki/Style#other_words_and_phrases> ____
>>
>>         __ __
>>
>>
>>         --         Emerging Web Technology Specialist/Accessibility 
>> (WAI/W3C) ____
>>
>>     __ __
>>
>>     --     ___________________________________________________
>>
>>     Kimberly Patch
>>     (617) 325-3966
>>     kim@scriven.com <mailto:kim@scriven.com>
>>
>>     www.redstartsystems.com <http://www.redstartsystems.com>
>>     - making speech fly
>>
>>     PatchonTech.com <http://www.linkedin.com/in/kimpatch>
>>     @PatchonTech
>>     www.linkedin.com/in/kimpatch <http://www.linkedin.com/in/kimpatch>
>>     ___________________________________________________ ____
>>
> 
Received on Wednesday, 3 February 2021 13:39:30 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 3 February 2021 13:39:31 UTC