<?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 Katie Del Angel on Medium]]></title>
        <description><![CDATA[Stories by Katie Del Angel on Medium]]></description>
        <link>https://medium.com/@katiedel?source=rss-ba2c61a8dd9e------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*NUDCSzlPW_gnCfV-k7bGbw.jpeg</url>
            <title>Stories by Katie Del Angel on Medium</title>
            <link>https://medium.com/@katiedel?source=rss-ba2c61a8dd9e------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 06:48:49 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@katiedel/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[How to test for accessibility with users at every design stage]]></title>
            <link>https://medium.com/@katiedel/how-to-test-for-accessibility-with-users-at-every-design-stage-ec655fed7878?source=rss-ba2c61a8dd9e------2</link>
            <guid isPermaLink="false">https://medium.com/p/ec655fed7878</guid>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[accessibility-testing]]></category>
            <category><![CDATA[ui-design]]></category>
            <category><![CDATA[accessibility]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Katie Del Angel]]></dc:creator>
            <pubDate>Wed, 11 Aug 2021 16:50:03 GMT</pubDate>
            <atom:updated>2021-08-11T17:01:21.336Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="An illustration with a coral-red background showing an email envelope icon with a roll of paper unfolding out of it, with icons on the paper, including keyboard cursor, audio and sight and icons." src="https://cdn-images-1.medium.com/max/1024/1*ENwJbZbzitUFfv3iHN9snw.jpeg" /><figcaption>Illustration by Alisha Giroux.</figcaption></figure><h4>A research template to test solutions for people with disabilities</h4><p>User research has always been a core part of the design process at Shopify. But, until recently, I’d only ever participated in sessions as a notetaker, or secondary facilitator.</p><p>This year, that all changed. Through a partnership with <a href="https://makeitfable.com/">Fable, an accessibility testing platform</a>, I developed and executed four research sessions for my project. As a result, the team was able to successfully improve the Shopify Email product experience to make it much more inclusive.</p><p>Going from 0 to 60 in user research testing as a product designer was a daunting task — especially in a realm I was still just learning about (<a href="https://ux.shopify.com/accessibility-is-more-than-a-technical-problem-ca6bb9dee8ce">designing for accessibility</a>). In this post, I’ll share how I leveraged user testing with people using assistive technologies — which let me improve Shopify Email by gaining first-hand feedback at every stage of the design process — and suggest a template you can use to plan your own user tests.</p><p>Taking the time to integrate <a href="https://ux.shopify.com/designing-for-cognitive-disabilities-b2933d58c278">inclusive user research</a>, beyond just applying “best practices,” is invaluable to ensure products can be used by a broader audience. The hardest part is just getting started.</p><h3><strong>The problem</strong></h3><p>Shopify Email was initially built in a way that was inaccessible to some users of assistive technology. In particular, we noticed that the ability to add a new section to an email was only possible using a mouse. This meant some people using alternative navigation, most screen reader users, and people who rely on the keyboard alone, were limited in how much they could customize an email.</p><p>That was a huge problem: around 15% of our merchants self-identify as having a vision disability.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UMLDT2O2j_Q6a777MJqpbQ.png" /><figcaption><em>In the initial experience, adding an email section was only visible while hovering between sections.</em></figcaption></figure><p>Additionally, the tab sequence navigation and labeling for screen readers needed refinement to allow those users to complete core task flows within the app more easily. To make our product more usable for more merchants, we sought to advance Shopify Email to better meet the <a href="https://www.w3.org/WAI/standards-guidelines/wcag/glance/">Web Content Accessibility Guidelines (WCAG)</a>.</p><p>Some of the key considerations I established with my team were:</p><ul><li>Introducing a keyboard shortcut wouldn’t be enough to make the product accessible; the option to add a section needed to be a permanently visible action.</li><li>A new “add section” solution should consider future mobile feasibility.</li><li>The tab sequence should follow best practices and provide a logical way to move between sections and their corresponding settings.</li></ul><h3><strong>What we designed</strong></h3><p>To enable blind and low-vision users to add a new section to their email template, we added a permanently visible button in the Editor. We also maintained the hover-over behavior for those already familiar with that way of doing things.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2FWqjNrWJGSJCN5A2rv7%2Ftwitter%2Fiframe&amp;display_name=Giphy&amp;url=https%3A%2F%2Fgiphy.com%2Fgifs%2FWqjNrWJGSJCN5A2rv7&amp;image=https%3A%2F%2Fmedia2.giphy.com%2Fmedia%2FWqjNrWJGSJCN5A2rv7%2Fgiphy.gif%3Fcid%3D790b7611c19cda79899a10ffa2f85ef1c88cc0479a21b915%26rid%3Dgiphy.gif%26ct%3Dg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="288" frameborder="0" scrolling="no"><a href="https://medium.com/media/e49ffde17bfbfb60f583bdbfda2f287d/href">https://medium.com/media/e49ffde17bfbfb60f583bdbfda2f287d/href</a></iframe><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2FbYgRqLwvvilXrEpVPh%2Ftwitter%2Fiframe&amp;display_name=Giphy&amp;url=https%3A%2F%2Fgiphy.com%2Fgifs%2FbYgRqLwvvilXrEpVPh&amp;image=https%3A%2F%2Fmedia3.giphy.com%2Fmedia%2FbYgRqLwvvilXrEpVPh%2Fgiphy.gif%3Fcid%3D790b76116b97fef911b89d96a5137a476e15c27bc9501feb%26rid%3Dgiphy.gif%26ct%3Dg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="244" frameborder="0" scrolling="no"><a href="https://medium.com/media/a5cec8f5bac154d598e3a67c26fa427d/href">https://medium.com/media/a5cec8f5bac154d598e3a67c26fa427d/href</a></iframe><p>In parallel with these changes, we updated the labelling and tab sequencing to ensure alternative navigation users were able to move around the app more easily.</p><p>To ensure the usability of all of these improvements for people using assistive technologies, we ran four research sessions with Fable testers.</p><h3><strong>About Fable</strong></h3><p>Fable is a user testing platform that facilitates recruitment of professional testers to help explore and vet solutions at all stages of fidelity.</p><p>All testers are people who use assistive technologies and some even have a technical background to offer implementation recommendations. (And, yes, all are under NDA.)</p><p>We piloted using Fable at Shopify in 2019 and again at the end of 2020. It’s been used by the Retail team for interviews, and by other teams for checking products after they’ve been built. The Email team is the first team at Shopify to use Fable more broadly, with multiple requests across different design stages.</p><h3><strong>Testing accessibility with Fable</strong></h3><p>Shortly after kicking off the project, we engaged the Fable community over the course of two months. Each round of research (four in total) took about 3–4 days to complete, accounting for recruitment time. (Because the Fable platform operates almost like a marketplace, finding testers was always the easy part once I submitted a research request.) While I ran point on three research sessions, the lead engineer on the project also stepped in to lead his own session.</p><p>To familiarize myself with the Fable platform, and help the team learn common preferences of folks using assistive technologies, I ran several informal, educational interviews. After I had a loose concept of a solution in mind, I conducted co-design sessions with Fable testers to validate the approach before polishing high-fidelity prototypes. When we were refining the tab sequencing solution, our lead engineer took the lead on a more casual implementation discussion with a Fable tester who had technical expertise. And finally, once the solution was live behind a beta flag, we conducted a few unmoderated sessions with testers running through a simple task flow.</p><p>After every research round, I would aggregate insights into a short, high-level deck to share with the project team for visibility. Although the research sessions did not surface any major red flags, they did help us build confidence that our solutions were actually accessible from a human perspective — as well as a technical one.</p><h3><strong>The impact: button vs. hover</strong></h3><p>When we initially rolled out the new button feature, we ran a 2-week experiment to track the user behavior of using the new button compared to the original hover behavior for adding a section. We saw 20% of users only used the button during their session of editing an email, which indicates that there are potentially folks who either didn’t realize they could add, didn’t know how to add, or were not able to add sections before this button existed.</p><p>Although the long-tail impact of this button since launch doesn’t indicate that merchants are adding more sections overall, the team is confident the improved experience has enabled more merchants to use the app successfully based on our initial experiment after launch.</p><p>This project was my first experience running this type of usability testing. While the project helped us successfully make our Email product more inclusive and usable, we’re still trying to work out a usability testing workflow that scales for all our projects.</p><p>Here are my tips and takeaways from the experience:</p><ul><li>Familiarizing myself with common challenges and user behaviors for folks using assistive technologies — before imagining a solution — helped build empathy and changed the lens I used when initially envisioning a solution.</li><li>Vetting our solution from both a usability and technical perspective ensured an experience that was accessible from both a human-centric and compliance-centric perspective.</li><li>Testing is easy — getting started is the hard part. Just think of your user testing like a conversation.</li></ul><p>To help you get started, below is a useful starting point for planning accessibility testing at every design stage.</p><figure><img alt="An illustration of a green envelope with a piece of paper showing an icon of an eye on a piece of paper inside." src="https://cdn-images-1.medium.com/max/400/1*mCrx3Bo_UMtqk-lZHID_WA.png" /></figure><h3><strong>A template for accessibility user testing</strong></h3><p>This template outlines a series of four research sessions, conducted at each design stage, to help successfully validate your products and solutions with people with disabilities.</p><h4><strong>Session 1: Informational interviews</strong></h4><p><strong>What</strong>: Casual 1:1 conversations to understand common challenges for people using assistive technologies (AT).<br><strong>When</strong>: Before exploring specific solutions to the problem at hand<br><strong>Who</strong>: 3 users: 1 screen reader, 1 screen magnification, 1 alternative navigation (voice control)<br><strong>Why</strong>:</p><ul><li>To get your feet wet using Fable and get comfortable conducting UX research</li><li>To understand the general preferences and challenges of folks using different AT</li><li>To get a quick “first impression” review of the existing product experience from folks using AT</li></ul><p><strong>How</strong>: Casual Q&amp;A followed by a very basic task flow within the product overall.</p><ul><li>Start with a quick company overview, and context about the specific product or app for the testers</li><li>General AT preference questions, to educate yourself and your team</li><li>High-level, guided task flow</li></ul><p><strong>Research questions that helped inform a detailed script:</strong></p><ol><li>What kinds of assistive technologies are folks using to interact with web applications?</li><li>What are their preferences in terms of using those technologies?</li><li>What are the frequent pain points they have? What do they consider characteristics of great experiences?</li><li>What does the product or app look like/how does it behave when using AT?</li></ol><h4><strong>Session 2: Design review/concept preview</strong></h4><p><strong>What</strong>: Moderated user interview to validate a proposed concept or solution<br><strong>When</strong>: With initial screen mockups, before build begins<br><strong>Who</strong>: 3 users: 1 screen reader, 1 screen magnification, 1 alternative navigation (voice control)<br><strong>Why</strong>:</p><ul><li>To identify any potential pitfalls in a proposed design, before moving into high-fidelity prototype and design</li><li>To vet initial impressions and user sentiment about solution</li></ul><p><strong>How</strong>: Quick Q&amp;A followed by a guided task flow with the proposed solution</p><ul><li>Start with a quick company overview, and context about the product for user</li><li>General AT preference questions</li><li>Share Figma link (or screen share your mockups) to get initial impression of solution</li></ul><p><strong>General format of questions while showing prototype:</strong></p><ul><li>Based on this mockup, how would you go about [doing some task]?</li><li>What would you expect to happen when you do that?</li><li>Can you tell me your impression of this mockup at this point?</li><li>What do you think about the experience around [doing that task] based on this mockup?</li></ul><p><strong>Research questions:</strong></p><ol><li>What is lacking or misaligned with their expectations of how the proposed flow should work?</li><li>Is the potential solution accessible from a human (versus technical) perspective?</li></ol><h4>Session 3: Implementation validation</h4><p><strong>What</strong>: Collaborative discussion between engineering and Fable tester to discuss implementation.<br><strong>When</strong>: After build begins, before launch<br><strong>Who</strong>: 1 screen reader user<br><strong>Why</strong>: To quickly test and discuss the technical implementation of our solution (in particular, labels and behavior for the tabbing sequencing)<br><strong>How</strong>: Informal discussion led by engineering</p><ul><li>Demo solution for user</li><li>Discuss any pitfalls and plan ways to address them</li></ul><h4>Session 4: Compatibility testing</h4><p><strong>What</strong>: Unmoderated testing of the solution to ensure users can complete the task at hand.<br><strong>When</strong>: Just before launch, when solution is usable in beta<br><strong>Who</strong>: 5 random users of different AT (i.e. screen reader, screen magnification, alternative nav)<br><strong>Why</strong>: To validate that our implementation technically and functionally supported the core task flow for most users<br><strong>How</strong>: Unmoderated user test in demo store</p><ul><li>Provide login credentials and specific 10-step task flow for users to test</li><li>Include company and product context brief with login instructions</li><li>Create any foundational drafts or individual test environments to provide as a base for each user flow</li></ul><p><strong>Research questions:</strong></p><ol><li>Can users accomplish the core task using their respective assistive technology?</li><li>Does the experience meet expectations of users of assistive technologies?</li></ol><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ec655fed7878" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[On Moving Alone]]></title>
            <link>https://medium.com/@katiedel/on-moving-alone-ff86961d3e4c?source=rss-ba2c61a8dd9e------2</link>
            <guid isPermaLink="false">https://medium.com/p/ff86961d3e4c</guid>
            <category><![CDATA[inspiration]]></category>
            <category><![CDATA[life]]></category>
            <dc:creator><![CDATA[Katie Del Angel]]></dc:creator>
            <pubDate>Fri, 22 Jul 2016 14:40:14 GMT</pubDate>
            <atom:updated>2017-07-23T02:55:58.441Z</atom:updated>
            <content:encoded><![CDATA[<p>When we relocate — by choice, or by circumstance — we are forced to face our own mortality.</p><p>Not in the “we all must die someday” sense, but in the “we are only human” sense. That sense is particularly astute when we move alone.</p><p>As a single unit, you are not much — just one, lone human in a very large, very busy world.</p><p>You are not a bird, nor wizard. Uprooting a home to the other side of the city takes planning, and more planning. You cannot simply leave the old and start anew. You must dismantle, piece by piece, everything you’ve built in your existing home before carefully, painstakingly planning how you will get it into the new. And how you will move yourself there, too.</p><p>Sure, there are companies to move the Stuff — but what about yourself? You pop into your car, hop on a bike, or shuffle into a taxi, and hurry on over to New Home to greet your friendly movers. Perhaps you’ve chosen a fancy new high-rise type, and your building manager is there to welcome you. But otherwise, you’re reveling in this moment with No One. That innate need to sentimentalize, to share this moment with someone “special” — it’s only you. And you’re only one, single human.</p><p>You are only human, with two empty hands. Seemingly simple tasks like disassembling a bed, or taping up a large box, are exercises in acrobatics without a second human around.</p><p>And speaking of taped up boxes…</p><p>Inevitably, you have come to hold so many things. Old Home has become a vessel of memories.</p><p>Moving requires organization. To organize, we must understand what we have… which inevitably reminds us of what we do not. Keepsake or memento, it always reminds us of what is no more, and Old Home is a goldmine of those little items. As a single person, you’ve probably culminated dozens or hundreds of them. But they are just things — things to which we attach memories but not other tangible humans. Because you can’t, you can only hold onto the Things. And you are just one, single human.</p><p>Even if you’re not the nostalgic sort, you still have these “emotional objects.” We all do.</p><p>As a human, you were expected to “nest,” as we call it. You bought furniture that was meant for this space. Furniture that was, likely, shared with another human at some point or another. For better or worse, there was a moment shared with Someone in some quadrant of Old Home… but once that furniture goes it returns to just an empty corner. The furniture is a pile of pieces. And you are just one, single human.</p><p>Maybe — quite probably — Old Home was never intended for more than your single being. But you aren’t a snail outgrowing a shell. There were people and things and moments loaded and unloaded in there with you. But now you must leave, and you’re still just one, single human.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ff86961d3e4c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The End of Delight?]]></title>
            <link>https://medium.com/@katiedel/the-end-of-delight-f060468fb039?source=rss-ba2c61a8dd9e------2</link>
            <guid isPermaLink="false">https://medium.com/p/f060468fb039</guid>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Katie Del Angel]]></dc:creator>
            <pubDate>Mon, 30 Mar 2015 16:23:29 GMT</pubDate>
            <atom:updated>2015-03-30T16:23:29.555Z</atom:updated>
            <content:encoded><![CDATA[<p>Since <a href="http://nymag.com/daily/intelligencer/2014/08/silicon-valley-whimsy-is-trumping-usefulness.html">at least mid-2014</a>, there’s been a bit of skepticism around the concept of “delight”. Trite. Trivial. Tacky. The word, in the digital space, suddenly carries the stigma of overly-ambitious gimmick.</p><p>Which, as you can imagine, is disconcerting after your pet project of 4 years was recently rebranded to encompass the very word. (For those out of the loop, I’m talking about <a href="http://delight.us/conference/">the Delight Conference</a>.) Founded as “Love at First Website” in 2004, it began as a local event to gather clients and industry professionals over lunch to discuss great design and digital work.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*MSIfJCmpbBRjPXcATtDB-A.jpeg" /><figcaption>Pure elation over the success of the 2014 event.</figcaption></figure><p>Fast forward to 2010, as we were all realizing digital “love” encompassed much more than beautiful website aesthetics or clever campaign work. When I came on board*, the vision for the event was taking off — as was traction around the concept of “delight” in experience design. In 2012, we rebranded to the Delight Conference.</p><p>Over four years, the event matured into a passionate, international community.</p><p>Featuring speakers from brands like <a href="http://www.simple.com/">Simple</a> (in beta, at the time), Disney, <a href="http://www.warbyparker.com/">Warby Parker</a>, <a href="http://www.bowanddrape.com/">Bow &amp; Drape</a>, Nordstrom, Zappos and many more, the conference served to gather the cream of the crop in exceptional customer experience design. With user experience, business strategy, engineering and marketing professionals in the audience, conversations around the event (before, during and after) reflected more than an industry buzzword: delightful experience design was a movement people wanted in on.</p><p>A <a href="http://www.fastcodesign.com/3042849/delightful-interaction-design-needs-to-die">recent Fast Company article,</a> which seems to attack the nature of delight, only underscores its true meaning. (Judging by the astute comments from other FastCo readers, it’s a pretty transparent attack anyways — but I digress.)</p><p>Over years of managing the Delight conference, I heard from both speakers and attendees what exactly “delight” means to them. To truly delightful brands, it isn’t “a cherry on top” piece of flair. People <strong>love</strong> brands like Nordstrom not for superficial surprises, but the meaningful interactions they create by understanding and anticipating needs of their customers. 100+ years of amazing customer service speaks volumes about the sustainability of their efforts.</p><p>Check out any number of <a href="http://delight.us/category/videos/">past talk videos</a> from the likes of NPR, Intel, Zipcar and more for more on what delight <em>really</em> is (and isn’t).</p><p>As the conversation around “delight” continues to grow, it was an exceptionally difficult thing to leave the Delight conference and community last month with my departure from ISITE. Though many have grown used to my face (and byline) on much of the content, the team behind the event actually spans over half the agency by now — it truly takes a village! While I don’t know what this next year will hold for the event, I do know the momentum and conversation around delight — the event and the broader concept — will only grow in scale and maturity. I’m looking forward to seeing what comes next…and enjoying some Delight Conf fun from the audience! ;)</p><p>*The Delight Conference is organized by ISITE Design, a digital agency in Portland, Oregon.</p><p><em>Originally published at </em><a href="https://www.linkedin.com/pulse/end-delight-katie-del-angel?trk=object-title"><em>www.linkedin.com</em></a><em> on March 27, 2015.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f060468fb039" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>