MyersDimitri&RouleauGrace-DTC478

<center>[[Home|Home]]|[[Audio|Audio]]|[[Video|Video]]|[[Written|Written]]|[[Sources|Sources]]|[[DIY|Project]]|[[Reflection|Reflection]]</center> <center> <iframe width="600" height="500" src="https://dtc-wsuv.org/dmyers19/DTC478_FinalAudio.mp4" frameborder="0" allow="accelerometer; autoplay; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe> </center> The purpose of this video is to give a brief overhead of COIK. It is important for usability design that content can reach as many means of communication as possible to reach as many people as possible. We wanted to do a video so that we could express our voice. The writing allows us to share information with those who can see and read, but the video allows us to extend that to those who may have reading or visual impairments. Additionally, the sources that were used will also be available to our audience along with a small project for you to test your newly learned skills at the end.

<center>[[Home|Home]]|[[Audio|Audio]]|[[Video|Video]]|[[Written|Written]]|[[Sources|Sources]]|[[DIY|Project]]|[[Reflection|Reflection]]</center> In a video on YouTube that came from <a href="https://99percentinvisible.org/article/norman-doors-dont-know-whether-push-pull-blame-design/">99% invisible</a> on Norman Doors. These problems often stem from some semblance of COIK. Without context for each type of door many users result in simply pushing or pulling and can become frustrated if they make the wrong choice. As a designer for Usability it is essential to clarify for the users how it would work. In the case of a door, a simple sign stating "Push to open" could leave the users feeling empowered. <iframe width="560" height="315" src="https://www.youtube.com/embed/yY96hTb8WgI" frameborder="0" allow="accelerometer; autoplay; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe> The website <a href="https://99percentinvisible.org/episode/guerrilla-public-service/ "target="_blank">99% invisible</a> is host to various podcasts that are available on different topics. This one focused on something called a Norman Door, these are examples of COIK. For example, have you ever encountered a door where you were not sure if you should push or pull? You are not alone.

<center>[[Home|Home]]|[[Audio|Audio]]|[[Video|Video]]|[[Written|Written]]|[[Sources|Sources]]|[[DIY|Project]]|[[Reflection|Reflection]]</center> The Google development team created a wonderful video on how words can be utilized to make your content standout. One of the major focal points for this video was how being Clear, Concise, and Useful. By being clear the audience will not be caught up on jargon, by being concise they can find the key points easily and making the content useful your audience is more likely to retain it. <center><iframe width="560" height="315" src="https://www.youtube.com/embed/DIGfwUt53nI" frameborder="0" allow="accelerometer; autoplay; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe></center> In this video Kyle Rocky covers the basics on how micro-interactions or as he calls them Microcopy can influence the way that users interact with both the information as well as their reaction to it. He begins by stating that we should use simple language that anyone can understand, rather than jargon which can prevent people from participating in the discussion of learning and sharing. <center> <iframe width="560" height="315" src="https://www.youtube.com/embed/Yv8xhsQB8JQ" frameborder="0" allow="accelerometer; autoplay; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe></center>

<center>[[Home|Home]]|[[Audio|Audio]]|[[Video|Video]]|[[Written|Written]]|[[Sources|Sources]]|[[DIY|Project]]|[[Reflection|Reflection]]</center> Many of these sources focus on a term called Microcopy. This refers to the act of explaining or hinting at the functionality of a UX-UI component such as a button. Because many of these aspects seem obvious to the developers they are often COIK to first time users. One of the most common means of COIK is that of icons and logos. According to Aurora Harley, “Icons are, by definition, a visual representation of an object, action, or idea. If that object, action, or idea is not immediately clear to the users, the icon is reduced to mere eye candy” (Harley, Aurora) So, without context or some text to give users the meaning behind a logo they would just look good. To prevent this content creators should always test the usability of their product. To reduce ambiguity the content creator should offer insight or create a universally acceptable symbol. As Shane Williams notes, “A user’s understanding of an icon is based on previous experience. Due to the absence of a standard usage for most icons, text labels are necessary to communicate the meaning and reduce ambiguity.” (Williams, Shane) In order to properly communicate the meaning of icons a universal symbol like that of an envelope could be employed. But it seems more reliable to add a very brief amount of text to clarify what the object means. COIK can occur in any aspect of design including interfaces. Business.com wrote, “This issue is not only related to interface design. In everyday life, we are surrounded by icons: Traffic signs along the road, signs at the entrance to any shop, even on clothing labels.” (10 Mistakes) While traffic signs may seem simple to someone who is familiar with them, by imagining the confusion that the audience could experience if they are not, such as a tourist. Especially when compared to how simple it is to add some context or simplify the imagery. Another aspect of COIK is helping people without them having to ask. Fabricio Texeira states, “If they don’t understand what you are referring to, they will not always interrupt you to ask. Most people feel embarrassed to confess what they don’t know.” (Texeira, Fabricio) So, as professionals it is our obligation to extend the courtesy of being clear and concise in our work. Information overload is something everyone is becoming more familiar. Nick Babich wrote, “Unknown terms or phrases will increase cognitive load for the user. Do your best to avoid ‘geek speak’. A safe bet is to write for all levels of readers and pick common words that are clearly and easily understandable to beginning and advanced users.” (Babich, Nick) Without a simple knowledge then the audience can quickly become overwhelmed with processing what the meaning and text is trying to convey. Although many would not notice, work is another common place for COIK. According to Patrick Stafford, “Nothing is worse than thinking you have to speak at a particular language to take part in a conversation at work.” (Stafford, Patrick) By creating barriers like this people are preventing their coworkers, friends and even family from gaining this knowledge. Perhaps even worse than using jargon is when someone is misled or simply misuses it. In an article from Business.com they mention, “In certain cases, jargon provides a concise description of an activity to those who understand the terms. It causes a problem, however, when you are talking to someone who doesn’t understand the jargon, or worse, misuses it.” (Stop Talking) When used correctly jargon can help relay complex ideas or information in a simple format, but it can just as easily convolute this information. To prevent the misuse of jargon there must be a level of clarity. As Vicki Krueger mentions, “Clarity starts with a clear understanding of the topic you are writing about.” (Krueger, Vicki) Again by giving context to the idea or object the creator is giving the audience the means of clarity or understanding on the topic. Many prioritize strutting their knowledge over their peers. But as Rotem Binheim notes, “Be witty, but not at the expense of the plain message” (Binheim, Rotem) If your audience cannot understand what your message is then there is little reason to have created the message to begin with.

<center>[[Home|Home]]|[[Audio|Audio]]|[[Video|Video]]|[[Written|Written]]|[[Sources|Sources]]|[[DIY|Project]]|[[Reflection|Reflection]]</center> In order to showcase your new skills and knowledge of COIK we have prepared a three-step project. First, identify something visual that may not be clear to everyone. We have provided several examples of signs that without context or prior knowledge can easily be misconceived. Ex 1: This sign features two different signs. The first one indicates that drivers can only turn one way but highlights multiple turns available. While the second tells drivers that traffic will merge left in order to turn. <center><img src='https://upload.wikimedia.org/wikipedia/commons/0/0e/Confusing_street_signs.jpg' alt="" width="250" height="250"></center> Ex 2: Although not as confusing, this sign indicates no traffic can pass through. <center><img src='https://encrypted-tbn0.gstatic.com/images?q=tbn%3AANd9GcQNy7kA09rTjlOopUtdv8gj_zeVsYWsjgupovzdm5Qi4dbgMXbi&usqp=CAU' alt="" width="250" height="250"></center> Ex 3: Another double sign, this one has information which looks contradicting. It states drivers must stop herem but the smaller sign notes the exception for drivers turning right. <center><img src='https://live.staticflickr.com/7623/16825777238_a7733c088f_b.jpg' alt="" width="250" height="250"></center> Ex 4: This sign is in a different language which could pose a problem for those traveling, and it indicates two directions to the same location. <center><img src='https://upload.wikimedia.org/wikipedia/commons/0/05/Confusing_road_sign_at_Elan_Village_-_geograph.org.uk_-_265977.jpg' alt="" width="250" height="250"></center> Ex 5: With no context this sign could mean a lot of things but is indicating that traffic will be merging into the left lane. <center><img src='https://upload.wikimedia.org/wikipedia/commons/b/bd/SADC_road_sign_TW330.svg' alt="" width="250" height="250"></center> Second, think of and write a clear description that helps to eliminate the confusion. Again, several examples will be provided. Ex 1: This sign could read: Turn lanes MUST turn. Thru traffic MERGE left. With this change drivers would know they must turn if they are in a side lane but can also merge left to go thru. Ex 2: The wording could be more concise like: No Thru Access. Then users would know that this road does not exit or merge from any other point of entry. Ex 3: Although this sign is relatively efficient, it could read: Stop Except Right Lane. Then drivers in the right lane know they do not have to stop. Ex 4: A language barrier could be present in any place, but these signs should read the same or say: Llanwrthwl take a left or right. By providing that information drivers would know that regardless of which way they take they will arrive at their destination. Ex 5: Without any text this sign gives no indication what the driver should do. By adding something like: Traffic merging into LEFT lane. Then drivers know that traffic will be entering into the left lane. Finally, remember that COIK is only as unclear as the author makes it. And try to employ your new knowledge to improve your content usability.

<center>[[Home|Home]]|[[Audio|Audio]]|[[Video|Video]]|[[Written|Written]]|[[Sources|Sources]]|[[DIY|Project]]|[[Reflection|Reflection]]</center> <center>Works Cited</center> 10 Mistakes in Interface Icon Design That Confuse Users. IconDesignLab, 17 Aug. 2018, blog.icondesignlab.com/en/2018/10-mistakes-in-icon-design-that-confuse-users/. Babich, Nick. Effective Writing for Your UI: Things to Avoid. Medium, 8 July 2017, uxplanet.org/effective-writing-for-your-ui-things-to-avoid-f6084e94e009. Binheim, Rotem, and Kinneret Yifrah. 7 Guidelines for Writing Accessible Microcopy. Invision, www.invisionapp.com/inside-design/writing-accessible-microcopy/. Confusing Road Sign. Wikipedia, https://upload.wikimedia.org/wikipedia/commons/0/05/Confusing_road_sign_at_Elan_Village_-_geograph.org.uk_-_265977.jpg. Confusing Street Signs. Wikipedia, https://upload.wikimedia.org/wikipedia/commons/0/0e/Confusing_street_signs.jpg. Guerrilla Public Service Redux. 99% Invisible, 1 Jan. 1970, 99percentinvisible.org/episode/guerrilla-public-service/. Harley, Aurora. Icon Usability. Nielsen Norman Group, 27 July 2014, www.nngroup.com/articles/icon-usability/. “How to Write Better Microcopy to Improve Your UX - Proposify Biz Chat.” YouTube, 23 Jan. 2018, https://www.youtube.com/watch?time_continue=1&v=Yv8xhsQB8JQ&feature=emb_title. “How Words Can Make Your Product Stand Out (Google I/O '17).” YouTube, 19 May 2017, https://www.youtube.com/watch?time_continue=1&v=DIGfwUt53nI&feature=emb_title. “It's Not You. Bad Doors Are Everywhere.” Https://99percentinvisible.Org/Article/Norman-Doors-Dont-Know-Whether-Push-Pull-Blame-Design/, YouTube, https://www.youtube.com/watch?v=yY96hTb8WgI#action=share. Kreuger, Vicki. 7 Ways to Avoid Jargon in Your Writing. Poynter, 14 June 2017, www.poynter.org/educators-students/2017/7-ways-to-avoid-jargon-in-your-writing/. Road Sign. Wikipedia, https://upload.wikimedia.org/wikipedia/commons/b/bd/SADC_road_sign_TW330.svg. Stafford, Patrick. Cutting the Jargon out of Your Creative Work: Inside Design Blog. Invision, 2 Oct. 2018, www.invisionapp.com/inside-design/jargon-creative-work/. Stop Talking in Technical Jargon. Business.com, 18 Aug. 2015, www.business.com/articles/cut-the-code-why-speaking-in-technical-jargon-is-not-making-you-look-smarter/. Teixeira, Fabricio. UX Designers, Stop the Jargon and Keep It Simple. The Next Web, 21 June 2018, thenextweb.com/syndication/2018/06/24/the-user-experience-of-choosing-the-simplest-possible-words/. Untitled. Static Flickr, https://live.staticflickr.com/7623/16825777238_a7733c088f_b.jpg. Untitled. Tbn Gstatic, https://encrypted-tbn0.gstatic.com/images?q=tbn:ANd9GcQNy7kA09rTjlOopUtdv8gj_zeVsYWsjgupovzdm5Qi4dbgMXbi&usqp=CAU. Williams, Shane P. Can Icons Harm Usability and When Should You Use Them? Medium, 14 Apr. 2019, uxdesign.cc/when-should-i-be-using-icons-63e7448202c4.

<center>[[Home|Home]]|[[Audio|Audio]]|[[Video|Video]]|[[Written|Written]]|[[Sources|Sources]]|[[DIY|Project]]|[[Reflection|Reflection]]</center> <center>Looking Back</center> <center>Grace Roueleau</center> Grace was in charge of gathering the sources for our project. She started looking at things relating to COIK but realized there was not a lot of direct information about COIK in UX-UI media sources. She began looking for various forms of COIK in the world such as in writing via technical jargon or visual with things like poorly designed icons. She also tried to diversify the types of sources she gathered. These included two videos, two podcasts, and nine articles. <center>Dimitri Myers</center> Dimitri was in charge of creating the Twine document, and written content for the site as well as procuring images and designing the do it yourself project. By taking the sources Grace provided, Dimitri wrote various excerpts to communicate to our audience how to identify COIK, what it means, and eventually how to avoid it in creating your own content. This allows our audience to gain some insight that helped us during our time in DTC 478- Usability. Also a big thank you to Dr. Barber, without the introduction to COIK in this class we may never have known about things like Norman Doors or tried to provide higher quality content that is accessible to those who otherwise would not have access.