<?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 Dave Newton on Medium]]></title>
        <description><![CDATA[Stories by Dave Newton on Medium]]></description>
        <link>https://medium.com/@newtron?source=rss-a835de471a1a------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*JaDLL3p_8_ZiEEXY.png</url>
            <title>Stories by Dave Newton on Medium</title>
            <link>https://medium.com/@newtron?source=rss-a835de471a1a------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 15:17:09 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@newtron/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[Debugging your work conflicts (Or: Have you tried talking to them?)]]></title>
            <link>https://medium.com/@newtron/debugging-your-work-conflicts-or-have-you-tried-talking-to-them-43e50e45fe17?source=rss-a835de471a1a------2</link>
            <guid isPermaLink="false">https://medium.com/p/43e50e45fe17</guid>
            <category><![CDATA[communication]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[management]]></category>
            <dc:creator><![CDATA[Dave Newton]]></dc:creator>
            <pubDate>Tue, 28 Aug 2018 20:21:07 GMT</pubDate>
            <atom:updated>2018-08-30T16:24:24.929Z</atom:updated>
            <content:encoded><![CDATA[<p>Work conflicts are a fact of life. I don’t even just mean disagreements or healthy tension or compromise — I’m talking about actual conflicts where you walk away feeling frustrated, angry, or unsure how to move forward.</p><p>Luckily this type of conflict is somewhat rare at my workplace; more often than not, problems are solved quickly with no bad feels. But these conflicts do happen sometimes, and being prepared to handle them is a crucial skill for getting shit done.</p><p>As a lead (a.k.a. manager), I hear about problems like this from my team from time to time. If they’re feeling frustrated and not sure how to proceed, I usually start by asking them one question: “Have you talked to the other person about it?”</p><p>Recently I experienced this myself with another team, when I was trying to work through some changes and was feeling slowed down and frustrated by unclear process. I felt like I had hit a wall and the longer I felt blocked, the more frustrated I got.</p><p>I initially did nothing to solve this. Well, that’s not totally true: I complained/whined to a coworker because she’s a trusted peer and I wanted to vent a bit. She asked me that all-important question: “Have you talked to them about it?”</p><p>I hadn’t.</p><h3><strong>Debugging software</strong></h3><p>Just like problems in human relationships, software problems are a fact of life.</p><p>One of the most common struggles for junior developers (especially those who have not worked in large codebases) is debugging.</p><p>When developers are first starting their career, their focus often tends to be on making things work, not fixing things that are broken. Even when they come across problems, often the debugging they’re doing is trivial because they’re working on code they’ve written. They know how everything works, or at least how it’s supposed to work. They have all the context.</p><p>As developers start working on more complex problems, in larger code bases, with code they haven’t written, they won’t have all the context when they come across a barrier. Debugging gets trickier and those junior devs may be unprepared for how to handle it.</p><p>A pattern I’ve seen many times is:</p><ol><li>developer has a problem (e.g. an error they don’t understand)</li><li>developer gets frustrated: “eff this software, it’s stupid, why doesn’t it work the way I want?!”</li><li>developer asks for help from trusted peer or lead</li></ol><p>When they ask for help, they’ll often get the same answer back: “have you tried Googling it?”</p><p>Learning to debug effectively is a skill like any other, and it starts with acknowledging your anxiety about this thing you’re unfamiliar with, but diving in to explore it anyway. There’s nothing wrong with asking for help (it’s a great way to learn), but instead of asking <em>as a first step</em>, developers learn to start adding other tools to their debugging toolbelt: Googling error messages, reading stack traces, adding breakpoints into code, isolating test cases, etc. All of these actions give the developer more knowledge, more context, with which to understand and eventually solve the problem.</p><p>As their set of debugging tools grows, developers may not feel any less frustration or anxiety when they hit a nasty problem, but they are more equipped to resolve it in a healthy way.</p><p>By debugging, developers may learn that the fault was with the software (e.g. some legitimate bug); or they may find that the fault was with them (e.g. that they were using something incorrectly). Often the truth is somewhere in the middle: neither the dev nor the software are <em>wrong</em>, they’re just both making different assumptions about how things should work.</p><h3><strong>Debugging human problems</strong></h3><p>In my conflict with the other team (and with many other folks I’ve had these conversations with) we can see the same frustrated-junior-dev pattern play out:</p><ol><li>Dave has a problem (e.g. things aren’t working the way I expected and I don’t understand why)</li><li>Dave gets frustrated: “why doesn’t this team work the way I want?!”</li><li>Dave asks for help from trusted peer</li></ol><p>Because of my emotional reaction, I was blind to my own behaviour and the way forward. My co-worker asking me that simple question (“have you talked to them?”) forced me to acknowledge that in order to solve this I needed to dive into the problem. It reminded me that I needed to turn to other tools in my debugging toolbelt.</p><p>As soon as I talked to the other team I learned:</p><ul><li>I had some missing context</li><li>I had been making some incorrect assumptions</li><li>They agreed some parts of the process weren’t working as well as expected and had plans to improve them</li></ul><p>I also remembered that I need to assume positive intent: that team is made up of reasonable people and they want what’s best for the company and the people who work here.</p><p>The conversation was not emotionally charged, not accusatory, not about blame. It was a rational exploration of the issue we were having, and it had tangible outcomes: we both now have a better understanding of the frustrations each of us was feeling, and we can now work together towards improving things. My frustration melted away.</p><p>Just like debugging, having these conversations can give us greater context and clarity around what the problem is, why it’s happening, and how to move forward. By talking it out, we may learn that the fault was with the other person (e.g. some legitimate problematic behaviour); or we may find that the fault was with us (e.g. that we were doing something wrong). Often the truth is somewhere in the middle: neither us nor the other person are <em>wrong</em>, we’re just both making different assumptions about how things should work.</p><p><strong>The next time you run into a conflict with somebody at work, when you’re feeling frustrated and just can’t understand why they’re doing (or not doing) something, put on your debugging toolbelt and ask yourself “have I talked to them yet?”</strong></p><h4>More where this came from</h4><p>This story is published in <a href="http://blog.usejournal.com/">Noteworthy</a>, where thousands come every day to learn about the people &amp; ideas shaping the products we love.</p><p>Follow our publication to see more product &amp; design stories featured by the <a href="https://usejournal.com/?utm_source=usejournal.com&amp;utm_medium=blog&amp;utm_campaign=guest_post">Journal</a> team.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=43e50e45fe17" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Semantic HTML: The Unbearable Rightness of Being]]></title>
            <link>https://medium.com/@newtron/semantic-html-the-unbearable-rightness-of-being-9b3c493e1791?source=rss-a835de471a1a------2</link>
            <guid isPermaLink="false">https://medium.com/p/9b3c493e1791</guid>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[web-design]]></category>
            <category><![CDATA[front-end-development]]></category>
            <category><![CDATA[product-development]]></category>
            <category><![CDATA[accessibility]]></category>
            <dc:creator><![CDATA[Dave Newton]]></dc:creator>
            <pubDate>Thu, 14 Jul 2016 14:00:46 GMT</pubDate>
            <atom:updated>2016-09-20T20:04:07.784Z</atom:updated>
            <content:encoded><![CDATA[<p><em>This is the fourth post in a series on accessibility from Shopify’s UX team. We’re publishing posts every two weeks. </em><a href="https://medium.com/shopify-ux/make-commerce-better-for-everyone-b96f0621ddf3#.qkhbxkncz"><em>Check out the introduction</em></a>.</p><p>Using valid, semantic HTML is one of the most impactful ways to make your site more accessible. Writing semantic HTML means using the HTML element with the most specific, correct meaning for your task. For example, if you’re building a button, use a <strong>&lt;button&gt;</strong> element. With CSS and JavaScript you could make just about any element, e.g. a <strong>&lt;div&gt;</strong>, <em>look</em> like a button, but it won’t <em>be</em> a button.</p><p>This <em>being</em> is the reason semantic HTML is important for accessibility. Browsers have different behaviour depending on what an element <em>is</em>, not what it looks like. These differences can have a big impact on user experience.</p><h4>How semantic HTML affects users</h4><p>Consider this example (<a href="http://codepen.io/newtron/pen/wWqAVv">also available as a CodePen</a>):</p><pre>&lt;div class=&quot;btn&quot; onclick=&quot;alert(&#39;something&#39;)&quot;&gt;do something&lt;/div&gt;</pre><pre>&lt;a href=&quot;#&quot; class=&quot;btn&quot; onclick=&quot;alert(&#39;something&#39;)&quot;&gt;do something&lt;/a&gt;</pre><pre>&lt;button type=&quot;button&quot; class=&quot;btn&quot; onclick=&quot;alert(&#39;something&#39;)&quot;&gt;do something&lt;/button&gt;</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yh5Rwza0DrVWtc_uIFwTHw.png" /><figcaption>Three identical buttons</figcaption></figure><p>These three buttons look identical. When you click them, they all produce the desired behaviour — popping up an alert that says “something”. But they are marked up differently — the first as a <strong>&lt;div&gt;</strong> element, the second as an <strong>&lt;a&gt;</strong> element, and the third as a <strong>&lt;button&gt;</strong> element. These markup differences have some effects that may not be obvious:</p><ul><li>breaking keyboard navigation,</li><li>inappropriately shifting browser focus, and</li><li>creating incorrect descriptions in screen readers</li></ul><pre>&lt;div class=&quot;btn&quot; onclick=&quot;alert(&#39;something&#39;)&quot;&gt;do something&lt;/div&gt;</pre><p>The first button uses a <strong>&lt;div&gt;</strong> HTML element. <strong>&lt;div&gt;</strong>s don’t have much default styling, so the <strong>btn</strong> class is used by our CSS to make it look like a button. The <strong>onclick</strong> attribute tells JavaScript to create the alert when the <strong>&lt;div&gt;</strong> is clicked. (Even though this is called <strong>onclick</strong>, it can be triggered by a mouse click, a touchscreen tap, or hitting <strong>ENTER</strong> on a keyboard. This is also true elsewhere in this post when I mention “clicking”.)</p><pre>&lt;a href=&quot;#&quot; class=&quot;btn&quot; onclick=&quot;alert(&#39;something&#39;)&quot;&gt;do something&lt;/a&gt;</pre><p>The second button uses an <strong>&lt;a&gt;</strong> HTML element, a link. As in the first example, the <strong>btn</strong> class and <strong>onclick</strong> attribute provide the styling and behaviour we want. This a has an <strong>href</strong> value of <strong>#</strong>, which means that it is linking to the top of the page. More on that later.</p><pre>&lt;button type=&quot;button&quot; class=&quot;btn&quot; onclick=&quot;alert(&#39;something&#39;)&quot;&gt;do something&lt;/button&gt;</pre><p>The third button uses a <strong>&lt;button&gt;</strong> HTML element. Again, the <strong>btn</strong> class and <strong>onclick</strong> attribute provide the styling and behaviour.</p><p>We have three buttons that seem to be the same, but are all marked up using different HTML elements. What is the effect that these different elements have?</p><h4>Keyboard navigation</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UDeb3AU6FOnGpSfeVpnVqQ.png" /><figcaption>The last button, marked up with a &lt;button&gt; element, can be focused with the keyboard</figcaption></figure><p>If you were to try using your <strong>TAB</strong> key to navigate around the example, you’d be able to focus on the third example (<strong>&lt;button&gt;</strong>) and, depending on your browser, maybe the second example (<strong>&lt;a&gt;</strong>), but not the first (<strong>&lt;div&gt;</strong>).</p><p>Certain HTML elements are <em>focusable</em> by default and others aren’t. Keyboards and some other devices can navigate around the page by focusing on these elements. Being able to focus on an element is necessary to be able to interact with it. You can activate the third (<strong>&lt;button&gt;</strong>) example by hitting <strong>ENTER</strong> or <strong>SPACE</strong>, but you can’t do that with the first (<strong>&lt;div&gt;</strong>) example.</p><p>Many people, both disabled and not, use keyboards to navigate web sites. If you use a <strong>&lt;div&gt;</strong> to create a button, keyboard users that are not disabled might get frustrated and resort to using their mouse. Users with motor difficulty may not be able to use a mouse, and will be left unable to use your button at all.</p><h4>Focus shifting</h4><pre>&lt;a href=&quot;#&quot; class=&quot;btn&quot; onclick=&quot;alert(&#39;something&#39;)&quot;&gt;do something&lt;/a&gt;</pre><p>Remember when I said that the <strong>href=“#”</strong> on the second (<strong>&lt;a&gt;</strong>) example button creates a link to the top of the page? This can be an accessibility problem if it’s not controlled for, because it can take a user out of their context.</p><p>Imagine this button was at the bottom of a long page with lots of content on it. Clicking the button could scroll the user up to the top of the page, and shift the keyboard focus up to the top as well. A non-disabled user might get confused and annoyed, and scroll back down to the bottom. A keyboard user might get confused and very annoyed, because now they need to tab all the way through the entire page to get back where they were. A screen reader user might get very confused; they might not immediately realize the screen reader has shifted focus back to the top of the page.</p><h4>Screen reader descriptions and navigation</h4><p>When visually impaired users navigate with a screen reader, they rely on how it describes HTML elements. It’s the only way they can know what something is and how they can interact with it.</p><p>The three example buttons are described differently by VoiceOver in Safari on macOS:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*7caRpb-3ajWnlmJj." /><figcaption>The first button, marked up with a &lt;div&gt;, is described as “do something, clickable” by VoiceOver</figcaption></figure><p>The first example (<strong>&lt;div&gt;</strong>) is described as “clickable”. That’s not bad, but there’s no sign that this is actually a button. The distinction may seem trivial, but lots of things are clickable — links, buttons, form inputs, and so on. By not being specific, this could leave the user suspicious about what clicking the <strong>&lt;div&gt;</strong> will actually do.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*y-uDzaaB_1-mv1Co." /><figcaption>The second button, marked up with an &lt;a&gt;, is described as “link, do something” by VoiceOver</figcaption></figure><p>The second example (<strong>&lt;a&gt;</strong>) is described as a “link” (because it is, even if it doesn’t look like one!). A screen reader user might expect that clicking this link would take them to another page, not that it would trigger on-page behaviour. Links are <em>navigation</em> elements — the expectation is that they take you somewhere.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*TK9OCbsWalquCDDa." /><figcaption>The third button, marked up with a &lt;button&gt;, is described as “do something, button” by VoiceOver</figcaption></figure><p>The third example (<strong>&lt;button&gt;</strong>) is described as a “button” (because it is!). To a screen reader user, this conveys the appropriate expectation, that clicking the button will <em>do something</em>.</p><p>These different HTML elements can affect how a screen reader user navigates the page. For example, VoiceOver has a “rotor” that lists different types of elements and lets users skip to a particular one. Amongst other things, the rotor has areas for “links” and “form controls”.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*22L2B-GIzcoFNJx1." /><figcaption>The VoiceOver rotor lists the second button, marked up with an &lt;a&gt;, in its “Links” area</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*V9Lvh8-fDzq2k9kW." /><figcaption>The VoiceOver rotor lists the third button, marked up with a &lt;button&gt;, in its “Form Controls” area and says it’s a button</figcaption></figure><ul><li>the first example (<strong>&lt;div&gt;</strong>) doesn’t get listed in either</li><li>the second example (<strong>&lt;a&gt;</strong>) shows up in the “links” area (setting false expectations for what it will do)</li><li>the third example (<strong>&lt;button&gt;</strong>) shows up in the “form controls” area as a “button” (correctly setting expectations)</li></ul><h4>&lt;button&gt; is the best choice for a button</h4><p>To recap:</p><ul><li><strong>&lt;div&gt;</strong>: has no semantic meaning, is not keyboard focusable, described as “clickable” by VoiceOver, not listed in VoiceOver’s rotor</li><li><strong>&lt;a&gt;</strong>: has navigational semantics, might be keyboard focusable, might unintentionally shift focus/context, described as a “link” by VoiceOver, listed in the “link” area of VoiceOver’s rotor</li><li><strong>&lt;button&gt;</strong>: has button semantics, is keyboard focusable, doesn’t shift focus/context, described as a “button” by VoiceOver, listed in the “form controls” area of VoiceOver’s rotor.</li></ul><p>Based on this data, using a <strong>&lt;button&gt;</strong> to make a button is the best choice!</p><p>It <em>is</em> possible to override all this default behaviour and make a <strong>&lt;div&gt;</strong> or an <strong>&lt;a&gt;</strong> work like a button. You could:</p><ul><li>add the aria <strong>role=“button”</strong> attribute to them to make them get described properly by screen readers</li><li>add a <strong>tabindex=“0”</strong> to the <strong>&lt;div&gt;</strong> to make it focusable</li><li>add a <strong>return false</strong> to the <strong>&lt;a&gt;</strong>’s <strong>onclick</strong> JavaScript to prevent focus shifting</li></ul><p>But why bother with that when you get all this behaviour free, out-of-the box with <strong>&lt;button&gt;</strong>? It’s super easy to forget to add these things, especially when the button looks and (for some users) behaves “right” without them. It’s far easier to use the correct HTML element for the job you’re doing.</p><p>This example was about buttons, but remember that the same lesson is true for <em>all</em> HTML elements. It’s always best to use the most specific, most appropriate HTML element for the task at hand. Let the browser’s built-in functionality do the hard work for you!</p><h4>Why valid HTML is important</h4><p>Now that we’ve gone through why <em>semantic</em> HTML is important, I want to briefly touch on the importance of <em>valid</em> HTML.</p><p>An accessible experience is made up of three layers:</p><ul><li>your code,</li><li>how the browser interprets your code, and</li><li>how an assistive technology or input device interacts with the browser’s interpretation of your code.</li></ul><p>Bugs and unexpected behaviour can sneak in at any stage, and a bug at any stage can make a screen reader describe something incorrectly. Browser and screen reader bugs are an unfortunate fact of life. The only part you have control over is the quality of your own code. To minimize problems, it’s crucial to make sure the markup you’re writing is free from bugs.</p><p>This is an example of a bug that snuck in at Shopify that was subtle, but had a big accessibility impact:</p><pre>&lt;label for=&quot;offer_set_offers_attributes_0_price_9999&quot;&gt;Offer price&lt;/label&gt;</pre><pre>&lt;input min=&quot;0&quot; step=&quot;any&quot; value=&quot;99.99&quot; type=&quot;number&quot; name=&quot;offer_set[offers_attributes][0][price]&quot; id=&quot;offer_set_offers_attributes_0_price&quot; /&gt;</pre><p>Can you spot the problem?</p><p>The <strong>&lt;label&gt;</strong>’s <strong>for</strong> attribute doesn’t match the <strong>&lt;input&gt;</strong>’s <strong>id</strong> attribute. The function that generated this markup mistakenly added the <strong>&lt;input&gt;</strong>’s <strong>value</strong> as part of the <strong>&lt;label&gt;</strong>’s <strong>for</strong> attribute. Instead of <strong>offer_set_offers_attributes_0_price</strong>, it used <strong>offer_set_offers_attributes_0_price_9999</strong>.</p><p>The result is that the <strong>&lt;label&gt;</strong> and the <strong>&lt;input&gt;</strong> are actually not associated with each other at all. Visually, everything looks right. But the bug introduces two accessibility problems:</p><ul><li>clicking the <strong>&lt;label&gt;</strong> won’t focus the form <strong>&lt;input&gt;</strong> to allow typing</li><li>a screen reader will describe the <strong>&lt;input&gt;</strong> wrong, by not saying the <strong>&lt;input&gt;</strong> is an “offer price”</li></ul><p>We caught this bug by running our markup through an <a href="https://checker.html5.org/">HTML validator</a>. The validator told us that “the for attribute of the label element must refer to a non-hidden form control”. In other words, that it was wrong for the <strong>&lt;label&gt;</strong>’s <strong>for</strong> attribute to point to something that didn’t exist. By validating our HTML we were able to squash this accessibility bug.</p><h4>Challenges Shopify is facing</h4><p>“Don’t write bad HTML” seems like a kind of easy thing to do, and “fix our existing bad HTML” doesn’t sound too tricky either. A lot of articles and conference talks will tell you to do this stuff without acknowledging some of the ways it can be hard.</p><ul><li><strong>Legacy content.</strong> With an organization and product as old and large as Shopify, there’s going to be legacy content. When we identify legacy code as needing cleanup or refactoring, it can be hard to find the people and time needed to update it.</li><li><strong>Lack of awareness.</strong> Within any large organization there are going to be diverse skillsets. That is <em>good</em>. But it means that not everybody will know a lot (or anything) about accessibility, or about semantic HTML.</li><li><strong>Imperfect tooling.</strong> Shopify has some HTML validation built into its test suite, but it doesn’t check against the whole HTML spec. (That’s how the label bug mentioned above snuck into our code.) We don’t currently have any automated tests checking the semantics of our HTML.</li></ul><p>We’re trying a bunch of approaches to solve these problems, including work to level-up both our devs and our tooling. Future articles in this series will touch on some of these approaches.</p><h4>Get started now!</h4><p>If you want to check your existing markup for validity, try the <a href="https://checker.html5.org/">Nu HTML Checker</a>. This tool gets updated frequently so it’s always in sync with current HTML specifications.</p><p>Checking the semantics of your markup can be a little trickier, but there are a few things you can try to get things started:</p><ul><li>Unplug your mouse. Can you still use your site? Is anything broken?</li><li>Start to read through parts of <a href="https://www.w3.org/TR/html5/">the HTML specification</a> — there’s even <a href="https://developers.whatwg.org/">a version specifically for web developers</a>!</li><li>Learn to test with a screen reader, like VoiceOver on macOS or NVDA on Windows. It will be very foreign and confusing at first, but hearing how your content gets described by the screen reader can be enlightening.</li></ul><p>Like every part of web development, writing valid, semantic HTML can sometimes be tricky, but that doesn’t mean it’s not worth doing. You might be facing some of the same challenges as us, or you might have different barriers. Whatever these may be, don’t let them stand in your way, and don’t get overwhelmed. Dive in and get started writing semantic HTML now. The sooner you do, the quicker you’ll have an impact on your users.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9b3c493e1791" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Make commerce better for everyone]]></title>
            <link>https://medium.com/@newtron/make-commerce-better-for-everyone-b96f0621ddf3?source=rss-a835de471a1a------2</link>
            <guid isPermaLink="false">https://medium.com/p/b96f0621ddf3</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[front-end-development]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[accessibility]]></category>
            <dc:creator><![CDATA[Dave Newton]]></dc:creator>
            <pubDate>Thu, 19 May 2016 14:05:20 GMT</pubDate>
            <atom:updated>2019-06-19T14:37:58.104Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*knWj0wZsc5djVsBprUMxCA.jpeg" /><figcaption>Our mission: make commerce better for everyone</figcaption></figure><p>At Shopify, our mission is to <em>make commerce better for everyone</em>. When we say better, we’re talking about caring deeply about making quality products. To us, a quality web product means a few things: certainly beautiful design, engaging copy, and a fantastic user experience, but just as important are inclusivity and the principles of <a href="https://en.wikipedia.org/wiki/Universal_design">universal design</a>.</p><p>“Everyone” is a pretty big group. It includes our merchants, their customers, our developer partners, our employees, and the greater tech community at large, where we love to lead by example. “Everyone” also includes:</p><ul><li>9.1% of adults with vision trouble [Source: <a href="http://www.cdc.gov/nchs/fastats/disability.htm">Disability and Functioning, CDC</a>], and 8% of men and 0.5% of women who are color blind [Source: <a href="http://www.colourblindawareness.org/colour-blindness/">Color Blind Awareness</a>].</li><li>16.8% of adults with hearing trouble [Source: <a href="http://www.cdc.gov/nchs/fastats/disability.htm">Disability and Functioning, CDC</a>].</li><li>15.1% of adults with physical functioning difficulty [Source: <a href="http://www.cdc.gov/nchs/fastats/disability.htm">Disability and Functioning, CDC</a>].</li><li>4.4% of adults with cognitive disabilities [Source: <a href="http://www.disabilitycompendium.org/docs/default-source/2014-compendium/annual-report.pdf">2014 Disability Statistics Annual Report, UNH</a>].</li></ul><p>We take our mission to heart, so it’s important that Shopify products are useable and useful to all our users. This is something we’ve been thinking about and working on for a few years, but it’s an ongoing, difficult challenge. Luckily, we love tackling challenging problems and we’re constantly chipping away at this one. We’ve learned a lot from the community and think it’s important to contribute back, so — in celebration of <a href="http://www.globalaccessibilityawarenessday.org/">Global Accessibility Awareness Day</a> — we’re thrilled to announce a series of posts on <a href="https://en.wikipedia.org/wiki/Accessibility">accessibility.</a></p><p>Over the next few weeks, we’ll be releasing posts about some of the real-world problems we’ve faced while trying to make different parts of Shopify accessible and how we’re trying to overcome them. Like many other teams, we’re not starting from scratch: with these posts we want to dig into our approach for making an existing platform accessible. You’ll hear from a bunch of talented people on our UX team — front end developers, designers, content specialists, and user experience researchers — who work closely with engineering and product teams to solve these problems. For this round, we’re releasing seven articles, with a new one dropping every two weeks. We’ll cover:</p><ul><li><a href="https://medium.com/@ry5n/in-plain-sight-5639c9afb4c6">In Plain Sight: Text, Contrast, and Accessibility</a> by Ryan Frederick</li><li><a href="https://medium.com/shopify-ux/how-much-is-that-t-shirt-in-the-browser-window-5804d9043ad8">How Much is that T-shirt in the Browser Window</a> (accessible pricing in Shopify themes) by Steve Bosworth</li><li><a href="https://medium.com/shopify-ux/writing-for-all-people-how-to-use-alternative-text-well-1205a18307a1#.izw9gzaa9">Writing for all people: how to use alternative text well</a> by Elizabeth Sahadeo</li><li><a href="https://medium.com/shopify-ux/semantic-html-the-unbearable-rightness-of-being-9b3c493e1791#.97h35dx34">Semantic HTML: The unbearable rightness of being</a> by Dave Newton</li><li><a href="https://medium.com/shopify-ux/lessons-from-building-mobile-friendly-accessible-data-tables-1e05c6924eaf#.eazj5tp2y">Lessons from building mobile-friendly, accessible data tables</a> by Tetsuro Takara</li><li><a href="https://medium.com/shopify-ux/how-to-run-accessibility-testing-demos-602005e176d0#.oq3lpyaks">How to run accessibility testing demos</a> by Arthur Gouveia</li><li><a href="https://medium.com/shopify-ux/creating-an-accessible-culture-199aaec12232#.37vsvhd3o">Creating an accessible culture</a> by Monika Piotrowicz</li></ul><p>We hope you’ll find these useful and that they’ll help you make your product (and industry!) better for everyone. Feel free to drop us comments and questions in the posts; we want this to be a conversation.</p><p>PS If you’re passionate about quality and are looking for an awesome place to work, check out <a href="https://www.shopify.com/careers/search?specialties%5B%5D=6/&amp;utm_source=uxblog&amp;utm_medium=post&amp;utm_term=1ddf3">our Careers page</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b96f0621ddf3" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>