large_Crossover Series NFTs.png

medium_Crossover Series NFTs.png

small_Crossover Series NFTs.png

thumbnail_Crossover Series NFTs.png

From Photography to NFT Art: Twisted Digital Landscapes with Nate Hill

From Design System to ‘NFT Design System’: Creating TinyFaces

Neurodiversity and Inclusion: Choosing Kinder Design

medium_652ccf22c8853584bde5553986a4eed0.png

small_652ccf22c8853584bde5553986a4eed0.png

thumbnail_652ccf22c8853584bde5553986a4eed0.png

Web5 is here. Goodbye Web3? TBD.

<p><a href="https://uxplanet.org/understanding-speech-recognition-to-design-better-voice-interfaces-bef36b8614f?source=rss----819cc2aaeee0---4">UX Planet &mdash; Medium</a> | Kore </p>
<blockquote><p>When designing a good voice user interface, it is always advantageous to know how the technology works.</p></blockquote>
<blockquote><p>Knowing what goes on behind the scenes enables you to make design decisions that take into account the current limitations and advantages of the technology.</p></blockquote>
<p><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ChocH_eUxil5eaeXIsd3rw.png"></p>
<h3><strong>Speech recognition technology</strong></h3>
<p>One key component of a <strong>Voice user interfaces(VUI)</strong> is <strong>automated speech recognition (ASR)</strong> that enables users’ speech to be translated into text. There are a number of free and paid services available that provide ASR engines. When choosing an engine, it is important to keep in mind the following two things:</p>
<ol>
<li><strong>Robustness and accuracy of data</strong><br /> As a rule of thumb, the more data the company has, the better it’s speech recognition will be. Incumbent companies are generally good at amassing a large quantity of data.</li>
<li><strong>A good endpoint detection</strong><br /> Endpoint detection refers to how the ASR engine knows when the user has begun or finished speaking. Try to go for a service that provides the best endpoint detection.</li>
</ol>
<p><em>Again, not all ASR tools will have advanced features like N-best lists, end of speech timeouts or the ability to incorporate custom vocabularies. It might be quicker to start with the cheapest ASR tool, however if the recognition accuracy is sub-standard, or the endpoint detection does not work very well, it is going to frustrate your users to eventually give up on the product.</em></p>
<h4><strong>Barge-in</strong></h4>
<p>Barge-In is the ability built into a VUI that allows for the user to interrupt the system anytime during the conversation. The decision to enable this will greatly depend on the type of VUI you are planning. It is advantageous if your VUI is going to say a long list of menu items, or tell a story or generally be verbose. Users might want to interrupt and stop it midway.<br />When deciding on a barge-in strategy, you need to keep in mind whether you want to enable barge-in with anything that the user says, or only using the wake word. Most common VUIs use the latter strategy of using a wake word. When Alexa is playing a song, the user can barge-in anytime to stop playing. Without barge-in, there would be no way to stop playing by using a voice command.</p>
<h4><strong>Timeouts</strong></h4>
<p>VUIs need to know when a user starts speaking as well as when the speech has ended. Knowing when the user stops speaking is known as a timeout. Giving an optimum timeout is critical to a good VUI experience. Think of a video call where the voice of the other person lagged and it was difficult to follow the conversation.<br />There are different conditions at which the ASR engine can decide to timeout:</p>
<ol>
<li><strong>End of speech timeout</strong><br /> Knowing when the user has finished talking, i.e. finished their turn in the conversation is one of the most important characteristics of a good VUI system. This is sometimes referred to as endpoint detection. Giving a response as soon as the user has stopped speaking is unnatural. The system needs to pause for sometime before continuing the conversation. It is a basic conversation etiquette. Some ASR engines allow you to configure this pause, also known as end-of-speech timeout. Using a 1.5 seconds end-of-speech timeout is a good rule of thumb. However, there might be cases when you’d need a longer end-of-speech timeout, such as when saying a long string of characters or numbers. For cases where the user only needs to give a one word response such as a ‘yes’ or a ‘no’, a shorter timeout works fine.</li>
<li><strong>No speech timeout (NSP)</strong><br /> As the name indicates, this timeout is used to detect if there is no speech detected. It is different from an end-of-speech timeout, where there is a concrete beginning and an end to the user speech. This timeout is usually longer at 10 seconds. There are different ways in which these timeouts can be handled ranging from showing the user a list of things or actions that can be done to doing nothing at all.</li>
<li><strong>Too much speech</strong><br /> This is a rare case when the user is talking for too long without any pauses. In most scenarios, you don’t need to handle Too much speech (TMS) timeouts. However if you want to incorporate this then a good rule of thumb is 7–10 seconds at which the system times out.</li>
</ol>
<p>Incorporating timeouts is essential to know when the user has stopped speaking.</p>
<h4><strong>N-best lists</strong></h4>
<p>When a user speaks with the VUI, the speech recognition system returns more than one response to what was said. It assigns a confidence value to each result and usually picks the one that has the highest confidence value. In simple terms, a confidence value is a percentage that indicates how confident the system is about a particular result. For example, when you say “Read me a book,” the system can interpret it as follows:</p>
<ol>
<li>Read me a book : 95% confidence</li>
<li>Reed me a book : 70% confidence</li>
<li>Rid mia boo : 30% confidence</li>
</ol>
<p>If you’ve designed your VUI to read books then the system would pick up the first result.<br />A recognition engine often does not return only one result. It returns an N-best list, which is a list of what it thinks the user might’ve said in the order of likelihood. It is usually the top 5–10 results along with a confidence score.<br />N-best lists are useful in cases where you’ve designed the system to answer in a narrow domain. For example, in a VUI that gives information about animals, when you say “Show me a Badger,” the ASR tool might interpret it as follows:</p>
<ol>
<li>Show me a badge her : 92% confidence</li>
<li>Show me a badger : 89% confidence</li>
</ol>
<p>Since you already know that this VUI is about animal information, it can search for cues for animal names and pick the second result even if it does not have the highest confidence level.<br />Another use of N-best list is in correcting information in case the first answer is not valid.</p>
<h3><strong>Challenges for </strong>Automated speech recognition tools (<strong>ASRT)</strong></h3>
<p>Many studies show that Automated speech recognition tools have an accuracy of more than 90%, however this is under ideal conditions. An ideal condition for an ASR tool is an adult male in a quiet room with a good microphone. Rest assured, most real life conditions are not ideal.</p>
<h4>Noise</h4>
<p>Handling noise is one of the most difficult challenges for ASR engines currently. Noise refers to situations like any noisy environment, television in the background, multiple people talking at the same time or side speech when the user talks to another person while the VUI is listening. Some VUIs can detect noise and ask the user to move to a less noisy environment. However, there’s not much you can do about this apart from waiting for the technology to improve.</p>
<h4>Children</h4>
<p>It is much more difficult for ASR tools to accurately recognize voices of children. Children have higher pitched voices owing to shorter vocal tracts. As yet there is less data to recognize that type of speech. Children often stutter and repeat words which is another challenge for ASR tools. Much like the earlier problem, things are improving.</p>
<h4>Names, spelling and alphanumeric</h4>
<p>It is easier for ASR tools to recognize longer phrases like “yes I will” rather than shorter responses like “yes.” Names, spellings and alphanumeric strings are also tough to recognize and it often makes sense to have a GUI input for these. The name ‘Karan’ is often misinterpreted as ‘Karen.’ Asking the VUI to call Karan might accidentally call the wrong person. Again, the technology is improving.</p>
<h3><strong>User Data Privacy</strong></h3>
<p>When designing voice interfaces, it is important to make sure that you do not store private data unless absolutely necessary. When you store this data, make sure the user is aware and has a choice in denying access. It might be tempting to store conversations and use this information for improving this experience. Even if the device is constantly listening, any data before the user has said the wake word should not be stored or sent to the cloud. Users expect privacy and breaking trust of your users is the worst thing you can do.</p>
<p><strong>References:<br /></strong>1. Being Digital — <a href="https://www.ted.com/speakers/nicholas_negroponte">Nicholas Negroponte</a><br />2. Designing voice user interfaces — <a href="https://www.uxmatters.com/mt/archives/2018/01/designing-voice-user-interfaces.php">Cathy Pearl</a><br />3. Design for Voice Interfaces — <a href="http://www.oreilly.com/pub/au/5366">Laura Klein</a></p>
<p><strong>If you liked this article, please click the 👏 button (once, twice or more). <br />Share to help others find it!</strong></p>
<p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2Fb3e808%3Fas_embed%3Dtrue&amp;dntp=1&amp;url=https%3A%2F%2Fupscri.be%2Fb3e808%2F&#038;image=https%3A%2F%2Fe.enpose.co%2F%3Fkey%3DdRXnS9Gplk%26w%3D700%26h%3D425%26url%3Dhttps%253A%252F%252Fupscri.be%252Fb3e808%252F%253Fenpose&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0"><a href="https://medium.com/media/96d08ab34921bdd17986cb5c0396842f/href">https://medium.com/media/96d08ab34921bdd17986cb5c0396842f/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&amp;referrerSource=full_rss&amp;postId=bef36b8614f" width="1" height="1" alt="stat?event=post.clientViewed&amp;referrerSou"></p>
<hr>
<p><a href="https://uxplanet.org/understanding-speech-recognition-to-design-better-voice-interfaces-bef36b8614f">Understanding speech recognition to design better Voice interfaces</a> was originally published in <a href="https://uxplanet.org">UX Planet</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>


Understanding speech recognition to design better Voice interfaces

Understanding speech recognition to design better Voice interfaces

Top Stories