[26-Feb-2026 00:31:13 America/Chicago] PHP Warning: Use of undefined constant ABSPATH - assumed 'ABSPATH' (this will throw an Error in a future version of PHP) in /home/touchmob/crazyleafdesign.com/blog/wp-content/plugins/thrive-visual-editor/thrive-dashboard/inc/app-notification/classes/DbMigration.php on line 2 [26-Feb-2026 00:31:13 America/Chicago] PHP Warning: require_once(ABSPATHwp-admin/includes/upgrade.php): failed to open stream: No such file or directory in /home/touchmob/crazyleafdesign.com/blog/wp-content/plugins/thrive-visual-editor/thrive-dashboard/inc/app-notification/classes/DbMigration.php on line 2 [26-Feb-2026 00:31:13 America/Chicago] PHP Fatal error: require_once(): Failed opening required 'ABSPATHwp-admin/includes/upgrade.php' (include_path='.:/opt/cpanel/ea-php74/root/usr/share/pear') in /home/touchmob/crazyleafdesign.com/blog/wp-content/plugins/thrive-visual-editor/thrive-dashboard/inc/app-notification/classes/DbMigration.php on line 2 [01-Mar-2026 07:45:51 America/Chicago] PHP Warning: Use of undefined constant ABSPATH - assumed 'ABSPATH' (this will throw an Error in a future version of PHP) in /home/touchmob/crazyleafdesign.com/blog/wp-content/plugins/thrive-visual-editor/thrive-dashboard/inc/app-notification/classes/DbMigration.php on line 2 [01-Mar-2026 07:45:51 America/Chicago] PHP Warning: require_once(ABSPATHwp-admin/includes/upgrade.php): failed to open stream: No such file or directory in /home/touchmob/crazyleafdesign.com/blog/wp-content/plugins/thrive-visual-editor/thrive-dashboard/inc/app-notification/classes/DbMigration.php on line 2 [01-Mar-2026 07:45:51 America/Chicago] PHP Fatal error: require_once(): Failed opening required 'ABSPATHwp-admin/includes/upgrade.php' (include_path='.:/opt/cpanel/ea-php74/root/usr/share/pear') in /home/touchmob/crazyleafdesign.com/blog/wp-content/plugins/thrive-visual-editor/thrive-dashboard/inc/app-notification/classes/DbMigration.php on line 2 [01-Mar-2026 18:48:26 America/Chicago] PHP Warning: Use of undefined constant ABSPATH - assumed 'ABSPATH' (this will throw an Error in a future version of PHP) in /home/touchmob/crazyleafdesign.com/blog/wp-content/plugins/thrive-visual-editor/thrive-dashboard/inc/app-notification/classes/DbMigration.php on line 2 [01-Mar-2026 18:48:26 America/Chicago] PHP Warning: require_once(ABSPATHwp-admin/includes/upgrade.php): failed to open stream: No such file or directory in /home/touchmob/crazyleafdesign.com/blog/wp-content/plugins/thrive-visual-editor/thrive-dashboard/inc/app-notification/classes/DbMigration.php on line 2 [01-Mar-2026 18:48:26 America/Chicago] PHP Fatal error: require_once(): Failed opening required 'ABSPATHwp-admin/includes/upgrade.php' (include_path='.:/opt/cpanel/ea-php74/root/usr/share/pear') in /home/touchmob/crazyleafdesign.com/blog/wp-content/plugins/thrive-visual-editor/thrive-dashboard/inc/app-notification/classes/DbMigration.php on line 2 [06-Mar-2026 13:14:53 America/Chicago] PHP Warning: Use of undefined constant ABSPATH - assumed 'ABSPATH' (this will throw an Error in a future version of PHP) in /home/touchmob/crazyleafdesign.com/blog/wp-content/plugins/thrive-visual-editor/thrive-dashboard/inc/app-notification/classes/DbMigration.php on line 2 [06-Mar-2026 13:14:53 America/Chicago] PHP Warning: require_once(ABSPATHwp-admin/includes/upgrade.php): failed to open stream: No such file or directory in /home/touchmob/crazyleafdesign.com/blog/wp-content/plugins/thrive-visual-editor/thrive-dashboard/inc/app-notification/classes/DbMigration.php on line 2 [06-Mar-2026 13:14:53 America/Chicago] PHP Fatal error: require_once(): Failed opening required 'ABSPATHwp-admin/includes/upgrade.php' (include_path='.:/opt/cpanel/ea-php74/root/usr/share/pear') in /home/touchmob/crazyleafdesign.com/blog/wp-content/plugins/thrive-visual-editor/thrive-dashboard/inc/app-notification/classes/DbMigration.php on line 2 [08-Mar-2026 11:47:41 America/Chicago] PHP Warning: Use of undefined constant ABSPATH - assumed 'ABSPATH' (this will throw an Error in a future version of PHP) in /home/touchmob/crazyleafdesign.com/blog/wp-content/plugins/thrive-visual-editor/thrive-dashboard/inc/app-notification/classes/DbMigration.php on line 2 [08-Mar-2026 11:47:41 America/Chicago] PHP Warning: require_once(ABSPATHwp-admin/includes/upgrade.php): failed to open stream: No such file or directory in /home/touchmob/crazyleafdesign.com/blog/wp-content/plugins/thrive-visual-editor/thrive-dashboard/inc/app-notification/classes/DbMigration.php on line 2 [08-Mar-2026 11:47:41 America/Chicago] PHP Fatal error: require_once(): Failed opening required 'ABSPATHwp-admin/includes/upgrade.php' (include_path='.:/opt/cpanel/ea-php74/root/usr/share/pear') in /home/touchmob/crazyleafdesign.com/blog/wp-content/plugins/thrive-visual-editor/thrive-dashboard/inc/app-notification/classes/DbMigration.php on line 2 [20-Mar-2026 17:37:48 America/Chicago] PHP Warning: Use of undefined constant ABSPATH - assumed 'ABSPATH' (this will throw an Error in a future version of PHP) in /home/touchmob/crazyleafdesign.com/blog/wp-content/plugins/thrive-visual-editor/thrive-dashboard/inc/app-notification/classes/DbMigration.php on line 2 [20-Mar-2026 17:37:48 America/Chicago] PHP Warning: require_once(ABSPATHwp-admin/includes/upgrade.php): failed to open stream: No such file or directory in /home/touchmob/crazyleafdesign.com/blog/wp-content/plugins/thrive-visual-editor/thrive-dashboard/inc/app-notification/classes/DbMigration.php on line 2 [20-Mar-2026 17:37:48 America/Chicago] PHP Fatal error: require_once(): Failed opening required 'ABSPATHwp-admin/includes/upgrade.php' (include_path='.:/opt/cpanel/ea-php74/root/usr/share/pear') in /home/touchmob/crazyleafdesign.com/blog/wp-content/plugins/thrive-visual-editor/thrive-dashboard/inc/app-notification/classes/DbMigration.php on line 2 [20-Mar-2026 17:37:53 America/Chicago] PHP Warning: Use of undefined constant ABSPATH - assumed 'ABSPATH' (this will throw an Error in a future version of PHP) in /home/touchmob/crazyleafdesign.com/blog/wp-content/plugins/thrive-visual-editor/thrive-dashboard/inc/app-notification/classes/DbMigration.php on line 2 [20-Mar-2026 17:37:53 America/Chicago] PHP Warning: require_once(ABSPATHwp-admin/includes/upgrade.php): failed to open stream: No such file or directory in /home/touchmob/crazyleafdesign.com/blog/wp-content/plugins/thrive-visual-editor/thrive-dashboard/inc/app-notification/classes/DbMigration.php on line 2 [20-Mar-2026 17:37:53 America/Chicago] PHP Fatal error: require_once(): Failed opening required 'ABSPATHwp-admin/includes/upgrade.php' (include_path='.:/opt/cpanel/ea-php74/root/usr/share/pear') in /home/touchmob/crazyleafdesign.com/blog/wp-content/plugins/thrive-visual-editor/thrive-dashboard/inc/app-notification/classes/DbMigration.php on line 2 [27-Mar-2026 14:07:52 America/Chicago] PHP Warning: Use of undefined constant ABSPATH - assumed 'ABSPATH' (this will throw an Error in a future version of PHP) in /home/touchmob/crazyleafdesign.com/blog/wp-content/plugins/thrive-visual-editor/thrive-dashboard/inc/app-notification/classes/DbMigration.php on line 2 [27-Mar-2026 14:07:52 America/Chicago] PHP Warning: require_once(ABSPATHwp-admin/includes/upgrade.php): failed to open stream: No such file or directory in /home/touchmob/crazyleafdesign.com/blog/wp-content/plugins/thrive-visual-editor/thrive-dashboard/inc/app-notification/classes/DbMigration.php on line 2 [27-Mar-2026 14:07:52 America/Chicago] PHP Fatal error: require_once(): Failed opening required 'ABSPATHwp-admin/includes/upgrade.php' (include_path='.:/opt/cpanel/ea-php74/root/usr/share/pear') in /home/touchmob/crazyleafdesign.com/blog/wp-content/plugins/thrive-visual-editor/thrive-dashboard/inc/app-notification/classes/DbMigration.php on line 2 [29-Mar-2026 10:21:48 America/Chicago] PHP Warning: Use of undefined constant ABSPATH - assumed 'ABSPATH' (this will throw an Error in a future version of PHP) in /home/touchmob/crazyleafdesign.com/blog/wp-content/plugins/thrive-visual-editor/thrive-dashboard/inc/app-notification/classes/DbMigration.php on line 2 [29-Mar-2026 10:21:48 America/Chicago] PHP Warning: require_once(ABSPATHwp-admin/includes/upgrade.php): failed to open stream: No such file or directory in /home/touchmob/crazyleafdesign.com/blog/wp-content/plugins/thrive-visual-editor/thrive-dashboard/inc/app-notification/classes/DbMigration.php on line 2 [29-Mar-2026 10:21:48 America/Chicago] PHP Fatal error: require_once(): Failed opening required 'ABSPATHwp-admin/includes/upgrade.php' (include_path='.:/opt/cpanel/ea-php74/root/usr/share/pear') in /home/touchmob/crazyleafdesign.com/blog/wp-content/plugins/thrive-visual-editor/thrive-dashboard/inc/app-notification/classes/DbMigration.php on line 2 {"id":27895,"date":"2018-12-11T15:53:11","date_gmt":"2018-12-11T07:53:11","guid":{"rendered":"https:\/\/www.crazyleafdesign.com\/blog\/?p=27895"},"modified":"2018-12-11T15:54:09","modified_gmt":"2018-12-11T07:54:09","slug":"the-rise-of-voice-ux-and-how-it-affects-web-design","status":"publish","type":"post","link":"https:\/\/www.crazyleafdesign.com\/blog\/the-rise-of-voice-ux-and-how-it-affects-web-design\/","title":{"rendered":"The Rise of Voice UX and How it Affects Web Design"},"content":{"rendered":"
User interfaces (UI) are things we take for granted these days. In fact, we often don\u2019t notice it unless it\u2019s poorly executed.<\/p>\n
<\/p>\n
If you\u2019ve ever been victimized by confusing kiosks or ATMs, difficult to navigate websites, or apps that don\u2019t work, then you\u2019ve experienced how bad UI can make or break the success of a product\/service.<\/p>\n
<\/p>\n
With the rise of touch screen technologies and smartphones, we\u2019re more exposed than ever to evolving UIs. A new trend, which evolved from graphic UIs (as seen in the screens we surround ourselves with), is voice UI.<\/p>\n
\u00a0<\/strong><\/p>\n Similar to how a graphic UI allows you to visually interact and input commands into your smartphone, a voice UI<\/strong> allows a person to interact with speech applications or programs using their voice.<\/p>\n <\/p>\n If you\u2019ve ever heard of or talked to Siri or Cortana, you\u2019ve already interacted with a voice UI. In these cases, the voice UI was the technology that allowed you to \u201ccommand\u201d your smartphone or personal computer to do specific tasks for you.<\/p>\n <\/p>\n Other popular examples you may be familiar with are the fictional Computer from the Star Trek series (not-so fictional now), or home devices such as Google Home or Amazon\u2019s Alexa.<\/p>\n \u00a0<\/strong><\/p>\n \u00a0<\/strong><\/p>\n According to a report by Alpine in 2017<\/a>, 1.7 million voice-first devices were shipped out to consumers in 2015. By 2016, this number had exploded to 6.5 million devices.<\/p>\n <\/p>\n Technology has made voice UIs more common and popular, as being able to make commands without having to use your hands or eyes has many valuable, practical, and accessible applications.<\/p>\n <\/p>\n According to Amazon<\/a>, there are four trends that are contributing to the rise of voice UIs:<\/p>\n <\/p>\n <\/p>\n In addition to this, RedStagFulfillment, backed by different studies, predicts that artificial intelligence<\/a> (specifically, Voice UI and chatbots) will help bring to ecommerce the personalized and engaging customer experience that only brick-and-mortar shops have achieved so far,<\/p>\n <\/p>\n <\/p>\n If voice UIs are on the rise, does this mean that other UIs will be replaced? Not necessarily.<\/p>\n <\/p>\n Although trends show that voice is growing in popularity, technology has always sought to improve upon itself.<\/p>\n <\/p>\n With this in mind, it\u2019s apt to assume that while voice will become more commonplace, it will also grow and integrate with current technologies rather than replace them. This also means that current technologies will need to adapt to accommodate voice UIs.<\/p>\n <\/p>\n \u00a0<\/strong><\/p>\n One of the technologies that is adopting voice UI is web design<\/a>. As a crucial element in any brand\u2019s marketing plan,<\/a> your web design<\/a> would lag behind competitors if you do not start including voice in their design arsenal.<\/p>\n <\/p>\n Among the ways voice UI will affect your site\u2019s interface, include:<\/p>\n <\/p>\n <\/p>\n For voice UIs to work successfully alongside web design<\/a>, designers have to be purposeful in the words that they choose.<\/p>\n <\/p>\n While graphic UIs can rely on visual cues, colors, and layouts to convey a message or guide users, voice UIs can only rely on words. Hence, designers have to not only design but also write for their target audience.<\/p>\n <\/p>\n Vocabulary, tone of voice, and understandability are some of the important factors that designers must keep in mind. Remember that users on voice UIs will not be looking at a screen to read text, but will rather be hearing text being read out loud to them.<\/p>\n <\/p>\n For example, while standard graphic user experiences<\/a> espouse following a standard style guide to fit a brand, voice user experience designers can follow this advice by making sure the style of writing is consistent.<\/p>\n <\/p>\n <\/p>\n As mentioned previously, while graphic UIs have visual aids to guide users, voice UIs do not. Instead, they rely on voice commands.<\/p>\n <\/p>\n Generally for this to work, these voice commands have to be standard and easy to remember. However, before you can even set commands, you have to understand what your users want to be able to do.<\/p>\n <\/p>\n For example, the general public using a voice UI will usually use it for everyday commands, such as checking the weather or searching for a place. Hence, they will need an interface that\u2019s easy to use, conversational, provides feedback, and can guide users.<\/p>\n <\/p>\n On the other hand, voice UIs for \u201cpower users\u201d\u2014those who use the technology for specific purposes such as workflow\u2014would need an interface that emphasizes productivity and efficiency.<\/p>\n <\/p>\n \u00a0<\/strong><\/p>\n It is worth noting that because word choice and user intent matter, you must also be able to adapt to when these change.<\/p>\n <\/p>\n In addition, because voice UIs and experiences are still growing and changing, you have to be ready to adapt and innovate to maximize its potential. The key to this is to always keep your users\u2019 intent at the core of the design process. As voice UIs and experiences advance, it\u2019s important that you stay ahead of the curve, and not behind it.<\/p>\n \u00a0<\/strong><\/p>\n <\/p>\n Once you have user intent down, you can now design your voice UI as a brand or personality.<\/p>\n <\/p>\n In order to avoid having users feel like they\u2019re speaking with a robot, interactions have to be unique. A user seeking academic information would likely trust a reply given in a mature, professional voice, while another listening to directions might appreciate an easy-going, conversational voice.<\/p>\n <\/p>\n You should also consider allowing users to choose which type of voice they would like to use with their interface.<\/p>\n <\/p>\n <\/p>\n Staying ahead of the curve means not only preparing future design work to accommodate voice UIs and experiences, but also adjusting what you already have.<\/p>\n <\/p>\n Here are some ways you can adapt to the growth of voice UIs:<\/p>\n <\/p>\n <\/p>\n Voice UIs are most likely set to integrate with current technologies rather than replace them. While being able to input commands without having to free up your hands or eyes is convenient, it will not replace graphic UIs.<\/p>\n <\/p>\n Thus, one way to adapt to the growth of voice UIs is to become multi-modal<\/a> for different types of information.<\/p>\n <\/p>\n Not only does this provide users with options, it also allows for the input and output of information in the most convenient methods available to the user as possible. An example would be navigating apps that, aside from presenting a visual map, also give verbal directions.<\/p>\n <\/p>\n <\/p>\n Another way to adapt to voice UIs is to invest in web-speech APIs.<\/p>\n <\/p>\n APIs, or application program interfaces<\/a>, set how software components interact with one another. A web-speech API would allow websites to \u201ctalk\u201d to you, but also listen to you as well.<\/p>\n <\/p>\n Some uses are: dictation, wherein a user speaks and the application converts this to text or vice versa; voice control, wherein a user can use their voice to find their way around a website; and translation.<\/p>\n <\/p>\n However, the limitation here is the need for a constant internet connection for verification, and offline capabilities are lacking.<\/p>\n <\/p>\n \u00a0<\/strong><\/p>\n Finally it\u2019s time to design and implement.<\/p>\n <\/p>\n <\/p>\n <\/p>\n <\/p>\n <\/p>\n <\/p>\n Now that you have an idea of what voice UIs and experiences are and how they relate to current web design, you should have a good grasp of how to adapt to accommodate voice in your website. Keep reading to stay ahead of the game, and be at the forefront of potential benefits of this emerging trend.<\/p>\n <\/p>\n <\/p>\n","protected":false},"excerpt":{"rendered":" User interfaces (UI) are things we take for granted these days. In fact, we often don\u2019t notice it unless it\u2019s poorly executed. If you\u2019ve ever been victimized by confusing kiosks or ATMs, difficult to navigate websites, or apps that don\u2019t work, then you\u2019ve experienced how bad UI can make or break the success of […] More<\/a><\/p>\n","protected":false},"author":1,"featured_media":27899,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[59],"tags":[2471,1136],"adace-sponsor":[],"class_list":{"0":"post-27895","1":"post","2":"type-post","3":"status-publish","4":"format-standard","5":"has-post-thumbnail","7":"category-web-design","8":"tag-voice-ux","9":"tag-web-design-2"},"acf":[],"yoast_head":"\nWhat Is A Voice User Interface?<\/h1>\n
<\/p>\nThe Growing Popularity of Voice User Interfaces<\/h1>\n

\n
What This Means for UX Web Design<\/h1>\n
The Impact of Voice in Web Design<\/h1>\n
The Need To Be Deliberate With Words<\/h2>\n
Finding Out What Your Users Want To Do<\/h2>\n
Adaptability<\/h2>\n
Engagement and Personalization<\/h2>\n
Adapting To The Growth Of Voice User Interfaces<\/h1>\n
Moving Toward Multi-Modal Designs<\/h2>\n
Web-Speech API<\/h2>\n
Designing and Implementing Voice User Experiences<\/h2>\n
\n
\n
\n
\n
\n