<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Erin Newby on Medium]]></title>
        <description><![CDATA[Stories by Erin Newby on Medium]]></description>
        <link>https://medium.com/@Erin_Newby?source=rss-596e6fc3f686------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*89-UoKQNXJBh00nfdFs87A.jpeg</url>
            <title>Stories by Erin Newby on Medium</title>
            <link>https://medium.com/@Erin_Newby?source=rss-596e6fc3f686------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 22:22:48 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@Erin_Newby/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Beyond accessibility basics: designing with choice]]></title>
            <link>https://medium.com/design-bootcamp/beyond-a11y-basics-designing-with-choice-2348819e6a4e?source=rss-596e6fc3f686------2</link>
            <guid isPermaLink="false">https://medium.com/p/2348819e6a4e</guid>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[accessibility]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[inclusive-design]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Erin Newby]]></dc:creator>
            <pubDate>Fri, 26 Jul 2024 13:02:24 GMT</pubDate>
            <atom:updated>2024-07-29T22:15:33.841Z</atom:updated>
            <content:encoded><![CDATA[<h4>Because users should have experiences that fit their needs</h4><figure><img alt="Blue watercolor painting of two hands" src="https://cdn-images-1.medium.com/max/1024/1*l_my513cX9SCylQQuqMN2A.png" /><figcaption>Artist: Miwon Yoon</figcaption></figure><p>I was once asked how to approach accessibility from a design perspective during the exploration/iteration phase of projects. Outside of blurting out conventional wisdom, I drew a blank. The common approach mentions color contrast ratios, tap target sizes, font sizes, etc., but most of that is <em>hopefully</em> covered by the design system if there’s one in place.</p><p>After a bit of reflection, I realized what I really wanted to communicate was the principle of “flexibility in use”. This principle is about creating design solutions that accommodate a wide range of individual preferences and abilities. It answers questions like: how would a blind person interact with this? Or, how would someone with limited dexterity complete this task? By considering how a solution solves problems for a variety of users, we are going a step further to ensure our designs are inclusive.</p><p>Voice search is an excellent example of this. It gives people the ability to search websites and apps using voice commands. While this feature wasn’t originally created with accessibility in mind, it was quickly adopted by a large range of users because of the choice it provides. This is especially helpful for people who have motor limitations, cognitive impairments, or those who simply find hands-free more convenient.</p><figure><img alt="Phone screen with search that has the option to voice search" src="https://cdn-images-1.medium.com/max/1024/1*ApsBIsRVB71Xh2HWGAlx7g.png" /></figure><p>Another great example is video captions. Captions provide a great alternative for people who are Deaf or hard of hearing, those who comprehend better through reading, or anyone who may be situationally impaired. For instance, someone could be in a library and want to watch a video, but doesn’t want to cause a stir or get evil looks from those nearby.</p><figure><img alt="Video still of Action Bronson talking about food" src="https://cdn-images-1.medium.com/max/1024/1*l7dTUd7NlYBZLprbGhMg8g.png" /></figure><p>Not only are video captions a great example of flexibility in use, but they also align seamlessly with the perceivable accessibility principle. This principle states that information and UI components must be presented to people in ways they can best perceive it. For instance, if a person can’t hear content, they should be able to read it, and vice versa.</p><p>Ultimately, it’s about creating solutions that offer people choice. By considering flexibility in use while exploring design solutions, we can create inclusive designs that cater to a wide range of preferences and abilities. So, to the person who asked me how to approach accessibility from a design perspective during the exploration/iteration phase of projects, know that this is the information I wish I’d shared.</p><p><em>Originally published at </em><a href="https://erinnewby.substack.com/p/beyond-a11y-basics-designing-with"><em>https://erinnewby.substack.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2348819e6a4e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/beyond-a11y-basics-designing-with-choice-2348819e6a4e">Beyond accessibility basics: designing with choice</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A few more things to consider about digital accessibility]]></title>
            <link>https://uxdesign.cc/a-few-more-things-to-consider-about-digital-accessibility-d001fbc7eae3?source=rss-596e6fc3f686------2</link>
            <guid isPermaLink="false">https://medium.com/p/d001fbc7eae3</guid>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[accessibility]]></category>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Erin Newby]]></dc:creator>
            <pubDate>Fri, 21 Jun 2019 21:23:09 GMT</pubDate>
            <atom:updated>2019-06-26T17:21:29.291Z</atom:updated>
            <content:encoded><![CDATA[<h4>And a closer look at what it means to be disabled</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XvDiq_SAF6pOeqCV66Ojew.jpeg" /><figcaption>Artist: Dadu Shin. 2016</figcaption></figure><p>Last year a lady in Arkansas walked to her car to find a “faker” note left on her windshield. She was parked in a handicapped parking spot and was being called out for using a handicapped sign while appearing to be just fine. What the rascal didn’t know was that she had a rare disease which symptoms were invisible. This example represents one of the many misconceptions we have about people with disabilities — let alone those that have disabilities that are invisible. These misconceptions not only affect how we view certain disabilities in our day to day life, but they can also trickle down and affect how we approach and view accessibility on all levels of product design.</p><p>It’s reported that roughly 1 in 5 Americans have a disability, but it’s unlikely that this number includes those living with disabilities that are temporary or invisible. By definition, temporary disabilities are physical or mental conditions that limit a person’s abilities for a short period of time. Examples include pregnancy, injured limbs, and anxiety — which many of us, if not all, are going to experience.</p><p>An invisible disability is a little trickier to identify — let alone relate to. As mentioned earlier, with the parking lot example, most people don’t recognize these types of disabilities because you simply can’t see them. Invisible disabilities are physical, mental or neurological conditions that limit a person’s movements, senses, or activities that are unseen to the onlooker. A few examples include dyslexia, color blindness, and multiple sclerosis.</p><p>By incorporating this broader definition of disability, we’re starting to close the gap between ourselves and the separate “user group” we put people with disabilities in while designing. Since it’s estimated that we’re all going to experience some form of disability within our lifetimes — whether physical, temporary, or invisible — designing for accessibility means designing for everyone.</p><p>With this broader scope of disability, it’s not only valuable — but very important to create accessible experiences. That being said, how do we get everyone on board — both stakeholders and designers — to create a landscape that allows everyone to interact with the digital world around us.</p><p>From a stakeholder perspective, it could potentially prevent unnecessary legal expenses and help to foster innovation.</p><p>Target, for example, in 2006, was sued by the national federation of the blind for not making their website accessible. Prior to getting sued they received many complaints from this community but made no effort to fix the issues. And, if you can believe this, they fought against the case — although they ended up losing.</p><p>In the first half of 2018 alone, over a thousand plaintiffs filled suites against companies for inaccessible digital products and services. Companies are — at an increasing rate — finding out the hard way that inaccessibility is a federal offense that comes with a huge price tag. Despite this, once companies start looking further into accessibility, they may be surprised with what they find.</p><p>Accessibility also has a strong link to innovation. Did you know that the typewriter was invented as a writing aid for a blind woman? The story goes she was dating the inventor and wanted to send him letters but couldn’t operate a pen and ink. He created the typewriter as a way for them to communicate <em>(A modern day love story!)</em>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/303/1*T4j6v6OlvfeRq-NuZpmPfQ.png" /></figure><p>The typewriter was originally an assistive technology that went on to become adopted as a mainstream commercial product that went on to inspire word processors and the very keyboards we use today. There are countless examples of similar stories.</p><p>By considering stakeholders goals and objectives, we can then begin to build a case for accessibility that not only adds to companies innovation efforts but also creates preventative measures for unnecessary expenses.</p><p>Now, how do we make sure that we, as designers, are doing our part? Counterintuitive to what some of us might think — design patterns and the basic building blocks of good design already cover a lot of ground in ensuring that we’re incorporating accessibility into our products and services.</p><p>The basic elements of good UI design — which, to name a few include: plain language, clearly defined hierarchy, minimizing clutter, the use of whitespace, and good color contrast — are keys to making interfaces usable and effective. They’re also keys to making interfaces accessible.</p><p>For instance, clearly written content with a defined hierarchy and logical structure makes your content easier to understand and aids in scannability. This allows the user to scan and find sections they’re interested in. This specifically helps those with low vision or that have cognitive or learning disabilities because it allows for clarity, consistency, and ensures that different parts of a product or site are easy to locate and identify.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9aa3Y4-i_bdBtiAsF1Y4nw.png" /></figure><p>To take it a step further, the use of established design patterns also aids in ensuring that were designed for accessibility. A large part of what makes successful interaction design successful is the use of these patterns. All humans — regardless of having a disability or not — are hardwired to recognize patterns. By using these we’re playing into this natural human tendency by reinforcing what the users have learned to expect — when interacting with technology.</p><p>These established patterns not only communicate function but also intent. From an accessibility standpoint, the use of these patterns helps the cognitively impaired by reducing their cognitive load as they would expect a search to behave like search and buttons to look and act like buttons.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-1G2R40Uc6u31DmQzDd3Bg.png" /></figure><p>We can also build a basic level of accessibility into our reusable component libraries. By doing this, we’re not only taking advantage of the benefits of design patterns but also — from a development standpoint — we’re ensuring that basic accessibility is baked our process. This approach may require more effort upfront, but in the long run, as development scales, we no longer have to fret over if we have basic level accessibility within our products.</p><p>Facebook does a good job of this. They’ve created a component library whose primary goal is providing their developers, across all product teams, components with basic accessibility support. Some of this basic level accessibility includes:</p><ul><li>Keyboard focus (this allows users to navigate the pages using the keyboard alone)</li><li>Alt text (this provides a text alternative to non-visual content)</li><li>Aria roles (aids screen readers when distinguishing between different types of content)</li></ul><p>By recognizing the benefits of incorporating accessibility into our design and development approaches, we’re ensuring that we’re designing for inclusivity.</p><p>Whether we’re Incorporating accessibility as a preventative measure to a lawsuit, fostering innovation, or rounding out our design and development toolkits, we’re helping people participate more fully in the digital landscape.</p><p>So, the next time you find yourself in a parking lot, or on a bus, and you see someone occupying a handicap space where it may not seem justifiable, stop and think because there could be more than meets the eye. Or, it could just be some lazy bastard.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d001fbc7eae3" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/a-few-more-things-to-consider-about-digital-accessibility-d001fbc7eae3">A few more things to consider about digital accessibility</a> was originally published in <a href="https://uxdesign.cc/">UX Collective</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Cultural Blind Spots in UX]]></title>
            <link>https://medium.com/nasdaq-design/cultural-blind-spots-in-ux-840353aa3cdd?source=rss-596e6fc3f686------2</link>
            <guid isPermaLink="false">https://medium.com/p/840353aa3cdd</guid>
            <category><![CDATA[language]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[culture]]></category>
            <dc:creator><![CDATA[Erin Newby]]></dc:creator>
            <pubDate>Fri, 09 Jun 2017 15:15:30 GMT</pubDate>
            <atom:updated>2017-06-15T01:48:03.543Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vhP2Ji-Vna2h5Q6QPYx9zQ.png" /></figure><h4>Designing for international markets requires more than translating words.</h4><p>Although Nicolas Cage won best global actor in China a few years ago, and almost every country in the world (except North Korea and Cuba) sells Coca Cola, it doesn’t mean all of western culture is the standard worldwide — specifically western design practices and digital experiences. Since more and more of our products and services are being used in global markets we need to think about how our designs are interpreted in these different countries beyond a one to one language translation. Designing for international markets means designing for cultural nuances.</p><p>Imagine you got an offer from your dream design job — it has an amazing salary and you’d be working alongside an award winning team. But, there’s one caveat. The office you’d be working in is located in China. And, upon receiving the offer, you get informed that you’d be designing for an Asian market. This excites you so you start digging around into market research and you stumble upon exhibit A:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/705/1*2P23DTsBJl5M2-krQWvTMw.png" /><figcaption>Example of data density for an Asian market</figcaption></figure><p>It has extremely high information density. You think to yourself, “Where is the white space?!” But upon digging deeper and talking to a few of your design colleagues, you discover that most Asian cultures emphasize communicating large amounts of content at a single instance with multiple areas of focus.</p><p>With the example above we can start to see how we are naïve in our design decisions when when it comes to our own cultural biases. Our own biases not only influence our visual design preferences, but all aspects of our design. For example, as it applies to information architecture, <a href="https://obaninternational.com/guides/download-scaling-for-international-digital-success/">Oban international partnered with Dell</a> to test IA via eye tracking to see how different cultures navigate webpages. And the results were surprising.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/766/1*igaG2EH9YlkCFYXPvcNu_g.png" /><figcaption>Eye scan habits of different cultures</figcaption></figure><p><strong>First:</strong> Japanese users start reading the whole page from right-to-left; they also scan the content a few times (that’s why you see the swirl on the image).</p><p><strong>Middle:</strong> UK users scan the content from left to right.</p><p><strong>Last:</strong> Users in Canada pay more attention to the text in the hero banner.</p><p>These results give us further insight about how different cultures vastly differ in how they consume information. Knowing this, if we’re working on products and designs that serve a broader international market, we need to be aware that our cultural biases stand in the way of creating products that effectively serve this larger market.</p><h4>With that in mind, there’s a few things we can do to better handle our cultural biases and design for cultural nuances:</h4><ol><li>Awareness — realizing that this problem does, in fact, exist</li><li>If possible, test with an international market. Conducting usability tests will catch pain points in different demographics and cultural contexts. I know, this is a lot to ask if there aren’t resources allocated in the budget for this, but this is truly invaluable. And, you could provide a very strong business case as to why this matters.</li><li>Localize copy and content beyond a 1–1 literal translation. Lots and lots of things get lost in 1–1 translations. Have you ever been in a foreign country and solely relied on google translate? Yeah, didn’t quite work out too well, did it? Localization captures cultural references, idioms, grammar, as well as words that don’t exist in other languages. For example, there’s no ‘yes’ or ‘no’ equivalent in Chinese languages</li><li>Flexible layout: Some languages, once translated, have longer words than the language it was being translated from. Flexible layouts take into account word length and makes sure the layout doesn’t break. For example, the five letter word sorry translates to a 17 letter Utoqqatsissutigaa in Greenlandic — the local language spoken in Greenland and Denmark.</li></ol><p>McDonald’s, the world&#39;s largest restaurant chain, understands the importance of designing for cultural nuances and adjusting to its international markets. Not only do they adjust their menu to the preferred local foods, they also make sure their digital presence is also in line with local cultural standards and expectations. For example, McDonald’s online presence in China is different than that of Arabia.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LGoDr6tPLzs_reTYVYbNtw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XcS1gI6LSf04LZ0sM7ajgA.png" /><figcaption>McDonald’s China vs. McDonald’s Saudi Arabia</figcaption></figure><p>One distinct difference between the two is the flipped layout. The language spoken in Saudi Arabia is read from right to left where in china non traditional Chinese is written and read from left to right. This layout change reflects an understanding of the local culture.</p><p>Designing for international markets can be tough — especially when you’re a foreigner with no familiarity of the cultural background. But, with research and usability testing, we can design better experiences, and bypass our cultural nuances. With that in mind, we can go back to wondering why, in fact, do Asian cultures love Nicholas Cage.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=840353aa3cdd" width="1" height="1" alt=""><hr><p><a href="https://medium.com/nasdaq-design/cultural-blind-spots-in-ux-840353aa3cdd">Cultural Blind Spots in UX</a> was originally published in <a href="https://medium.com/nasdaq-design">Nasdaq Design</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Tough Crowd: Designing for designers]]></title>
            <link>https://medium.com/@Erin_Newby/tough-crowd-designing-for-designers-9a219bb27dde?source=rss-596e6fc3f686------2</link>
            <guid isPermaLink="false">https://medium.com/p/9a219bb27dde</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[thoughts]]></category>
            <dc:creator><![CDATA[Erin Newby]]></dc:creator>
            <pubDate>Tue, 03 May 2016 01:17:51 GMT</pubDate>
            <atom:updated>2016-05-03T01:29:28.954Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*8pjGizOjEVPG84z3m3ZadA.jpeg" /></figure><p>So your presented with a problem, how do you design a landing page to get the attention of other designers? Do you pull out all the tricks in the bag, use all the trends? Suddenly you feel the pressure building, <em>oh the scrutiny.</em></p><p><strong>Hmmm….</strong></p><p>So I got to thinking, designers are simply normal people that need their lives easier like everyone else. Solve an everyday problem and were sold, right?</p><p>It couldn’t be that simple. <em>Or could it?</em> Yes. If the product your designing for actually, like actually, solves a problem then whats the fuss. Although, it wouldn’t hurt to pull out the bells and whistles! One of the great things about designing for designers is that it gives you room to flex. After all why not, you finally have a crowd that truly appreciates great design.</p><p>Design on my friends :)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9a219bb27dde" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>