<?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 Bingying Xia on Medium]]></title>
        <description><![CDATA[Stories by Bingying Xia on Medium]]></description>
        <link>https://medium.com/@bingying?source=rss-f73e9eae8214------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*yYUtq-_y18Rk9-3Uk_EJJg.jpeg</url>
            <title>Stories by Bingying Xia on Medium</title>
            <link>https://medium.com/@bingying?source=rss-f73e9eae8214------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 04:47:20 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@bingying/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[5 lessons I learned by designing for accessibility]]></title>
            <link>https://uxdesign.cc/5-lessons-i-learned-by-designing-for-accessibility-65842a74f849?source=rss-f73e9eae8214------2</link>
            <guid isPermaLink="false">https://medium.com/p/65842a74f849</guid>
            <category><![CDATA[inclusive-design]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[accessibility]]></category>
            <dc:creator><![CDATA[Bingying Xia]]></dc:creator>
            <pubDate>Sun, 29 Mar 2020 05:47:53 GMT</pubDate>
            <atom:updated>2020-04-05T07:05:28.178Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="Illustration of woman in wheelchair and man holding white cane" src="https://cdn-images-1.medium.com/max/1024/1*YVVjb1UMmP6sflNlezZNSw.png" /><figcaption>Illustration based on Pablo Stanley’s <a href="https://www.humaaans.com/">Humaaans library</a></figcaption></figure><p>18 months ago, I joined the Android team at Google as its first <strong>Android Accessibility Design Lead</strong>.</p><p>Now, you might think I must have some ironclad qualifications in accessibility in order to be handed the responsibility of designing accessible experiences for the nearly 3 billion Android devices out there.</p><p>The honest truth was, <strong>I barely had any knowledge of accessibility</strong> beyond color contrast ratios and tap target sizes. I had a drive for designing for social good (something I’ve been passionate about throughout my career), and sadly, the team simply was not able to find anyone more qualified than that — an empty enthusiasm. That speaks to how scarce accessibility resources are, even at one of the largest tech companies in the world.</p><p>Ask anyone in tech, and they’ll say “<strong>oh yeah, of course accessibility is important; it’s the right thing to do.</strong>” Come deadline time, the same people will be pulling their hair out saying “look, I’d love to make it work, but given the constraints, we simply can’t accommodate <strong><em>edge cases</em></strong> like accessibility.”</p><p>Before I became an accessibility designer, I was OK letting go of this type of mentality. Not anymore.</p><p>Here’s what I learned after 18 months on this job.</p><h3>1. Everyone is disabled in one way or another, at one point or another</h3><figure><img alt="Decorative illustration" src="https://cdn-images-1.medium.com/max/1024/1*L0TYEZSePyDQt00b09vFJg.png" /></figure><p>When I say “disability”, what’s the first thing that comes to your mind? For most people, it’s probably a <strong><em>permanent disability</em></strong> — blindness (visual impairment), deafness (hearing impairment), person in a wheelchair (motor impairment), or cognitive impairments such as Alzheimer’s or Down syndrome.</p><p>Even when you limit your definitions of disability to permanent disabilities only, 1 out of 7 people are disabled, according to the <a href="https://www.who.int/disabilities/world_report/2011/report/en/">WHO</a>. That is <strong><em>more than one billion people</em></strong> in the world.</p><p>However, disability is much wider than that. Have you ever been in a loud restaurant trying to have a conversation with someone, and simply can’t hear them above the background noise? That is <strong>situational deafness</strong>. Have you had a paper cut in your finger and avoided using that finger for a few days? That is a <strong>temporary motor impairment</strong>.</p><p><strong>Everyone experiences situational and temporary disabilities on a daily basis.</strong></p><figure><img alt="Illustration of situational impairments: driving, bumpy bus, loud restaurant, screen glare, foreign travel, shopping" src="https://cdn-images-1.medium.com/max/1024/1*hc8JHJyjPm3urq5ogtVYLg.png" /></figure><p>A few more examples:</p><ul><li><strong>Driving</strong>: situationally impaired vision, mobility, and attention</li><li><strong>Riding on a bumpy bus / train</strong>: situationally impaired dexterity</li><li><strong>Traveling and doesn’t speak the local language</strong>: situationally impaired verbal communication</li><li><strong>Carrying bags while shopping</strong>: situationally impaired mobility</li><li><strong>Pupils dilated after eye exam</strong>: temporarily impaired vision</li><li><strong>Wearing a cast due to bone injury</strong>: temporarily impaired mobility</li><li><strong>Not enough coffee in the morning</strong>: temporarily impaired cognition</li></ul><p>In these situations, a normally able-bodied person experiences the same limitations as someone with a permanent disability when using your product (physical or digital).</p><p>In addition, <strong>everyone is steadily growing older</strong> with each passing day. With old age comes natural deterioration in physical and cognitive capabilities. About 65% of people with vision impairments are aged 65 or older (<a href="https://www.who.int/en/news-room/fact-sheets/detail/blindness-and-visual-impairment">WHO</a>, 2012). Just because you have perfect 20/20 vision today, doesn’t mean it’ll stay that way forever.</p><p>Tech products tend to focus heavily on the young, tech-savvy population. However, if we as user-centric product designers don’t consider older adults in our design, who will care for us when we inevitably grow old?</p><h3>2. Accessible products = better products for every single user</h3><figure><img alt="Decorative illustration" src="https://cdn-images-1.medium.com/max/1024/1*cU9GTtfDLw8wtQVBARu4yg.png" /></figure><p>Designing with accessibility in mind means being inclusive of everyone, whether they have a permanent disability, or experience situational and temporary disabilities from time to time. Accessibility is in no way, shape, or form an <strong><em>edge case</em></strong> — it impacts 100% of your users.</p><p>A classic phenomenon is the <strong>curb cut effect </strong>— it refers to the fact that stuff designed for people with disabilities often end up helping everyone.</p><p>Curb cuts are ramps cut into sidewalks where they meet the street. You’ve probably seen these before without really noticing them. These are mandated by law so that people on wheelchairs can get around easily. However, they’re also useful to people carrying luggages, pushing a stroller or bicycle, riding a skateboard, etc.</p><figure><img alt="Photo of a curb cut on an urban sidewalk" src="https://cdn-images-1.medium.com/max/1024/1*3crbXAkyv6oXnqrm8QgB3g.jpeg" /><figcaption>A curb cut, by <a href="http://commons.wikimedia.org/wiki/User:Nick-philly">Nick-philly</a> — Own work, <a href="https://creativecommons.org/licenses/by-sa/4.0">CC BY-SA 4.0</a></figcaption></figure><p>Other examples of curb cut effect include:</p><ul><li><strong>Typewriter</strong>: originally designed by Italian inventor Pellegrino Turri to help his blind girlfriend write more legible love letters (Bodine, Cathy. <em>Assistive Technology and Science</em>. 2013.)</li><li><strong>Captions</strong>: originally designed to help people who are deaf or hard of hearing watch TV</li><li><strong>Email</strong>: invented by Vint Cerf when architecting the internet, largely influenced by his own hearing impairment and reliance on written communication (<a href="https://www.cnet.com/news/internet-inventor-vint-cerf-accessibility-disability-deaf-hearing/">CNET</a>)</li></ul><p>In addition, accessibility is a <strong>magnifying lens that amplifies underlying problems</strong> for you to see. If someone with hand tremor has trouble tapping a particular button in your UI, more likely than not, non-disabled users will often mis-tap when trying to use that button as well. If someone with a learning disability has trouble understanding the language or layout in your product, more likely than not, non-disabled users will also find it complex and hard to understand.</p><p>When you dedicate time and resources toward solving issues for people with disabilities, everyone ends up benefiting from it, because honestly, <strong>we could all use a little bit of help sometimes</strong>.</p><h3>3. Accessibility drives innovation</h3><figure><img alt="Decorative illustration" src="https://cdn-images-1.medium.com/max/1024/1*ui2pzYMcVtlOcW9FkTMUuw.png" /></figure><p>When we face situational or temporary disabilities, minor annoyances may not be annoying enough for us to design solutions for. However, for people with permanent disabilities such as blindness or deafness, their difficulties won’t simply go away if you ignore them long enough.</p><p>Designing with an <strong>accessibility-first mindset</strong> means treating problems faced by people with disabilities as top-priority problems. When we design accessibility-first, we can <strong>identify unsolved problems</strong> faced by everyone, <strong>unlock new use-cases and potentials</strong> that people haven’t explored before, and push technology forward for everyone. That is the beauty of the curb cut effect.</p><p>Designers are often daunted by the extreme constraints that accessibility puts on design — how does someone use my product if they can’t see it? However, when you solve for the hardest problems, the solution naturally extends to solving a strings of related and easier problems.</p><p><strong>If a blind user can use your product with ease, think of just how effortless it will be for people who <em>aren’t</em> blind.</strong></p><p>A reverse phenomenon to the curb cut effect is true as well — stuff that were intended to offer a bit of convenience to able-bodied people often end up becoming <strong>life-changers for people with disabilities</strong>.</p><ul><li><strong>Phone camera</strong> is frequently used by people with low vision as a magnifier to better read product packaging or see things further away. This is much cheaper than having to buy a separate magnifying device, and it doesn’t call attention to their disability when they use it in public.</li><li><strong>Voice assistants or smart speakers</strong> are a nice-to-have for most people. I use my Google Home when I’m cooking and can’t use my phone normally. However, blind users really adore them, because they can get stuff done much faster without having to fumble around on a touchscreen — something that inherently isn’t designed for blind usage.</li><li><strong>Ride sharing apps</strong> like Lyft or Uber are a convenience for most people. However, it’s led to a lot more freedom for people who are deaf or hard of hearing, so that they can get a taxi without having to rely on verbal communication. I’ve also met a deaf Lyft driver. Ride sharing allowed him to work as a taxi driver despite his disability, something that would’ve been impossible before.</li><li><strong>Self-driving cars</strong> are exciting for most people because we look forward to playing Candy Crush while driving to work one day. However, it will open up a whole world of possibilities for people with vision or motor impairments who can’t drive today. One of the first <a href="https://www.youtube.com/watch?v=cdgQpa1pUUE">Google self-driving cars (now Waymo) demos</a> were done with a blind person.</li></ul><p>Whenever I talk to people with disabilities about technology, the feedback is overwhelmingly positive. <strong>Technology empowers them</strong> to do things they can’t do otherwise, to accomplish everyday tasks quickly and easily, to narrow the ability gap between them and people without disabilities, and to help them be more employable so they can lead meaningful and fulfilling lives.</p><p>I believe <strong>we’re at a critical time in history</strong> where the rise of cutting-edge technology like AI, image recognition, and natural language processing can drastically improve the lives of people with disabilities. Technology can become the eyes for a blind person, the ears for a deaf person, and the voice for someone who cannot otherwise speak.</p><p>Does the technology you’re working on today have the potential to change someone’s life?</p><h3>4. You assumptions about people with disabilities are probably wrong</h3><figure><img alt="Decorative illustration" src="https://cdn-images-1.medium.com/max/1024/1*Zn0xVyRFyiVjTrlqRA3OBw.png" /></figure><p>A question I often get asked is — I don’t know anything about people with disabilities. How am I supposed to design for them?</p><p>For starters, <strong>they are not that different</strong>. When I first started in accessibility, I asked the closest blind engineer, “So what apps do blind people use?” That question was met with an apathetic not-this-again eye-roll: “We use the same apps that you do — Facebook, YouTube, Twitter, whatever.”</p><p>People tend to face this understanding gap because they <strong>assume people with disabilities are some distant <em>other</em></strong>, not living, breathing human beings like the rest of us.</p><p><strong>People with disabilities are normal, regular human beings too</strong>, just with a few constraints peppered in.</p><figure><img alt="Photo of people playing wheelchair basketball in a stadium" src="https://cdn-images-1.medium.com/max/1024/1*-HFzMecJ_d1ceWgtcTfE6g.jpeg" /><figcaption>Image by <a href="https://pixabay.com/users/tpsdave-12019/?utm_source=link-attribution&amp;amp;utm_medium=referral&amp;amp;utm_campaign=image&amp;amp;utm_content=79604">David Mark</a> from <a href="https://pixabay.com/?utm_source=link-attribution&amp;amp;utm_medium=referral&amp;amp;utm_campaign=image&amp;amp;utm_content=79604">Pixabay</a></figcaption></figure><p>It may be easy to <strong><em>assume</em></strong> that blind users don’t take photos, or that deaf users don’t listen to music, so these products don’t need to be as accessible, but <strong>that cannot be further from the truth</strong>.</p><p>Excluding users based on unvalidated assumptions is just plain rude. <strong>Don’t be rude</strong>.</p><p>Here’s <strong>what I learned from research</strong>: many blind users enjoy capturing and sharing life moments with their camera just as much as sighted users, and many deaf users enjoy feeling the beat and rhythm of music with their body, just like hearing users.</p><p>When in doubt, don’t assume, ask!</p><p>As you probably know from being a designer, the best way to learn about users is to talk to them directly. Your local community might have non-profit organizations for people with disabilities, and they may be happy to answer your questions.</p><p>Failing in-person contact, YouTube also has a vast pool of videos if you just search for “How do people with [insert disability here] do [insert task here]?”, and folks may be able to answer your questions online as well. Some of my favorite channels include <a href="https://www.youtube.com/user/TommyEdisonXP">the Tommy Edison Experience</a>, <a href="https://www.youtube.com/channel/UCfEalJW91FE9BDH9xUVDvvg">The Essential Sign</a>, and <a href="https://www.youtube.com/channel/UCRIiUxBTaeMCU_K0sWtl5sw">Whhels2Walking</a>.</p><p>The only difference between able-bodied people and those with disabilities, is that <strong>we perceive or interact with the world slightly differently</strong>.</p><p>You and I can’t fly, but you wouldn’t say we’re “aerially-disabled”, because no other human can fly. But birds can fly, dogs can smell something a mile away, and bees can see ultraviolet colors. Does that make all humans <em>disabled</em> compared to animals? No, we just perceive the world differently.</p><p>This is true for people with differing abilities, and it’s true for people from different cultural backgrounds, income levels, age, gender, belief, etc.</p><p>We only consider blindness a disability because most people are not blind. Let’s pretend that instead of 4%, 94% of people have a vision impairment. Imagine how different our physical world and our digital products would be.</p><h3>5. Considering inclusion early saves you a ton of trouble down the road</h3><figure><img alt="Decorative illustration" src="https://cdn-images-1.medium.com/max/1024/1*-h0E1dY8am1JQs7aMvufFA.png" /></figure><p>At many organizations, the model for accessibility I’ve observed is <strong><em>compliance-centric accessibility</em></strong>. That means accessibility is one of the last things on a checklist that the team has to tick off in order to meet compliance standards and launch a product.</p><p>The problem with compliance-centric accessibility is that, <strong>accessibility issues are often found at the last stage of product development</strong>, when people are running up against deadlines, and heavy amounts of design and engineering work has already been poured into the product.</p><figure><img alt="Graph showing the cost to fix a big grows bigger when bug is found later in the software development process" src="https://cdn-images-1.medium.com/max/576/1*PwOncGhZNlQKJ_3jwSJ1uw.png" /><figcaption>Diagram extracted from the book <em>Software Testing by Ron Patton</em></figcaption></figure><p>When accessibility issues arise at the very end, what ends up happening is that instead of going back to the drawing board and redesigning everything from scratch (which teams definitely don’t have time for), they slap together a <strong>last-minute band-aid quick fix</strong> in order to meet compliance, often still resulting in unanticipated stress and extra work for the whole team.</p><p>This is not healthy for the team, nor is it good for end users.</p><p>On my team, I’m advocating to adopt what I call <strong><em>accessibility-first design</em></strong>. Even in the earliest stages of brainstorming and visioning exercises, make sure to <strong>consider inclusive use-cases</strong> <strong>and inclusive personas</strong> so that your final product is inclusive of everyone.</p><p>An easy way to do it is to include common situational impairments, such as driving or holding groceries with one hand, as your primary user journeys.</p><p>When you consider accessibility from the get-go, you avoid unanticipated compliance issues down the road, your designers and engineers don’t have to scramble to put together last minute fixes, your QA team doesn’t have to worry about filing hundreds of accessibility bugs, and your users will enjoy a much more effortless and helpful product experience. <strong>It’s a win-win-win-win situation.</strong></p><p>How might you help bring inclusive design to your organization?</p><p>In the past 18 months, I’ve also gained many surprising <strong>personal benefits</strong> from working on accessibility.</p><h3><strong>1. I can consume knowledge 3 times faster</strong></h3><p>One of the products I’m responsible for is TalkBack, which is <strong>Android’s screen reader for blind users</strong>. Screen readers are software that read the content of the screen out loud, so a blind person can know what’s on-screen without looking at it. This is how blind users interact with their phones and computers.</p><p>Listening to audio is a one-dimensional, linear way of consuming information, so it’s often much slower than visual reading in a two-dimensional space. To make up for this inefficiency, blind users generally set their screen readers at a very fast speech rate — probably 3–5 times faster than normal human conversation.</p><p>In the process of designing for TalkBack, I’ve also developed a habit of <strong>listening to audio at ~3x speed</strong> in order to make my workflow efficient. Mind you, I’m not even a native English speaker.</p><p>Now, even when I listen to the most information-dense content, be it an instructional YouTube video, a presentation, or an online course, I always listen to it at the fastest speed available — generally 2x (I wish they offered 3x though). This means it only takes me 30 minutes to finish an hour-long talk, and <strong>it’s been a huge time saver</strong>.</p><p>Relevant: <a href="https://www.youtube.com/watch?v=c0nvdiRdehw">How Blind People Use YouTube &amp; Twitter on the iPhone</a>, by The Tommy Edison Experience</p><h3><strong>2. I discovered useful tools that help myself as well as family and friends</strong></h3><figure><img alt="Illustration of a meeting, where someone holds a phone that reads “Is it all updated? Yep.”" src="https://cdn-images-1.medium.com/max/1024/1*UTGaSNrYxefr1k1fHOZygA.png" /></figure><p>As stated earlier, everyone is disabled in one way or another, and by working on accessibility, I got to know a ton of accessibility tools that are helpful for everyone.</p><p>Examples include:</p><ul><li>I use <a href="https://www.android.com/accessibility/live-transcribe/">Live Transcribe</a> (shameless plug for my own product) to help me record meeting notes and communicate better with people who are less fluent in English.</li><li>I use <a href="https://blog.google/products/android/sound-amplifier-more-people-can-hear-clearly/">Sound Amplifier</a> (another shameless plug) paired with bluetooth headphones to hear what’s on TV from another room.</li><li>I’ve helped people with deteriorating eyesight (e.g. my parents) to find helpful settings like large font size, large display size, and magnifying tools.</li><li>I’ve helped people who love dark theme but wish more apps supported it to find advanced accessibility settings for <a href="https://android.gadgethacks.com/how-to/force-enable-dark-mode-for-all-apps-android-10-0214254/">forcing dark theme on all apps</a>.</li></ul><h3><strong>3. I’m no longer afraid of growing old or becoming disabled</strong></h3><p>As a designer, one of my hidden fears has been: “What if one day I lose my eyesight or lose dexterity of my hands? How will I live and work?” Maybe we all have this intrinsic fear.</p><p>I’m happy to report that <strong>I no longer have these stupid fears</strong>. Through the process of understanding accessibility users and how they cope with their disabilities, I now know every type of assistive technology and coping mechanism like the back of my hand.</p><p>If I get into an accident and become blind tomorrow — no problem, I know how to <strong>stay productive and positive</strong> as a blind person. Well, <em>maybe</em> I won’t be a designer any more, but I know I’ll still have a happy and fulfilling life. If I gradually lose the ability to use my eyes, ears, hands and feet over time with old age, I know exactly how to not let that bother me as well. This <strong>feeling of security and freedom</strong> is really reassuring.</p><p>I won’t say that I <em>understand</em> everything that people with disabilities have to deal with, because I can’t possibly be that arrogant, but after talking to people with disabilities and learning about them on a daily basis for the past 18 months, I’ve developed a much healthier understanding of disabilities.</p><p>It’s just a different way of life, that’s all. There’s nothing to fear and nothing to feel sorry for.</p><h3><strong>4. I became a much better public speaker and knowledge sharer</strong></h3><figure><img alt="Me teaching a design workshop at a conference" src="https://cdn-images-1.medium.com/max/1024/1*7tbU5Bre7lQDymfaHW7uSA.jpeg" /><figcaption>Me teaching a workshop at User Friendly conference, photo courtesy of <a href="http://www.upachina.org/">UXPA</a></figcaption></figure><p>A large part of my job is to convince other designers and people in tech to consider accessibility, so I often find myself being <strong>thrown into an activist and evangelist role</strong> — a situation I’m positively surprised by.</p><p>This was a forcing function for me to develop stronger skills in <strong>storytelling, negotiation, and public speaking</strong>. In turn, it’s helped me become a better designer and generally a better communicator.</p><p>I’ve also taken a much more <strong>proactive stance in knowledge sharing </strong>in order to advocate for accessibility, doing talks and running workshops both within Google and at external conferences, appearing on a <a href="https://www.uxcoffee.com/episode/72">design podcast</a>, and writing articles such as this one.</p><p><strong>It’s helped grow my career as well as my personal impact</strong>. I can only do so much as a single person with accessibility knowledge, but if I help others to start caring and taking action, my impact grows exponentially.</p><p>I hope that one day, I can look back and see I’ve made a small footprint in <strong>helping build a better, more inclusive world</strong>.</p><p>Interested in learning more about designing for accessibility?</p><p>Here are some further reading:</p><ul><li><a href="https://uxdesign.cc/designing-for-accessibility-is-not-that-hard-c04cc4779d94">Designing for accessibility is not that hard</a>, by Pablo Stanley</li><li><a href="https://99percentinvisible.org/episode/curb-cuts/">Curb Cuts</a>, a 99% Invisible podcast episode</li><li><a href="https://material.io/design/usability/accessibility.html#">Accessibility design guidelines</a> from Google Material Design</li><li><a href="https://www.microsoft.com/design/inclusive/">Inclusive design toolkit</a> from Microsoft</li><li><a href="https://developer.apple.com/design/human-interface-guidelines/accessibility/overview/introduction/">Accessibility design</a> from Apple Human Interface Guidelines</li></ul><p>This was an Inclusive Design 101 level introduction to designing for accessibility. I hope to continue this series and delve deeper in the near future.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=65842a74f849" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/5-lessons-i-learned-by-designing-for-accessibility-65842a74f849">5 lessons I learned by designing for 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>
    </channel>
</rss>