<?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 Hope Turner on Medium]]></title>
        <description><![CDATA[Stories by Hope Turner on Medium]]></description>
        <link>https://medium.com/@hopeturner?source=rss-73e0ce48c6af------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*l6E-73593t2v9YYIuH1VJg.png</url>
            <title>Stories by Hope Turner on Medium</title>
            <link>https://medium.com/@hopeturner?source=rss-73e0ce48c6af------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 19:11:54 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@hopeturner/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[The accessibility work nobody sees]]></title>
            <link>https://hopeturner.medium.com/the-accessibility-work-nobody-sees-061e3f25fd52?source=rss-73e0ce48c6af------2</link>
            <guid isPermaLink="false">https://medium.com/p/061e3f25fd52</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[web-accessibility]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[design-systems]]></category>
            <dc:creator><![CDATA[Hope Turner]]></dc:creator>
            <pubDate>Sat, 17 Oct 2026 11:56:37 GMT</pubDate>
            <atom:updated>2026-10-17T11:56:37.810Z</atom:updated>
            <content:encoded><![CDATA[<h4>How designers can shift left and build what people can actually use.</h4><p>Let’s be honest, most of us learned accessibility the hard way. Something fails an audit, a ticket bounces back, and someone explains what went wrong after the work already shipped.</p><p><strong>That’s not on you. It’s a training gap.</strong></p><p>Most design programs barely touch accessibility, so we pick it up piecemeal on the job, usually right after something breaks.</p><p>The good news? The fastest fix isn’t another checklist. It’s seeing real work… the actual problem, and the actual design decision that would have headed it off.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/540/1*nrLtOsxtuHBNKTTZWsmkzw.jpeg" /><figcaption>Common Accessibility Pitfalls</figcaption></figure><h3>Two hours of real examples</h3><p>On October 13, <a href="https://www.linkedin.com/in/cindyschaffnerseeingblind/"><strong>Cindy Schaffner, a Senior Accessibility Specialist</strong></a><strong>,</strong> and I got to present “<strong>Accessible by Design: Bridging the Gap from Concept to Code</strong>” at <a href="https://www.section508.gov/event/itacm-oct2026/"><strong>GSA’s IT Accessibility Community Meeting</strong></a><strong>.</strong></p><p>We kept it real. Cindy walked through actual Section 508/Trusted Tester Program issues from audits, including the ones that keep popping up project after project.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BVX5t9dtDAtTghdc4v644A.png" /></figure><p>Then I showed what designers can do earlier, while a fix still takes minutes instead of a whole sprint. That’s what people mean by “<strong>shifting left</strong>”: moving accessibility from the end of the timeline, where it’s expensive, to the beginning, where it’s cheap and easy.</p><h3><strong>Want to dig in and see examples?</strong></h3><p>The <a href="https://www.section508.gov/~assets/accessible-by-design-itacm-oct-2026.pptx"><strong>full presentation deck</strong></a> is free to download from GSA’s <a href="https://www.section508.gov/training/presentations-workshops/"><strong>Section 508 presentations and workshop materials page</strong></a><strong>.</strong> (While you’re there, poke around the past community meeting decks too).</p><h3>The fixes you can see</h3><p>Some accessibility problems come with a nice, clean before and after. Those are the easy ones to teach.</p><p><strong>Error messages.</strong> A field turns red and… that’s it. A screen reader user hears nothing, and someone with color blindness might not notice anything changed. The fix happens in design, not code: a clear message right next to the field that says what went wrong and how to fix it. (Or better yet, great contextual help or instructions to prevent errors in the first place, but I digress!)</p><p><strong>Color contrast.</strong> Light gray text on white looks so clean in a mockup. In the real world, plenty of people can’t read it. Checking contrast while you’re picking your palette takes seconds. Fixing it after launch can mean touching every screen that uses that color.</p><figure><img alt="Example of a good visual treatment of an error in a form. There is dark red bold text and the fields are outlined in red. There is a bold vertical red bar that draws the user’s attention to the area." src="https://cdn-images-1.medium.com/max/1024/1*Ai5sWqvWy2_EeF_4VOY0WQ.png" /><figcaption>GOV.UK Error Message Example</figcaption></figure><p><strong>Want to get these right? Here’s where I’d start:</strong></p><ul><li><strong>Error messages:</strong> The GOV.UK Design System’s <a href="https://design-system.service.gov.uk/components/error-message/"><strong>error message guidance</strong></a> is one of the best plain-language guides to what to say, and the W3C’s <a href="https://www.w3.org/WAI/tutorials/forms/notifications/"><strong>User Notification tutorial</strong></a><strong> </strong>covers how to make sure screen readers announce it.</li><li><strong>Color contrast:</strong> The <a href="https://webaim.org/resources/contrastchecker/"><strong>WebAIM Contrast Checker</strong></a> tells you in seconds whether your colors pass, and GSA has a short <a href="https://www.section508.gov/training/create/making-color-usage-accessible/webaim-contrast-checker/"><strong>video walkthrough of how to use it</strong></a><strong>.</strong></li></ul><h3>The fixes nobody sees</h3><p>Then there’s the work with no visual “after” at all. Honestly, this is where we’re letting each other down the most.</p><p><strong>Alt text.</strong> Good alt text doesn’t show up on the screen, in a design review, or in anyone’s portfolio. Writing it well takes judgment: what does this image mean here, and what would someone miss without it? You can’t learn that from a rule. You learn it by seeing good examples next to not-so-good ones.</p><p><strong>Annotated wireframes.</strong> A wireframe shows what a screen looks like. It doesn’t show heading order, focus order, what a screen reader should announce, or how errors get communicated. Annotations hand that intent to developers. Skip them, and developers have to guess. Then testers find the guesses later.</p><figure><img alt="Form field with a red asterisk and then examples of good and bad alt text that can be used to describe the asterisk. Helpful: Red asterisk is incorporated as part of the label text so no image with alt text is required. Helpful: Alt text for red asterisk says “Required.” Unhelpful: Alt text for red asterisk says “Asterisk” or “Star.” Unhelpful: Red asterisk image has no alt text." src="https://cdn-images-1.medium.com/max/1024/1*Hwg8HORrdz4xj5JLovMw3Q.png" /><figcaption>GSA Section 508’s Example of ‘Red Asterisk Alt Text’</figcaption></figure><p><strong>Want to level up on both? A few good places to start:</strong></p><ul><li><strong>Alt text:</strong> GSA’s <a href="https://www.section508.gov/training/alt-text/what-is-alternative-text/"><strong>What is Alternative Text?</strong></a> and the W3C’s <a href="https://www.w3.org/WAI/tutorials/images/decision-tree/"><strong>alt Decision Tree</strong></a>, which walks you through what to write (or not write) for almost any image. The Nielsen Norman Group has good information for designers on <a href="https://www.nngroup.com/articles/write-alt-text/"><strong>what to write</strong></a>.</li><li><strong>Annotations:</strong> University of Michigan’s guide to <a href="https://accessibility.umich.edu/how-to/design-development/annotating"><strong>annotating designs for accessibility</strong></a><strong> </strong>and Indiana University’s <a href="https://www.kb.indiana.edu/d/bhpk"><strong>expectations for wireframe accessibility annotations</strong></a><strong>.</strong></li></ul><p>Because this work is invisible, it rarely gets shared. And because it rarely gets shared, newer designers never get to see it done well.</p><figure><img alt="What Alt-Text Should You Use? Does image convey task-related info? No: Decorative; use empty alt. Yes: Go to Q2. Is image a function (button or link)? Yes: Functional; describe its function. No: Go to Q3. Can its message be described in 150 characters? Yes: Simple informative; describe its message. No: Complex informative; edit page copy or use long description." src="https://cdn-images-1.medium.com/max/1024/1*RmOUgE5juWvyuhL3a-TZvg.png" /><figcaption>Nielsen Norman’s ‘Alt-Text Decision Tree’</figcaption></figure><h3>Compliant isn’t the same as usable</h3><p>Here’s the catch with checklists: <strong>you can check every box and still build something people hate using.</strong></p><p>A few ways that happens:</p><ul><li><strong>Alt text that says nothing.</strong> “Image” or “chart” will sail right through an automated scan. It tells a screen reader user exactly nothing.</li><li><strong>Error messages that don’t help.</strong> “Invalid input” is announced, visible, and fully accessible. It’s also useless if you don’t know what’s wrong or how to fix it.</li><li><strong>Contrast that barely squeaks by.</strong> A thin, tiny font at the minimum contrast ratio may pass the test and still be a struggle to read.</li></ul><p>Compliance is the floor, not the goal. The checklist tells you whether someone <em>can</em> use your product. Only good design decides whether they’ll <em>want</em> to. That’s exactly why designers need to be part of this conversation, not just the people checking the boxes at the end.</p><h3>AI won’t save us (yet)</h3><p><strong>I know what some of you are thinking: can’t AI just handle this now?</strong></p><p>I wish.</p><p>AI is still too new to reliably produce accessible products on its own.</p><p>Plenty of people in the accessibility community are finding issues in AI-generated designs and code, even when they’ve explicitly prompted it with the standards to follow. It might add alt text that misses the point, skip focus states, or build a component that looks right and falls apart with a screen reader.</p><p>This isn’t just my experience. In a test published recently, accessibility company AudioEye asked five AI tools to build websites that met WCAG at the AA level. <a href="https://venturebeat.com/ai/we-asked-five-ai-tools-to-build-accessible-websites-all-15-sites-failed"><strong>All 15 sites failed</strong></a> even the most basic Level A checks, averaging 55 issues per page. Academic researchers have found the same pattern: <a href="https://arxiv.org/abs/2501.03572v1"><strong>ChatGPT’s default code often fell short</strong></a>, and while it could fix simple issues when asked, the harder ones still needed human oversight.</p><p><strong>We are in the early days of AI, and it needs time to mature before we can count on it. Until then, it makes a great assistant and a risky replacement.</strong></p><p>Which brings me to something I want to say loud and clear: manual testing is not something to skip. If anything, it matters more now than ever. When more of the work is generated faster, we need people who know what to listen for, what to tab through, and what to question. Cindy and the testers like her aren’t a bottleneck. They’re the safety net.</p><p>Don’t just take my word for it. The W3C, the group that writes the accessibility standards, says it plainly: <a href="https://www.w3.org/WAI/test-evaluate/tools/selecting/"><strong>evaluation tools “can not determine accessibility, they can only assist in doing so,”</strong></a> and human judgment is required. When the UK’s Government Digital Service ran ten automated tools against a page loaded with known problems, <a href="https://accessibility.blog.gov.uk/2017/02/24/what-we-found-when-we-tested-tools-on-the-worlds-least-accessible-webpage/"><strong>even all ten together missed nearly a third of the barriers</strong></a><strong>.</strong> Their conclusion? Tools work best combined with manual testing.</p><p>And manual testing isn’t only for testers. That includes us designers. Red Hat’s design system team says designers should <a href="https://ux.redhat.com/accessibility/manual-testing/"><strong>test their own work before handoff</strong></a><strong>,</strong> checking things like color contrast and whether the reading and focus order make sense. And as Ronise Nepomuceno argues in UX Collective, <a href="https://uxdesign.cc/everyone-working-in-digital-should-learn-how-to-use-a-screen-reader-fb3dc5447ff1"><strong>everyone working in digital should learn how to use a screen reader</strong></a><strong>.</strong> Start by tabbing through your own designs with a keyboard. You’ll be surprised what you find.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/626/1*Q8t9u331M052nIV5jZZIZg.avif" /></figure><h3>Go find your accessibility experts</h3><p>Here’s the fun part: nobody assigned Cindy and me to work together. We found each other because we kept bumping into the same problems from opposite ends. She saw them in audits; I saw where they started in design.</p><p>Once we started working together, the doors swung open both ways. I invited her to my design system meetings, and she invited me to the Section 508 audits.</p><p>Sitting in those audits, I noticed who was missing: the design leads. I asked why they weren’t there, and Cindy invited them.</p><p>That small change made a big difference. Designers started hearing audit findings firsthand instead of through a ticket weeks later. Testers got a better feel for the design intent behind what they were testing. Bit by bit, the culture started shifting toward real collaboration, and accessibility started shifting left right along with it.</p><p>None of it needed a mandate. It just took two people noticing a gap and holding the door open.</p><p><strong>So here’s my challenge to you: go find your people.</strong></p><p>Almost every organization has accessibility specialists, testers, or a Section 508 program tucked away somewhere. They might sit in a different office or only show up at the end of a project. Look them up, invite them to a design review, and ask if you can sit in on an audit. I’d bet they’ve been hoping someone from design would knock.</p><figure><img alt="Example of a screen with designer annotations with helpful information for developers" src="https://cdn-images-1.medium.com/max/1024/1*EmnBFAvAJMmrswSgUrJ11w.png" /><figcaption>Annotation example from VA.gov</figcaption></figure><h3>Show your work</h3><p>If you care about accessibility, you probably know more than most designers were ever taught. And that knowledge does the most good when you share it.</p><p>The designers who need it aren’t careless. They’re ramping up, just like we all did, and they’re looking for proof of what good looks like.</p><p>So share it:</p><ul><li>The audit finding and the design decision that would have prevented it</li><li>The alt text you rewrote, and why</li><li>The annotations you hand to developers</li><li>The thing you got wrong, and what you do differently now</li></ul><p>Accessibility gets better a lot faster when we stop treating it as specialist knowledge and start treating it as something we all practice together.</p><p><strong>Post the example. Teach the session. Show your work. Help build the community.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=061e3f25fd52" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Nobody starts as an accessibility expert]]></title>
            <link>https://uxdesign.cc/nobody-starts-as-an-accessibility-expert-6a16e8a99960?source=rss-73e0ce48c6af------2</link>
            <guid isPermaLink="false">https://medium.com/p/6a16e8a99960</guid>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[visual-design]]></category>
            <category><![CDATA[accessibility]]></category>
            <dc:creator><![CDATA[Hope Turner]]></dc:creator>
            <pubDate>Tue, 22 Sep 2026 02:34:36 GMT</pubDate>
            <atom:updated>2026-09-22T04:33:51.041Z</atom:updated>
            <content:encoded><![CDATA[<h4><em>Designers, leave your intimidation at the door.</em></h4><p>Nobody becomes a designer because they’re excited about compliance. It sounds boring and it sounds like someone else’s job. Most of us are glad it is.</p><p><strong>But what if we’re wrong? What if no one else is doing it? What if no one else cares?</strong></p><figure><img alt="arrow pointing left indicating that accessibility is shifting left" src="https://cdn-images-1.medium.com/max/1024/1*qlc9hL1A0e5eGD7SO0toBA.png" /></figure><p>Picture a project as a timeline, with design on the far left and launch on the right. Accessibility problems are cheapest to fix on the left, before anything is built. <strong>Software teams call this ‘shifting left,’ which just means catching problems earlier, closer to the design, so developers and testers aren’t cleaning up later. </strong>We’re already standing on the left. If we care about our users and their experience, doesn’t that make our part of it our job?</p><p>That sounds like a big ask, so here’s the reassuring part: nobody starts as an accessibility expert. The people you picture as experts began just as unsure as you are, and they got there one small thing at a time. I still struggle with imposter syndrome on occasion.</p><p>Recently I listed everything I’d done around accessibility over the past year. I expected a short list. I was shocked to see how long it ran: writing design system component guidance, identifying rendering issues in a mobile view, posting article links and accessibility presentation invites in a shared channel, a change to who gets invited to which meeting, a note to a colleague about a gap in their training plan. None of it felt big when I did it.</p><p>These small actions add up over time. I never set out to build a body of work. I’d have been too intimidated. If someone had shown me everything I’d end up doing, I would have said no, because I didn’t trust that I had the skills or that it fit nicely in my job description.</p><p>Accessibility feels overwhelming when you look at the whole thing. It’s manageable when you only have to finish the one thing in front of you, and your skills grow as you go.</p><figure><img alt="WCAG 2 — Web Content Accessibility Guidelines screen from W3C" src="https://cdn-images-1.medium.com/max/1024/1*NDUCECDvCDKlCEKzhphsyA.png" /><figcaption><a href="https://www.w3.org/">https://www.w3.org/</a></figcaption></figure><h3>Getting started seems hard and complicated</h3><p>Let’s be honest about how accessibility usually reaches us. It arrives as a mandatory standards document full of acronyms, success criteria, and conformance levels, written in the formal register of people who write standards. It’s dense, it’s prescriptive, and just when you’ve got a handle on it, a new version appears. It’s not designer-friendly language, and I don’t blame you if you cringe when you first see it.</p><p>It’s natural to feel that you are already behind and completely overwhelmed, wondering where to even start.</p><p>There’s a reason it feels this way. In my experience, most designers were never taught accessibility. Design programs often treat it as an afterthought, and that carries into the field, where it’s rarely prioritized. It isn’t intuitive either. Unless someone deliberately puts it in front of you, there’s no reason you’d know where to start. So if you feel behind, that isn’t a personal failing. Nobody handed you the map.</p><p><strong>The good news is that you don’t need to understand all of it to do your first useful thing.</strong></p><p>And you’re not starting from zero. In my earlier article,<a href="https://uxdesign.cc/you-already-know-how-to-make-it-accessible-b29513a9b217"> <strong>You already know how to make it accessible</strong></a>, I mapped design to the accessibility standards behind them. Most of it turns out to be good design with a legal name attached. You probably have more skills and knowledge than you think, and just didn’t know what it was called.</p><h3>Baby steps, start small</h3><p>One of the most useful things you can do is take your first step.</p><p>Take the part of the requirements we designers actually control, like readable text, buttons that are easy to hit, clear labels, and helpful error messages, and start there. That’s shifting left in practice.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FvqdJF3hWxUo%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fshorts%2FvqdJF3hWxUo%3Fsi%3DzAwpZgNJsDXMGuI0&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FvqdJF3hWxUo%2Fhq2.jpg&amp;type=text%2Fhtml&amp;schema=youtube" width="640" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/27e349f0d9b24fc055f1d9549ba3c3a5/href">https://medium.com/media/27e349f0d9b24fc055f1d9549ba3c3a5/href</a></iframe><h3>Experience it for yourself</h3><p>Nothing converts a skeptic like experiencing your own design the way some users do.</p><p><strong>Put the mouse away and finish a task with the keyboard.</strong></p><p><strong>Turn on a screen reader for ten minutes.</strong></p><p>You’ll see focus jump somewhere nonsensical, a button that announces itself as just “button,” a popup you can’t escape. Worst of all, you’ll hit a dead end where your task cannot be completed.</p><p>That’s hard to argue with. It turns a requirement into “my design is broken for some people.”</p><p><strong>Ever see someone use a screen reader?</strong></p><p>I’ll never forget the first time I experienced it. It was mind-blowing how quickly someone can navigate through content and hear it read rapid-fire. In that moment, my empathy grew by leaps and bounds. I heard what a screen reader does with a page that’s technically compliant. The images all had alt text, so on paper everything passed. In reality, the descriptions repeated what the page already said in words, so the same information got read out again and again. Supremely annoying.</p><p><strong>Nothing on the checklist was failing, and the experience was still awful.</strong></p><p>That’s the part a checklist can’t teach you. Passing isn’t the same as working, and the only way to know the difference is to experience it.</p><p>One caution: ten minutes with a screen reader shows you what your design is doing. It won’t teach you what it’s like to rely on one every day. When you can, learn from the people who do.</p><p>I haven’t seen AI fix this, and I think we’ll need people testing manually for a long time to make sure the experience works for the people using it.</p><figure><img alt="image of a mobile device showing a bunch of apps" src="https://cdn-images-1.medium.com/max/1024/0*ZZsF1CHCs4vgeUAD" /><figcaption>Photo by <a href="https://unsplash.com/@williamtm?utm_source=medium&amp;utm_medium=referral">William Hook</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h3>Small things to try</h3><p>Pick any one. Any one. There’s no right way to get started, just get started!</p><p><strong>Squint at it.</strong> <br>Step back from your screen, or literally squint. What disappears? Light gray text, pale buttons, and faint borders go first. If you have to strain, someone else does too. A free contrast plugin in your design tool will give you a pass or fail if you want a second opinion, and you don’t need to understand the math.</p><p><strong>Turn your screen to grayscale.</strong> <br>Can you still tell which field has an error, which chart line is which, which tab is selected? If color was doing all the work, add a second signal, like an icon, a label, or a pattern.</p><p><strong>Dim your brightness and take it outside.</strong> <br>Open your design on your phone in the sun, or drop the brightness way down. This is how a lot of people use your product every day.</p><p><strong>Put the mouse away and tab through one flow.</strong> <br>Can you always see where you are? Does it move in an order that makes sense? Can you get out of every popup? You’re feeling your design without a mouse, so there’s nothing technical to learn.</p><p><strong>Rewrite one error message.</strong> <br>Say what went wrong and how to fix it, in words a person would use. “Invalid input” becomes “Enter a date like 04/15/2026.” Then check that the message doesn’t rely on red alone.</p><p><strong>Try it with one thumb.</strong> <br>Hold your phone in one hand and try to reach and tap everything. Tiny icons, crowded links, and buttons in the far corner become obvious fast.</p><p><strong>Zoom way in.</strong> <br>Make your text much larger, or zoom the page in. Does anything overlap, get cut off, or become unusable? This catches a surprising number of mobile problems.</p><p><strong>Turn on a screen reader for ten minutes.</strong></p><p><a href="https://support.apple.com/guide/voiceover/welcome/mac">VoiceOver</a> on Apple devices and <a href="https://support.google.com/accessibility/android/answer/6283677?hl=en">TalkBack</a> on Android are already built in. On a Mac, Command+F5 turns VoiceOver on. For TalkBack on Android phones, look under ‘Accessibility’ in Settings.</p><p>You don’t need to be good at it. You just need to hear your design once. Listen for anything it says twice or notice what it skips.</p><figure><img alt="Homepage of Knowbility showing the landing page for the Accessibility Internet Rally Program" src="https://cdn-images-1.medium.com/max/1024/1*8eFIgDCs2e4YeOGTOWPLag.png" /></figure><h3>Take it to the next level</h3><p>Once you’ve tried a few small things, here are two ways to go further:</p><p><strong>Turn understanding into advocacy.</strong> The next skill is advocacy, and it works better with evidence than with principle. Bring concrete examples of what real users hit. A passing report doesn’t tell you what it sounds like. Check your analytics, because if most of your traffic is on mobile, mobile is your main experience and not an edge case. Point out that shifting left saves time and money: problems found early are cheaper than problems found after launch. Then bring your developers in early, before anything is built. Show them what you found and what a person would experience, and work out the fix together. Designers set the direction, but it takes the whole team to deliver it. And invite other disciplines to add their own expertise and finishing touches.</p><p><strong>Learn by volunteering.</strong> You don’t have to wait for a project at work. Since accessibility is rarely taught, the best way in is to be around people who do it. Some of the fastest learning happens outside your job, where the stakes are lower and everyone around you is there to learn too. And if it doesn’t fit in your job description, it doesn’t have to.</p><ol><li><a href="https://knowbility.org/programs/air/"><strong>Accessibility Internet Rally (AIR).</strong></a> Knowbility’s AIR is an accessibility hackathon, and it needs designers. Teams are paired with a nonprofit, artist, or community group and spend about ten weeks building an accessible website for them, with a mentor’s guidance and training along the way. Registration for the next rally opens the week of September 28 and runs through December 21, and the work itself runs from January through May.</li><li><a href="https://wpaccessibility.day/"><strong>WordPress Accessibility Day.</strong></a> A free, 24-hour virtual event run by volunteers. You can just attend and soak up the sessions, or you can volunteer. Past volunteer roles, like session moderator and emcee, don’t require any coding.</li><li><a href="https://accessibility.day/"><strong>Global Accessibility Awareness Day.</strong> </a>It falls on the third Thursday in May, with community events all over the world. It’s a good nudge to spend a day trying something.</li></ol><p>I’ve volunteered at Knowbility’s AccessU conference, and I learned in two ways. I picked up a lot from the lectures and workshops. But some of the best learning happened in conversation with the people who attend. The accessibility community is open and generous with its time. They welcome newcomers, and they want more people involved, so the barrier to entry is low. Volunteering also gives you plenty to add to your list.</p><figure><img alt="Checklist of tasks to do for small steps to have big impact. Tasks are called out in the story." src="https://cdn-images-1.medium.com/max/1024/1*Ws93BX2P3FTOJTcopyhAOw.png" /></figure><h3>Keep a list</h3><p>This kind of work is nearly invisible while you’re doing it. Nudging a process, fixing an accordion component’s interaction, asking for accessibility tools, sharing an article, engaging with your accessibility or QA folks — none of it feels like an accomplishment at the moment. I only saw how much I’d done because I happened to look back to see what wins I have for this past year and saw that I had more accessibility points than I realized.</p><p>So keep a running list, and add a line whenever you change something, share something, or unblock someone’s work. (This is good practice for all your work — tracking your accomplishments).</p><h3>Start with one small thing</h3><p>Nobody starts as an accessibility expert. You become one by finishing small things, one after another, until one day you’re the person people ask. You never decided to be. It just happened. Our part of this is our job, and it turns out to be one you can learn a small thing at a time.</p><p>Don’t try to take on the whole thing at once. Pick one thing from the lists above and do it this week. Finish it, then pick the next. The more you do, the easier it gets.</p><p><strong>So what are you waiting for? This is your personal invitation! Come join us in making digital products work better for everyone.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6a16e8a99960" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/nobody-starts-as-an-accessibility-expert-6a16e8a99960">Nobody starts as an accessibility expert</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[It Feels Like the Wild West, But It Isn’t. Not Really.]]></title>
            <link>https://www.designsystemscollective.com/it-feels-like-the-wild-west-but-it-isnt-not-really-098de64b35e8?source=rss-73e0ce48c6af------2</link>
            <guid isPermaLink="false">https://medium.com/p/098de64b35e8</guid>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[accessibility]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[design-systems]]></category>
            <dc:creator><![CDATA[Hope Turner]]></dc:creator>
            <pubDate>Wed, 16 Sep 2026 02:55:03 GMT</pubDate>
            <atom:updated>2026-09-21T17:49:48.815Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jnR3p4LlDs3kbsRp6GEQig.png" /></figure><p>I have a mental list of the AI-generated design work that crosses my feed. Not the polished stuff people share as wins. The other stuff: work someone was proud enough of to post, that falls apart the moment you actually look at it.</p><p>The tells show up in the same handful of places, over and over:</p><ul><li><strong>The grid is broken.</strong> <br>Some elements float with no relationship to each other.</li><li><strong>Typography goes unchecked.</strong> <br>Too many typefaces, illegible sizes, no hierarchy telling your eye where to go first.</li><li><strong>Contrast hurts to look at.</strong> <br>Text that swims into its background or sears your eyeballs.</li><li><strong>Interactions lose their logic.</strong> <br>No clear button where one’s needed, or a page cluttered with buttons competing for the same click.</li><li><strong>The writing repeats itself.</strong> <br>A headline that promises one idea and body copy that circles back through it three more times. Redundant text taking up prime real estate for no good reason.</li><li><strong>It has a look.</strong> <br>A generic sameness: the same gradients, the same overwrought illustration style, the same stock-feeling compositions. Trained or not, most people can spot AI-generated art on sight now. It’s becoming its own visual cliché.</li></ul><p><strong>Each of these points is second nature to anyone with UX training, and invisible to anyone without it.</strong></p><p>You don’t need design training to feel something’s wrong with a page like this. What you do need training for is to name what’s wrong, and to know it needs fixing before it ships.</p><p><strong>That gap is the whole story.</strong></p><figure><img alt="Color contrast tool illustrating failing text color combination" src="https://cdn-images-1.medium.com/max/1024/1*lIsNffwNxCTopaPB6f9HyQ.png" /></figure><h3>What about accessibility?</h3><p>A broken grid or illegible type isn’t an accessibility failure by itself. It’s a craft failure. But bad color contrast is both. WCAG has actual, measurable contrast ratios, so text that hurts to read isn’t a stylistic choice I happen to dislike. It’s a documented accessibility violation, already shipped, produced by someone who had no idea they’d failed a standard that’s existed for two decades.</p><p>That’s what makes this different from a hypothetical “AI might hurt accessibility someday” argument. It’s already happening, and it’s checkable with a color contrast tool in seconds.</p><p>If a fundamental this visible is failing at this rate, what confidence should we have in the fundamentals that nobody can see just by looking? Keyboard navigation, screen reader compatibility, focus order, alt text that actually describes something, the kind of thing you catch by manually testing with ANDI or MacOS VoiceOver, not by eyeballing a screen.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_Pv8Q0MK67yTLgw6HQRFrg.png" /></figure><h3>People can’t prompt for what they don’t know exists</h3><p>I don’t think this is a failure of effort or care. It’s a failure of visibility. Someone without design training asks for an AI tool to make something look “clean” or “professional.” They don’t know how to say “limit this to two font families” or “verify a 4.5:1 contrast ratio.” People think that “make it look good” feels like a complete instruction. It isn’t. There’s an invisible checklist behind it they don’t know exists.</p><p>Trained designers should find this a little humbling too: we weren’t reliably catching all of this before AI, either. AI didn’t introduce a new failure mode. It removed the one imperfect, inconsistent human filter that used to catch some of it, some of the time, and handed the same blind spot to people with no filter at all.</p><p><strong>AI didn’t lower the bar. It removed the person who used to check where the bar was.</strong></p><h3>What a better prompt actually says…</h3><p>Some of this is fixable at the prompt level, if you know what rules to use:</p><ul><li><strong>Grid</strong><br><em>“Lay this out on a 12-column grid with consistent 24px gutters, and align every element to it.”</em></li><li><strong>Whitespace</strong><br><em>“Use an 8px spacing scale. Leave at least 32px between major sections.”</em></li><li><strong>Line length</strong><br><em>“Constrain body copy to 60–75 characters per line for readability.”</em></li><li><strong>Type scale</strong> <br><em>“Use a modular type scale so titles, headers, and body text are clearly distinct. Limit to two font families, three to four weights.”</em></li><li><strong>Contrast</strong> <br><em>“Maintain at least a 4.5:1 contrast ratio for normal text, per WCAG AA.”</em></li><li><strong>Interaction</strong> <br><em>“Include exactly one clear primary action per screen.”</em></li><li><strong>Plain language</strong> <br><em>“Write copy at a 6th–8th grade reading level. Use short sentences, plain words, and avoid jargon.”</em></li><li><strong>Content structure</strong> <br><em>“Lead with the main point in the first sentence. One idea per paragraph, no restating the headline in the body copy.”</em></li></ul><p><strong>None of this requires a design degree to type. It requires knowing these are things worth specifying, which is how we start to bridge the gap and raise the bar. </strong><a href="https://www.nngroup.com/articles/ai-prototyping/"><strong>Better prompts net better results.</strong></a></p><h3>Jack of all trades, master of none</h3><p>The visual failures get noticed first. But read the words, and there’s often a second problem underneath: redundant phrasing, headlines that circle back through the same point, walls of text with no scanning path, and confusing jargon. <a href="https://www.nngroup.com/articles/content-strategy/">Content strategy</a> is its own discipline, with its own fundamentals, and someone who lets AI take the wheel doesn’t know that discipline exists any more than they knew about the necessity of visual design in <a href="https://www.nngroup.com/articles/using-grids-in-interface-designs/">using a grid</a> and <a href="https://design.dev/guides/typography-web-design/">detailing typography.</a></p><p>AI collapsed visual design, content strategy, and information architecture into a single prompt box, and handed the reins of all three to one person who never trained in any of them. A trained team used to have separate roles, each catching what the others might miss. <a href="https://www.nngroup.com/articles/content-design-systems/">Content needs the same kind of standards and governance</a> that visual design already has, not just good instincts.</p><figure><img alt="cartoon image of a sheriff’s badge" src="https://cdn-images-1.medium.com/max/512/1*apknl3O71jGFALZEDZTraA.png" /></figure><h3>The missing sheriff</h3><p>This is where “wild west” earns its name. Not because AI is inherently lawless, but because it’s operating in the one part of the process that used to have law: the design system.</p><p>A <a href="https://designsystem.university/courses/design-systems-101">design system</a> isn’t just a component library and a color palette. It’s the codified version of “here’s what good already looks like,” applied automatically, so accessible defaults come built in instead of reconstructed from memory each time. That’s exactly the layer missing when someone opens a blank AI prompt. The AI has nothing governed to default to, so it defaults to whatever the training data averages out to.</p><p>A subtler version shows up even where some structure exists. Teams with a component library often believe that’s their design system, and that having it makes AI output automatically compliant.</p><p>A <a href="https://www.figma.com/community/ui-kits?resource_type=files&amp;editor_type=figma">component library</a> is parts. A <a href="https://docsio.co/blog/design-system-documentation">design system is the governance</a> around the parts: when and how components are used, the accessibility built into every variant, the documentation for what breaks if you deviate. A library without that governance is a box of ingredients with no recipe. It can still fail contrast and skip a focus state using entirely the right pieces.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RvIB4S2AkPqN3PNvXxBvKg.png" /><figcaption>Laws of UX Examples</figcaption></figure><h3>There actually are laws</h3><p>If “wild west” implies lawlessness, it’s worth naming that a body of law already exists here: the Laws of UX, well-documented heuristics for how people actually use interfaces.</p><ul><li><a href="https://lawsofux.com/fittss-law/"><strong>Fitts’s Law</strong> </a><br>The time to reach a target depends on its size and distance. Inconsistent, tiny buttons make an interface measurably harder to use.</li><li><a href="https://lawsofux.com/hicks-law/"><strong>Hick’s Law</strong> </a><br>More choices at once take longer to decide between. A screen crowded with competing buttons slows the user down.</li><li><a href="https://lawsofux.com/law-of-proximity/"><strong>Law of Proximity</strong> </a><br>Elements placed close together read as related. A broken grid violates this by accident, grouping things that were never meant to be.</li></ul><p>None of it is new or hard to find. Feeding a handful of these principles into a prompt, explicitly, tends to produce output that behaves the way a trained designer already knows it should.</p><h3>Two kinds of lawlessness</h3><p>Not everyone skipping the standards is skipping them for the same reason.</p><p><strong>Pioneers:</strong> <br>Some teams, often startups with no design function, have no governance to bypass, because none was ever written down. They’re closer to early pioneers than outlaws, striking out because no trail existed yet.</p><p><strong>Outlaws:</strong> <br>More commonly we see people inside large organizations who know a design team and standards exist, and cut across the fence line anyway. I’ve heard some version of the same tired joke at more than one company, that once design gets involved everything slows down, and deadlines don’t care about a review cycle. And there is some truth that design can make the process take longer because designers want to make sure that the problem is defined correctly and the most successful solution has been identified. They will do user research and iterate on findings.</p><p><a href="https://www.smashingmagazine.com/2024/08/how-defend-your-design-process/">The friction between product owners and designers</a> used to have a ceiling. A stakeholder could resent the “slow” design process, but they still couldn’t build the thing themselves. AI has made it easier to bypass designers and their design governance. You can lead a horse to water, hand someone a documented design system, and still not make them drink it — if going around is faster and nobody’s stopping them. This is why the guardrails matter more now, not less. They exist to catch what a person moving fast isn’t positioned to catch themselves.</p><figure><img alt="Antique map illustrating a early pioneer town that looks thoughtfully constructed" src="https://cdn-images-1.medium.com/max/768/1*mXwoaUfwp_Ck1lwPIW_TSw.jpeg" /></figure><h3>Getting back on the map</h3><p>A few starting points, depending on where a team actually is:</p><ul><li><strong>No design system at all</strong> <br>Document minimum viable standards first, a type scale, a contrast floor, a grid. A one-page reference beats no reference.</li><li><strong>A component library with no governance</strong> <br>Write down why components look the way they do and what breaks if someone deviates. Make the invisible reasoning visible.</li><li><strong>Governance that gets routed around</strong> <br>Look honestly at where review is genuinely slow and fix the process, not just the messaging. A gate people can’t get through fast enough is one they’ll learn to walk around.</li><li><strong>AI work already shipping without review</strong> <br>Add one checkpoint, not ten. A single accessibility and standards review is a far more realistic ask than inserting design into every step.</li></ul><p><strong>The goal isn’t to slow AI down. It’s to make sure it’s generating inside territory that’s actually been surveyed.</strong></p><h3>The fix already exists</h3><p>I don’t think the answer is waiting for someone to invent AI-specific rules. It only feels lawless. Look closer, and there’s already a body of law here:</p><ul><li><a href="https://www.w3.org/WAI/">WCAG/508 standards</a></li><li><a href="https://designx.co/design-system-documentation/">Design system governance + documentation</a></li><li><a href="https://lawsofux.com/">Laws of UX</a> and other related publications</li><li><a href="https://www.nngroup.com/articles/principles-visual-design/">Design fundamentals </a>(grids, type, scale, hierarchy, balance, and contrast)</li><li><a href="https://www.nngroup.com/articles/ten-usability-heuristics/">Heuristics and gestalt principles</a></li></ul><figure><img alt="graphic with words “rules, policies, standards, compliance, and regulations”" src="https://cdn-images-1.medium.com/max/626/1*fEyMkULik-PFbPpOT3OHUg.jpeg" /></figure><h3><strong>We’re not starting from nothing.</strong></h3><p>AI-specific guidance is still being written, and we’re all still learning. But not having every answer yet isn’t the same as not knowing what good design looks like.</p><p><strong>What’s missing isn’t a shared definition of quality. It’s the discipline to apply the one we already have to the AI work that nobody planned to review. The problem is a production method operating outside the process that is used to enforce quality and accessibility as a baseline.</strong></p><p>You need to ask whether the work in front of you actually passed through the standards you already have, or skipped the gate because nobody put one there yet.</p><p><strong>It only feels like the wild west. Arm yourself with a design system, real guidance, and governance, and the territory turns out to be far more civilized than it looks. That’s the work of a designer now, and it’s more essential than it’s ever been: not fighting the frontier, but civilizing it.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=098de64b35e8" width="1" height="1" alt=""><hr><p><a href="https://www.designsystemscollective.com/it-feels-like-the-wild-west-but-it-isnt-not-really-098de64b35e8">It Feels Like the Wild West, But It Isn’t. Not Really.</a> was originally published in <a href="https://www.designsystemscollective.com/">Design Systems Collective</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[AI Made Design Easier. It Didn’t Make It Good.]]></title>
            <link>https://medium.com/design-bootcamp/ai-made-design-easier-it-didnt-make-it-good-cb0eb94ec623?source=rss-73e0ce48c6af------2</link>
            <guid isPermaLink="false">https://medium.com/p/cb0eb94ec623</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[accessibility]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ai]]></category>
            <dc:creator><![CDATA[Hope Turner]]></dc:creator>
            <pubDate>Thu, 20 Aug 2026 21:35:57 GMT</pubDate>
            <atom:updated>2026-09-21T22:45:14.739Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*eknXxH_iMdQvtzNY" /><figcaption>Photo by <a href="https://unsplash.com/@markuswinkler?utm_source=medium&amp;utm_medium=referral">Markus Winkler</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h4>Nice Scissors. Have You Ever Actually Cut Hair?</h4><p>Buying a fancy pair of scissors doesn’t make you a hairstylist.</p><p>It doesn’t mean you shouldn’t get a great haircut, though. It just means you find someone trained to use them well.</p><p>That’s the tension I feel as I watch designers, and non-designers, rush into AI tools with a “build first” mindset. Because y’all, we’ve actually been here before. More than once.</p><h3>The Desktop Publishing Wave</h3><p>Back in the 90s, desktop publishing put typesetting into anyone’s hands. Before that, laying out a document (choosing type, setting margins, controlling hierarchy) was a skilled trade. Suddenly anyone with a Mac and a copy of PageMaker could do it themselves.</p><p>The results were, famously, not great.</p><p><strong>Comic Sans everywhere.</strong></p><p><strong>Papyrus showing up on things that had no business being anywhere near ancient Egypt.</strong></p><p><strong>Six fonts on one flyer.</strong></p><p><strong>Text stretched and squeezed to fit a box instead of the box being designed to fit the text.</strong></p><figure><img alt="wall with flyers posted illustrating a variety of designs from a variety of sources" src="https://cdn-images-1.medium.com/max/1024/0*-LzemFElIDjxpYfL" /><figcaption>Photo by <a href="https://unsplash.com/@heyitst0m?utm_source=medium&amp;utm_medium=referral">Tom Dillon</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>I want to be clear: Comic Sans and Papyrus are not inherently evil. They have their place. A kid’s birthday party flyer, sure. A dentist’s office logo trying to look “friendly,” I guess. But an untrained eye doesn’t pick them for the right reasons. They pick them because they’re fun, or different, or the first thing that jumped out. And then they use them for everything, forever, with total confidence. That’s the tell.</p><p>The tools had democratized <em>production</em>. They hadn’t democratized <em>judgment</em>.</p><p>It took years, and a lot of typography education finding its way into mainstream design culture, before the average document stopped looking like a ransom note.</p><h3>The WYSIWYG Wave</h3><p>Fast forward to the early 2000s, and the same pattern showed up again with website builders. Suddenly anyone could drag, drop, and publish a website without knowing HTML. The barrier to <em>building</em> something dropped to almost nothing.</p><p>And once again, the results were often unusable. Confusing navigation. Inaccessible color contrast. Layouts that worked on one screen size and fell apart on every other. The tools made it possible to build. They didn’t make anyone able to judge whether what they’d built actually worked for the people using it.</p><p>It took the rise of UX as a discipline, and later design systems as a governance tool, to close that gap. Not everyone became a professional designer. But the field built guardrails, standards, and shared components that helped non-specialists produce better outcomes than raw talent alone ever could.</p><figure><img alt="image of an AI prompt" src="https://cdn-images-1.medium.com/max/1024/1*urgw6Qic1PPP3J22A-C5kA.png" /></figure><h3>Now It’s AI’s Turn</h3><p>I’m seeing a lot of designers, and plenty of non-designers, jump into AI tools with a “build first” mindset. And honestly, I get the excitement. These tools can produce something polished-looking in minutes: clean typography, a coherent color palette, a layout that looks finished.</p><p>But polish and quality are not the same thing.</p><p>Someone without a trained eye sees something that looks <em>better than what they could make themselves</em>, and it’s easy to mistake that for <em>good</em>. That disconnect is the real risk of this moment. Not that AI produces bad output, but that it produces confident looking output that nobody involved is actually equipped to evaluate.</p><figure><img alt="A door that has a handle you would use to pull it open juxtaposed with a sign that says ‘push’ on it" src="https://cdn-images-1.medium.com/max/1024/0*Q97l4m7eDqs50L2t" /><figcaption>Photo by <a href="https://unsplash.com/@huntleytography?utm_source=medium&amp;utm_medium=referral">Devon Janse van Rensburg</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>I think of it like a door with a handle that says “push,” when the only way through is to pull. The design <em>looks</em> like it affords one thing. It actually requires another. <strong>A trained eye catches that gap immediately. </strong>An untrained one just feels confused, or worse, doesn’t notice at all. And neither does anyone downstream who’s relying on the product working the way it appears to.</p><p><strong>And it’s not just the visual layer. The interaction patterns are off too.</strong></p><p><strong>A dropdown that should be a radio button.</strong></p><p><strong>A modal that opens when a tooltip would do.</strong></p><p><strong>A multi-step flow where one screen would work fine.</strong></p><p>AI is generating interfaces that don’t match the mental models people have built up over twenty years of using the web, because those mental models aren’t really “logic,” they’re convention, and convention is exactly the kind of thing that’s hard to reverse-engineer from a prompt.</p><figure><img alt="A graphic that has the text ‘mind the gap’" src="https://cdn-images-1.medium.com/max/899/1*s8Yh7aq1mTj9mfSDSrFvDA.png" /></figure><p>Here’s the part that gets me the most: someone without design training can usually tell that something feels a little off. They just can’t say why. They’ll click around, get a nagging sense that it’s clunky, and shrug it off as a personal problem, like they’re just not tech savvy enough, instead of what it actually is: the product asking them to do the work the design should have done for them. <strong>Mind the gap — that space between sensing something’s wrong and being able to name it is exactly where a trained eye earns its keep.</strong></p><h3>Lipstick on a Pig: The Latest Shade, Now Available</h3><p>Designers who’ve been staring at this stuff for a while have started calling it “lipstick on a pig.” Harsh, but honestly, kind of fair. And the other word that keeps showing up is “slop,” which, funny enough, is also what you feed a pig. Somebody out there has a sense of humor about all this, even if it’s a dark one.</p><p>That phrase captures something important: this isn’t one problem, it’s three stacked on top of each other:</p><p>1 - The <strong>visual design </strong>is often lacking, inconsistent, or just plain wrong.</p><p>2 - The <strong>UX and interactions</strong> can be misleading or actively broken.</p><p>3 - And the <strong>accessibility </strong>issues are real, whether or not the thing technically passes an automated scanner. Something can sail through every automated accessibility test you throw at it and still be genuinely unusable for a real person trying to get something done.</p><p>That’s the part that stings. Someone pours real time and energy into shipping this AI slop, honestly believing it’s the greatest thing since sliced bread, only to get rudely awakened when actual users show up and it turns out to be a hot mess. Nobody wins there. Not the person who built it, not the people trying to use it, and definitely not the mission the product was supposed to serve in the first place.</p><h3>What Actually Changed, and What Didn’t</h3><p><strong>Here’s the pattern across all three waves: the barrier to <em>production</em> keeps dropping. The barrier to <em>judgment</em> never does.</strong></p><p>Desktop publishing didn’t make everyone a typographer.</p><p>WYSIWYG tools didn’t make everyone a UX designer.</p><p>AI isn’t going to make everyone a product designer either, no matter how good the output looks on the first pass.</p><p>What each wave actually needed wasn’t less access to the tools. It was more access to the judgment that makes the tools worth using well: education, standards, and often, someone trained to look at the result and say, clearly and specifically, <em>here’s what’s actually wrong, and here’s why it matters.</em></p><h3>The Real Question</h3><p>If you’re using AI to build something right now (a website, an app, a product), the question worth asking isn’t “does this look good?”</p><p>It’s <strong>“would this hold up to someone who’s spent years learning what ‘good’ actually requires, for the person using it, not just for the person who made it?”</strong></p><p>That gap between looking finished and actually working is where the next generation of design problems is quietly getting built. The tools got faster. <strong>The judgment gap didn’t close. It just got easier to miss.</strong></p><figure><img alt="Stack of design books showing a range of knowledge that a trained designer might read" src="https://cdn-images-1.medium.com/max/1024/0*y_appFeM87LizUVj" /><figcaption>Photo by <a href="https://unsplash.com/@karlsolano?utm_source=medium&amp;utm_medium=referral">Karl Solano</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h3>Trained Designers Are More Valuable, Not Less</h3><p>Here’s the part that should give trained designers some hope in the middle of all this AI anxiety: every wave of “anyone can build it now” has ended the same way. The tools got adopted, the slop piled up, and the people who actually knew what they were doing became more in demand, not less. <strong>Judgment doesn’t get automated away. It gets more valuable the more noise there is to sort through.</strong></p><p>And a lot of the sorting looks the same every time, too. Someone ships their AI-built thing, feels great about it for a while, and then real users show up and the cracks start to show. Eventually, sheepishly, they seek out a skilled designer. Not to start over. Just to fix it. To take the AI slop and make it actually work.</p><p>There’s no shame in that, honestly. Y’all know how this story goes. Maybe it happened to you. More likely you know somebody, a sibling, a college roommate, that one friend from your book club, who watched a few YouTube tutorials, bought some real clippers, and decided they could handle cutting their own hair. Or worse, offered to “help out” a friend. It goes fine right up until it doesn’t, and suddenly there’s a chunk missing that was never part of the plan. Everybody’s got a story like this, or knows somebody who does. That’s when you call an actual stylist, a little sheepishly, and ask them to fix it. Not because the clippers were bad. Because owning them was never the same thing as knowing how to use them. That’s still a real skill, still worth paying for, and if anything, this whole AI moment is making that clearer, not less clear.</p><figure><img alt="Image of a person that has a blindfold over their eyes so they can’t see what they’re doing. They have a pair of hair clippers where they have shaved their head." src="https://cdn-images-1.medium.com/max/1024/0*hQhQJNFi49VPhOzP" /><figcaption>Photo by <a href="https://unsplash.com/@attiepatatie?utm_source=medium&amp;utm_medium=referral">Altin Ferreira</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>And look, not every haircut needs to be a luxury salon experience. Sometimes a SuperCuts is exactly right. Quick, cheap, good enough, done.</p><p>There’s an old saying about projects: fast, cheap, good, pick two. Haircuts follow the same rule, and so does AI-built design. There’s nothing wrong with picking fast and cheap, as long as it matches what you actually need.</p><p>The problem isn’t reaching for that option. It’s not knowing the difference, or worse, thinking you’re getting salon results when what you actually got needs a professional to salvage it. <strong>Know which one you’re choosing, and choose it on purpose.</strong></p><h3>In closing…</h3><p>I know where a lot of designers are right now, watching AI spit out layouts in seconds, quietly wondering: <em>am I still needed?</em></p><p>Yes, absolutely.</p><h3><strong>You’re needed to know the difference: the gap between “this technically works” and “this actually serves the person using it.”</strong></h3><p><strong>Convincing a stakeholder of that gap is the harder part.</strong></p><p>A few places to start: stop arguing taste, ask for evidence. Try “have we watched anyone try to use it?” Show, don’t tell. Put it in front of five real users and let the gap reveal itself.</p><p>Reframe speed as a phase, not a finish line. Fast gets you a first draft; the distance from there to shippable is exactly the terrain designers know how to navigate. <strong>That’s the job now. Not producing faster than the machine. Minding the gap it can’t see.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cb0eb94ec623" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/ai-made-design-easier-it-didnt-make-it-good-cb0eb94ec623">AI Made Design Easier. It Didn’t Make It Good.</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[You already know how to make it accessible]]></title>
            <link>https://uxdesign.cc/you-already-know-how-to-make-it-accessible-b29513a9b217?source=rss-73e0ce48c6af------2</link>
            <guid isPermaLink="false">https://medium.com/p/b29513a9b217</guid>
            <category><![CDATA[visual-design]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[content-design]]></category>
            <category><![CDATA[web-accessibility]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Hope Turner]]></dc:creator>
            <pubDate>Sun, 16 Aug 2026 10:08:36 GMT</pubDate>
            <atom:updated>2026-08-16T10:08:36.968Z</atom:updated>
            <content:encoded><![CDATA[<h4><em>A translation guide for designers who think accessibility is a separate skill set</em></h4><p>Every year, <a href="https://webaim.org/">WebAIM</a> crawls the home pages of the top one million websites and runs them through an automated accessibility scanner. The <a href="https://webaim.org/projects/million/">2026 results</a>, published this spring, found errors on <strong>95.9% of home pages</strong>, averaging <strong>56 detectable accessibility barriers per page</strong>. That number actually went up from the year before, <strong><em>reversing six straight years of slow improvement.</em></strong></p><h4>Here’s the part that should stop every designer in their tracks: <br><strong>the six most common failure types haven’t changed in seven years of this report.</strong></h4><figure><img alt="2026 Common Failure Types: • Low contrast text: 83.9% of pages • Missing alt text on images: 53.1% of pages • Unlabeled form inputs: 51% of pages • Empty links: 46.3% of pages • Empty buttons: 30.6% of pages • Missing document language: 13.5% of pages" src="https://cdn-images-1.medium.com/max/1024/1*CO1y6Yw8YXLpYBVkhLV_nw.png" /></figure><p><strong><em>Now read that list again as a designer, not as a compliance officer.</em></strong></p><p>Contrast. Labeling. Meaningful content in interactive elements. A document that actually declares what it is. <strong>None of this is accessibility exotica.</strong> It’s first-semester design fundamentals, the stuff any trained designer was taught to care about long before anyone ever said the words “<a href="https://www.wcag.com/resource/what-is-wcag/">WCAG</a>” or “<a href="https://www.section508.gov/">Section 508</a>” out loud.</p><p>That’s really the whole argument of this piece: <strong>accessibility standards aren’t a new discipline bolted onto design. They’re a legal and technical translation of design principles good designers already practice.</strong> The gap isn’t knowledge. It’s vocabulary. Once a designer sees the 1:1 mapping, the standards stop feeling like an outside checklist and start feeling like a language for something they’ve been doing all along.</p><p><strong>Here’s that mapping.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EBsLePOilpPLO_5_3TRkmw.png" /></figure><ol><li><strong>VISUAL HIERARCHY<br>Design Principle:</strong> guide the eye through content in a deliberate order.<br><strong>WCAG: </strong><a href="https://www.w3.org/WAI/WCAG21/Understanding/info-and-relationships">1.3.1 Info and Relationships</a>; <a href="https://www.w3.org/WAI/WCAG21/Understanding/headings-and-labels.html">2.4.6 Headings and Labels. </a><br><strong>Section 508: </strong><a href="https://www.section508.gov/manage/section-508-assessment/2023/background/">Federal Law and Policy</a>.<br><strong>Missing in practice: </strong>41.8% of pages skip heading levels; 18.1% have more than one &lt;h1&gt;. The hierarchy exists on screen but not in the underlying structure.</li><li><strong>CONTRAST</strong><br><strong>Design Principle:</strong> text needs to be legible against its background.<br><strong>WCAG: </strong><a href="https://www.w3.org/WAI/WCAG21/Understanding/contrast-minimum.html">1.4.3 Contrast </a>(Minimum).<br><strong>Section 508: </strong>Same as WCAG.<br><strong>Missing in practice:</strong> the single most common failure on the web, 83.9% of pages, about 34 instances per page on average.</li><li><strong>MEANINGFUL LABELS</strong><br><strong>Design Principle: </strong>a field should say what it wants.<br><strong>WCAG:</strong> <a href="https://www.w3.org/WAI/WCAG21/Understanding/info-and-relationships">1.3.1 Info and Relationships</a>; <a href="https://www.w3.org/WAI/WCAG21/Understanding/labels-or-instructions.html">3.3.2 Labels or Instructions. </a><br><strong>Section 508: </strong>Same as WCAG.<br><strong>Missing in practice: </strong>one in three form inputs on the average home page (33.1%) has no programmatic label.</li><li><strong>DESCRIPTIVE, PURPOSEFUL IMAGERY</strong><br><strong>Design Principle:</strong> an image should communicate something, not just decorate.<br><strong>WCAG: </strong><a href="https://www.w3.org/WAI/WCAG21/Understanding/non-text-content.html">1.1.1 Non-text Content.</a><br><strong>Section 508: </strong>Same as WCAG.<br><strong>Missing in practice: </strong>16.2% of images are missing alt text entirely, and another 10.8% have alt text so generic (“image,” “graphic,” a filename) that it says nothing at all.</li><li><strong>CLEAR AFFORDANCES</strong><br><strong>Design Principle: </strong>a button should look and behave like a button, a link like a link.<br><strong>WCAG:</strong> <a href="https://www.w3.org/WAI/WCAG21/Understanding/link-purpose-in-context.html">2.4.4 Link Purpose (In Context)</a>; <a href="https://www.w3.org/WAI/WCAG21/Understanding/name-role-value.html">4.1.2 Name, Role, Value </a><br><strong>Section 508: </strong>Same as WCAG.<br><strong>Missing in practice: </strong>46.3% of pages have empty links and 30.6% have empty buttons, controls with no discernible purpose to anyone, sighted or not.</li><li><strong>PREDICTABLE, CONSISTENT NAVIGATION</strong><br><strong>Design Principle: </strong>the same pattern should work the same way everywhere. <br><strong>WCAG: </strong><a href="https://www.w3.org/WAI/WCAG21/Understanding/consistent-navigation.html">3.2.3 Consistent Navigation</a>; <a href="https://www.w3.org/WAI/WCAG21/Understanding/consistent-identification.html">3.2.4 Consistent Identification </a><br><strong>Section 508: </strong>Same as WCAG.<br><strong>Missing in practice: </strong>design-system inconsistency is exactly what this criterion penalizes, components that drift, visually or functionally, from page to page.</li><li><strong>CONTENT THAT ORIENTS </strong><br><strong>Design Principle: </strong>establish context before asking for action.<br><strong>WCAG: </strong><a href="https://www.w3.org/WAI/WCAG21/Understanding/language-of-page.html">3.1.1 Language of Page</a>.<br><strong>Section 508: </strong>Same as WCAG.<br><strong>Missing in practice: </strong>13.5% of pages don’t declare a document language, which breaks screen reader pronunciation and translation tools entirely.</li><li><strong>RESTRAINT WITH NOVEL INTERACTION PATTERNS</strong><br><strong>Design Principle:</strong> don’t invent a new pattern when a standard one works.<br><strong>WCAG:</strong> 4<a href="https://www.w3.org/WAI/WCAG21/Understanding/name-role-value.html">.1.2 Name, Role, Value </a>(custom components); <a href="https://www.w3.org/WAI/ARIA/apg/">ARIA Authoring Practices</a>.<br><strong>Section 508: </strong>Same as WCAG.<br><strong>Missing in practice: </strong>pages using ARIA averaged 59.1 errors vs. 42 on pages without it, more custom interaction complexity means more chances to get the underlying semantics wrong. 22% of ARIA menus lacked the markup needed to actually function as menus.</li><li><strong>ERROR PREVENTION AND GRACEFUL RECOVERY</strong><br><strong>Design Principle: </strong>help people avoid mistakes and recover from them without shame. <br><strong>WCAG:</strong> <a href="https://www.w3.org/WAI/WCAG21/Understanding/error-identification.html">3.3.1 Error Identification</a>; <a href="https://www.w3.org/WAI/WCAG21/Understanding/error-suggestion.html">3.3.3 Error Suggestion</a>.<br><strong>Section 508: </strong>Same as WCAG.<br><strong>Missing in practice: </strong>this one maps directly to standard usability heuristics, basically Nielsen’s “help users recognize, diagnose, and recover from errors,” just given legal teeth.</li><li><strong>SKIMMABLE, WELL STRUCTURED CONTENT</strong><br><strong>Design Principle: </strong>headings and landmarks let people jump to what matters.<br><strong>WCAG: </strong><a href="https://www.w3.org/WAI/WCAG21/Understanding/info-and-relationships">1.3.1 Info and Relationships</a>; <a href="https://www.w3.org/WAI/WCAG21/Understanding/bypass-blocks">2.4.1 Bypass Blocks</a>.<br>Section 508: Same as WCAG.<br><strong>Missing in practice: </strong>only 46.1% of pages have a &lt;main&gt; landmark, and only 17.1% offer a skip link. One in ten of those skip links is broken.</li><li><strong>DESCRIPTIVE MICROCOPY</strong><br><strong>Design Principle: </strong>link and button text should say where it goes, not just “click here.” <br><strong>WCAG: </strong><a href="https://www.w3.org/WAI/WCAG21/Understanding/link-purpose-in-context.html">2.4.4 Link Purpose (In Context)</a>.<br><strong>Section 508:</strong> Same as WCAG.<br><strong>Missing in practice:</strong> 15.2% of pages have ambiguous link text like “click here” or “read more,” averaging 5.3 instances per page.</li><li><strong>PLAIN, CLEAR LANGUAGE</strong><br><strong>Design Principle: </strong>write for the reader in front of you, not for yourself.<br><strong>WCAG:</strong> <a href="https://www.w3.org/WAI/WCAG21/Understanding/unusual-words">3.1.3 Unusual Words</a>; <a href="https://www.w3.org/WAI/WCAG21/Understanding/reading-level.html">3.1.5 Reading Level</a>; <a href="https://www.w3.org/WAI/WCAG21/Understanding/help">3.3.5 Help</a>.<br><strong>Section 508:</strong> Same, reinforced by the federal <a href="https://digital.gov/resources/plain-writing-act">Plain Writing Act </a>for government content.<br><strong>Missing in practice: </strong>WCAG’s automated tools can’t score reading level directly, which is exactly why this one gets skipped, no error count nags anyone about it. It’s invisible in a scan and enormous in real-world impact.</li></ol><p><strong>A quick note on “</strong><a href="https://www.section508.gov/"><strong>Section 508</strong></a><strong>”:</strong> since the 2018 Refresh, the federal standard no longer keeps its own separate technical criteria for web content. It points to the same rulebook everyone else uses, incorporating WCAG 2.0 Level A/AA by reference, and most agencies now hold themselves to the newer <a href="https://accessibility.build/guides/wcag-2-1-vs-2-2">2.1/2.2 version</a> as the practical bar.</p><p><strong>“Section 508 compliant” and “WCAG 2 A/AA conformant” are, for nearly every practical purpose, the same target. That’s worth saying plainly, because a lot of designers think of these as two separate rulebooks to learn, when for digital products they’ve basically merged into one.</strong></p><p><em>Data source: WebAIM, “The WebAIM Million” (2026), webaim.org/projects/million</em></p><h3>Why this framing matters</h3><p>The WebAIM data makes an argument you can’t really make with a checklist alone: <strong>these failures cluster around the exact areas where “just design it well” already gets you the answer.</strong> Contrast, labeling, hierarchy, affordance, consistency: none of this requires a designer to learn a new skill. It just requires the designer’s existing judgment to actually survive the trip from comp to production.</p><p>You don’t need to become an accessibility specialist to close most of this gap. You need to:</p><ul><li>Insist that your visual hierarchy survives into real <a href="https://www.w3.org/WAI/tutorials/page-structure/headings/">heading</a> markup, not just font-size styling.</li><li>Treat <a href="https://webaim.org/resources/contrastchecker/">contrast ratios</a> as a design constraint, with the same seriousness you’d give brand color.</li><li>Write real link and button copy instead of <a href="https://www.w3.org/QA/Tips/noClickHere">“click here”</a> and empty icon buttons.</li><li><a href="https://www.section508.gov/create/alternative-text/">Write alt text </a>that actually describes what the image communicates, not just what it depicts (a purely decorative graphic gets alt=&quot;&quot;, a chart gets a meaningful description of what it shows).</li></ul><p><strong>None of that is compliance work tacked on top of design. It’s just design work, finished properly.</strong></p><h3>Why designers, and why early</h3><p>There’s a reason this matters so much at the design stage specifically, and not just at QA or launch. <strong>Every one of the issues in that table is far cheaper to fix in a Figma file than in shipped code. </strong>A contrast problem caught in a design review is a token swap. The same contrast problem caught after launch is a ticket, a sprint, a regression test, and a developer annoyed at rework nobody budgeted for. A missing label caught while a content designer is still drafting form copy is a two-minute fix. The same gap caught by an auditor six months post-launch can mean a remediation plan, a legal risk assessment, and a much less pleasant conversation with leadership.</p><p><strong>Designers sit upstream of nearly all of this. That’s exactly why designers, more than any other role in the process, are positioned to make accessibility cheap instead of expensive.</strong> Not because they’re accessibility experts. Because they’re already the ones making the calls about hierarchy, contrast, labeling, and content, long before a single line of code gets written.</p><p>So here’s the confidence-building part, because a lot of designers feel intimidated by “accessibility standards” as a category, like it’s a body of legal knowledge they haven’t been trained in and might get wrong. Look back at that table one more time. Every single row starts with something you already know how to do. You don’t need to memorize WCAG success criteria numbers. You need to trust the instincts you already have, and treat <strong>“will this work for someone who can’t see color, can’t use a mouse, or is skimming on a screen reader”</strong> as just another design constraint, the same way you’d think about a slow connection or a small screen. It’s not a separate skill. It’s the same skill, applied a little further out.</p><h3>Content designers: you’re already doing this too</h3><p>Everything above focuses on interface and interaction, but there’s a whole other group of designers who are just as central to accessibility and often don’t realize it: <a href="https://digital.gov/guides/accessibility-for-teams/content-design/">content designers, UX writers, anyone shaping the words.</a></p><p><a href="https://plainlanguage.com/"><strong>Plain language</strong></a><strong> isn’t just good writing practice.</strong> It’s an accessibility intervention in its own right, for people with cognitive disabilities, for non-native speakers, for anyone reading on a phone at 6am before their first coffee. Short sentences. One idea per sentence. Familiar words instead of jargon. Clear instructions instead of clever ones. That’s <a href="https://www.w3.org/WAI/WCAG21/Understanding/reading-level.html">WCAG 3.1.5</a> (Reading Level) and <a href="https://www.w3.org/WAI/WCAG21/Understanding/help.html">3.3.5</a> (Help) in practice, even though almost nobody frames it that way in the writing room.</p><p>Here’s why this matters more than ever right now: a growing share of digital content is AI-authored or AI-assisted, and AI-generated text has a habit of drifting toward exactly the things plain language guidance warns against. It reaches for longer words when shorter ones would do. It nests qualifying clauses. It produces confident, fluent paragraphs that are genuinely harder to parse than they sound. None of that shows up in an automated accessibility scan, because reading level isn’t something a scanner can reliably score. It’s invisible in the data and enormous in the lived experience of the reader. <strong>That makes a sharp-eyed content designer, someone who edits AI output the same way they’d edit a junior writer’s draft, one of the most important accessibility roles in the organization right now. </strong>Not a nice-to-have. A frontline defense.</p><p>If you’re a content designer reading this and wondering where you fit into “the accessibility conversation,” the honest answer is: right at the center of it. You’ve probably been doing this work under the name “clarity” or “voice and tone” for years. It has another name too.</p><h3>A structural note for your design system</h3><p><strong>If you run or contribute to a design system, this table doubles as a component-audit checklist. </strong>Every row maps to something a shared component can enforce automatically: contrast tokens, required label props, semantic heading levels baked into typography components, link and button components that simply reject empty content. Standardizing this once at the component level does more to move WebAIM-style numbers than any amount of individual designer diligence, because it removes the failure mode at the source instead of hoping every contributor remembers it every single time.</p><h3>In closing…</h3><p><strong>If you’re a designer who has ever felt like accessibility is some separate credential you’re supposed to go earn, some badge you don’t have yet, I hope this article was a confidence boost. You’ve had this power the whole time!</strong></p><p>That instinct to tighten a headline, to pick a color that actually reads, to write a button label that tells the truth about what happens next: that’s not a soft skill sitting next to accessibility. That <em>is</em> accessibility, wearing a name tag you never bothered to read.</p><p>Every designer who’s ever obsessed over whether text felt legible, or rewritten a sentence until it finally made sense, or gotten irrationally annoyed by a button that just says “Submit,” has been quietly practicing this the entire time. You didn’t need a certification. You needed a translator. Consider this it.</p><p><strong>Go forth and use your powers for good. Turns out you had a cape in the closet the whole time.</strong></p><h3><strong>BUT WAIT, THERE’S MORE!</strong></h3><p>And if you want to learn even more about accessibility or usability, here are some books to check out. A few are explicitly about accessibility, and a few aren’t, but they all feed the same instincts this article is about.</p><p><strong>Accessibility and disability-inclusive design</strong></p><ul><li><a href="https://bookshop.org/p/books/a-web-for-everyone-designing-accessible-user-experiences-ms-sarah-horton/82f0fdcb78346d47?ean=9781933820972&amp;bkshp-astro=t"><em>A Web for Everyone: Designing Accessible User Experiences</em> </a>— the accessibility field guide for designers specifically, personas and all.</li><li><a href="https://bookshop.org/p/books/design-meets-disability-graham-pullin/5a235298f20a8844?ean=9780262516747&amp;bkshp-astro=t"><em>Design Meets Disability</em> </a>— on how disability has historically shaped some of design’s best ideas.</li><li><a href="https://bookshop.org/p/books/inclusive-design-for-a-digital-world-designing-with-accessibility-in-mind-regin-m-gilbert/793d4a7d25fefd44?ean=9798868818196&amp;next=t"><em>Inclusive Design for a Digital World</em> </a>— a practical, UX-focused rundown of designing for a wide range of disabilities.</li><li><a href="https://bookshop.org/search?keywords=Digital%20Accessibility%20Ethics%20Lainey%20Feingold"><em>Digital Accessibility Ethics: Disability Inclusion in All Things Tech</em></a> — brand new for 2026, an ethics framework for disability inclusion built by 39 authors across 10 countries.</li><li><a href="https://bookshop.org/p/books/mismatch-how-inclusion-shapes-design-kat-holmes/b231fc8d8d57fdc5?ean=9780262539487&amp;bkshp-astro=t"><em>Mismatch</em></a> — exclusion is a design choice, not an accident.</li></ul><p><strong>Design, usability, and communication</strong></p><ul><li><a href="https://bookshop.org/p/books/don-t-make-me-think-revisited-a-common-sense-approach-to-web-usability-steve-krug/d30340ad4751d00d?ean=9780321965516&amp;bkshp-astro=t"><em>Don’t Make Me Think</em> </a>— the usability bible: if people have to think about how to use it, it’s not designed well enough.</li><li><a href="https://www.amazon.com/Information-Anxiety-2-Hayden-Que/dp/0789724103/ref=pd_sbs_d_sccl_1_1/130-4163393-4523732?pd_rd_w=YDXOA&amp;content-id=amzn1.sym.aa738fbd-ad05-4d11-aae2-04b598db6305&amp;pf_rd_p=aa738fbd-ad05-4d11-aae2-04b598db6305&amp;pf_rd_r=BV986WN8ZVG18JJP7PXX&amp;pd_rd_wg=I0GqQ&amp;pd_rd_r=e95278ed-e6a3-4e7c-82e7-a7aee5fd487c&amp;pd_rd_i=0789724103&amp;psc=1"><em>Information Anxiety</em></a>— the classic on the gap between data and understanding, and why clarity is a design problem.</li><li><a href="https://bookshop.org/p/books/writing-is-designing-words-and-the-user-experience-andy-welfle/78df4057012288d5?ean=9781933820668&amp;bkshp-astro=t"><em>Writing Is Designing</em> </a>— the content design case, in book form, for everything this article argues about words.</li><li><a href="https://bookshop.org/p/books/100-things-every-designer-needs-to-know-about-people-susan-weinschenk/d9015c51818e96da?ean=9780136746911&amp;bkshp-astro=t"><em>100 Things Every Designer Needs to Know About People</em> </a>— the psychology behind why good design decisions work.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b29513a9b217" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/you-already-know-how-to-make-it-accessible-b29513a9b217">You already know how to make it accessible</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[Accessibility isn’t sexy… and other myths]]></title>
            <link>https://uxdesign.cc/accessibility-isnt-sexy-and-other-myths-c01997787c2f?source=rss-73e0ce48c6af------2</link>
            <guid isPermaLink="false">https://medium.com/p/c01997787c2f</guid>
            <category><![CDATA[accessibility]]></category>
            <category><![CDATA[inclusive-design]]></category>
            <category><![CDATA[a11y]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[user-experience]]></category>
            <dc:creator><![CDATA[Hope Turner]]></dc:creator>
            <pubDate>Wed, 28 Apr 2021 15:34:22 GMT</pubDate>
            <atom:updated>2021-04-29T21:26:45.080Z</atom:updated>
            <content:encoded><![CDATA[<p>When I talk to other designers about accessibility, they frequently shrug and say things like: “<em>I use the </em><a href="https://webaim.org/resources/contrastchecker/"><em>Color Contrast Tool</em></a><em>, so I’m compliant.</em>” That’s appreciated more than “<em>the dev team takes care of that and there is some kind of checklist they follow. I don’t really know, it’s not my job.</em>”</p><p>If you venture out into your bigger team, a project manager might express concern that your company can <em>“get sued because of </em><a href="https://www.essentialaccessibility.com/blog/ada-guidelines"><em>ADA laws</em></a><em>” </em>if your product doesn’t meet accessibility standards or they just don’t see a <a href="https://www.w3.org/WAI/business-case/">business case</a>. These non-design team members seem to be more motivated by the stick, instead of the carrot.</p><h3><strong>User-Centered Design</strong></h3><p>As designers, most of us say that we create <a href="https://www.usability.gov/what-and-why/user-centered-design.html">‘user-centered’ design</a>. And aren’t we carrot-motivated? We claim that we are empathetic. What does that really mean? <strong>If you aren’t actively participating in the process of ensuring that the end result is accessible, how are you truly centering your design on your user?</strong> Is your design and user research solely focused on the ‘able-bodied’ user?<em> (What does an ‘able-bodied’ user even look like by the way?)</em> Don’t you want to make sure that your product can be used by as many people as possible? I have many questions.</p><h3><strong>Misconceptions</strong></h3><p>I know that baking accessibility into the design process doesn’t seem to be common, or at least not with the designers I know. I think that there is an assumption that it’s too much work, or that it isn’t sexy — that accessibility isn’t innovative. Designers like freedom, not constraints.</p><p>We might think that accessible websites and apps will be ugly and boring if they are complying with accessibility standards. Or we could think that it’s just not worth worrying about when we have a heavy workload divided into <a href="https://www.ibm.com/able/toolkit/plan/sprint/">sprints</a> and no apparent place to start.</p><p>Maybe our managers don’t see the value and think it’s a waste of time because they don’t understand that accessibility can improve the user experience for everyone, not just people with disabilities. They don’t know that <a href="https://knowledge.wharton.upenn.edu/article/design-for-all-why-inclusion-matters-in-business/">“when we design for accessibility, it ends up benefiting a much broader group of people.”</a></p><p>Accessibility doesn’t have to be expensive, time-consuming, and hard to implement. If you start in the beginning, it can make a <a href="https://www.section508.gov/blog/benefits-accessible-design">big impact</a>. If you start mid-cycle, it still makes an impact. Towards the end of the project isn’t ideal to shoe-horn in accessibility, but it’s better than never. <strong>As with anything, it’s cost savings when you spend the time upfront. It’s never too late to start incorporating accessibility practices into your design process. </strong>Do what you can, when you can.</p><h3><strong>Taking Action</strong></h3><p>So <a href="https://www.w3.org/WAI/tips/designing/">what’s a designer to do</a>? How can you start making inroads on being accessible? A lot of designers operate in an agile world. Create some accessibility issues and put in your backlog. Sprinkle them in upcoming sprints. Update your <a href="https://xd.adobe.com/ideas/principles/design-systems/accessibility-in-design-systems/">design system</a> with <a href="https://www.smashingmagazine.com/2021/03/complete-guide-accessible-front-end-components/">accessible components</a> and create a design <a href="https://www.a11yproject.com/checklist/">checklist</a> for you and your team to follow. <strong>You can start small. Any effort to become more accessible will be a win. </strong>Talk to others, let them know that accessibility is not the sole responsibility of the developer. Spread the gospel! And read. There are a lot of <a href="https://www.goodreads.com/shelf/show/accessibility">good books</a> about inclusive design. Learn about the <a href="https://www.w3.org/WAI/standards-guidelines/wcag/">Web Content Accessibility Guidelines (WCAG)</a>. Add disabilities to your <a href="https://www.gov.uk/government/publications/understanding-disabilities-and-impairments-user-profiles">personas</a> to build empathy. When you are ready, go a step further and attend a conference like Knowbility’s <a href="https://knowbility.org/programs/accessu-2021">AccessU</a> or the CSUN <a href="https://www.csun.edu/cod/conference/sessions/">Assistive Technology Conference.</a></p><figure><img alt="“The one argument for accessibility, that doesn’t get made nearly often enough, is how extraordinarily better it makes some people’s lives. How many opportunities do we have to dramatically improve people’s lives just by doing our job a little better?” - Steve Krug" src="https://cdn-images-1.medium.com/max/1024/1*_qmWkp5UfXxOVLjSo9ic6g.png" /></figure><p>I know that people are stretched thin, we are all trying to do more with less — in this ‘work-from-home because COVID sucks’ world we find ourselves in. I know we have all experienced technology issues that disrupt our work and lives. Can you imagine if you had vision or hearing issues on top of what you have experienced? Recently there have been <a href="https://khn.org/news/article/covid-vaccine-websites-violate-disability-laws-create-inequity-for-the-blind/">reports</a> of websites for COVID testing and <a href="https://www.forbes.com/sites/forbesagencycouncil/2021/04/05/six-tips-for-making-vaccination-registration-websites-more-accessible-for-all/?sh=31666d692947">immunizations</a> not being accessible. We can do better than this. <strong>We should be concerned about the lack of ability to quickly roll out important information quickly to vulnerable populations like people with disabilities.</strong> Let’s be motivated by the carrot. Let’s do the right thing and help our users — all of them. <strong>Is there really anything sexier, in digital design, than an inclusive product that is easy and delightful to use?</strong></p><p>There’s a caveat to consider when you start trying to make some improvements to your product — you know that was coming, didn’t you? Even though I am encouraging people to go out of their comfort zone to learn something new and add more or different work to their plates, <strong>I don’t want to have it result in a band-aid fix.</strong> Y’all are familiar with this I’m sure. It’s where you don’t really have enough time — so you do something quick and easy just to ‘get ‘er’ done and promise to come back later. We all know how that works out. <strong>Don’t be tempted to cut corners by using any old accessibility tool out there on the web. </strong>Some of the tools you’ll find are <a href="https://www.ibm.com/able/toolkit/tools/">valid tools</a> that will benefit you, but I see there is a growing movement of covering up lack of accessibility with <a href="https://sheribyrnehaber.medium.com/overlays-are-not-the-solution-to-your-accessibility-problem-c5ffe44bd61f">overlays</a>, which are met with disdain by the accessibility community. (<em>Follow some accessibility people on LinkedIn and you’ll see what I mean!</em>) Step away from the overlay tool. It is not your friend. So make sure that when you do implement something, that it’s not actually creating more problems.</p><p>I’ll leave you with one suggestion to get started. <strong>Do a </strong><a href="https://inviqa.com/blog/accessibility-audits-how-do-quick-and-dirty-audit"><strong>‘quick and dirty’ manual audit</strong></a><strong> of your current site or app. </strong><a href="https://www.ibm.com/able/toolkit/verify/manual#test-without-a-keyboard"><strong>Use your keyboard without your trackpad or keyboard</strong></a><strong> for an hour. </strong>See what happens when you use the tab key. Does it go in the right order? Do you have a bright focus or selection color so you can see where your pointer is and what is selected? This way you will start finding accessibility bugs to submit to your dev team. You’ve got this!</p><h4>References:</h4><ul><li><a href="https://www.ibm.com/able/toolkit/verify/manual#test-without-a-keyboard">Manual</a></li><li><a href="https://inviqa.com/blog/accessibility-audits-how-do-quick-and-dirty-audit">Accessibility audits: how to do a &#39;quick and dirty&#39; audit</a></li><li><a href="https://sheribyrnehaber.medium.com/overlays-are-not-the-solution-to-your-accessibility-problem-c5ffe44bd61f">Overlays are not the solution to your accessibility problem</a></li><li><a href="https://www.forbes.com/sites/forbesagencycouncil/2021/04/05/six-tips-for-making-vaccination-registration-websites-more-accessible-for-all/?sh=31666d692947">Council Post: Six Tips For Making Vaccination Registration Websites More Accessible For All</a></li><li><a href="https://khn.org/news/article/covid-vaccine-websites-violate-disability-laws-create-inequity-for-the-blind/">Covid Vaccine Websites Violate Disability Laws, Create Inequity for the Blind</a></li><li><a href="https://www.gov.uk/government/publications/understanding-disabilities-and-impairments-user-profiles">Understanding disabilities and impairments: user profiles</a></li><li><a href="https://www.w3.org/WAI/standards-guidelines/wcag/">WCAG 2 Overview</a></li><li><a href="https://www.w3.org/WAI/business-case/">The Business Case for Digital Accessibility</a></li><li><a href="https://www.a11yproject.com/checklist/">Checklist - The A11Y Project</a></li><li><a href="https://webaim.org/resources/contrastchecker/">Contrast Checker</a></li><li><a href="https://www.essentialaccessibility.com/blog/ada-guidelines">ADA Website Accessibility Requirements and Guidelines</a></li><li><a href="https://www.usability.gov/what-and-why/user-centered-design.html">User-Centered Design Basics</a></li><li><a href="https://uxdesign.cc/future-tech-accessibility-e93600e8917e">Heck yes, accessibility! Let’s make the future awesome</a></li><li><a href="https://knowledge.wharton.upenn.edu/article/design-for-all-why-inclusion-matters-in-business/">Design for All: Why Inclusion Matters in Business - Knowledge@Wharton</a></li><li><a href="https://www.section508.gov/blog/benefits-accessible-design">Benefits of Accessible Design</a></li><li><a href="https://xd.adobe.com/ideas/principles/design-systems/accessibility-in-design-systems/">Building Accessibility Into Design Systems | Adobe XD Ideas</a></li><li><a href="https://www.w3.org/WAI/tips/designing/">Designing for Web Accessibility - Tips for Getting Started</a></li><li><a href="https://www.smashingmagazine.com/2021/03/complete-guide-accessible-front-end-components/">A Complete Guide To Accessible Front-End Components - Smashing Magazine</a></li><li><a href="https://knowbility.org/programs/accessu-2021">John Slatin Virtual AccessU 2021 - Knowbility</a></li><li><a href="https://www.csun.edu/cod/conference/sessions/">Center on Disabilities</a></li><li><a href="https://www.goodreads.com/shelf/show/accessibility">Accessibility Books</a></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/94/0*787qnqPXQkogO8bV" /><figcaption>The UX Collective donates US$1 for each article published on our platform. This story contributed to <a href="https://www.bayareablackdesigners.com/">Bay Area Black Designers</a>: a professional development community for Black people who are digital designers and researchers in the San Francisco Bay Area. By joining together in community, members share inspiration, connection, peer mentorship, professional development, resources, feedback, support, and resilience. Silence against systemic racism is not an option. Build the design community you believe in.</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c01997787c2f" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/accessibility-isnt-sexy-and-other-myths-c01997787c2f">Accessibility isn’t sexy… and other myths</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[Design Research Hack: When you want your design to be user-centered design and you don’t have…]]></title>
            <link>https://hopeturner.medium.com/design-research-hack-when-you-want-your-design-to-be-user-centered-design-and-you-dont-have-fd8184321d9d?source=rss-73e0ce48c6af------2</link>
            <guid isPermaLink="false">https://medium.com/p/fd8184321d9d</guid>
            <category><![CDATA[user-testing]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[design-hack]]></category>
            <category><![CDATA[usability]]></category>
            <category><![CDATA[user-research]]></category>
            <dc:creator><![CDATA[Hope Turner]]></dc:creator>
            <pubDate>Wed, 03 Feb 2021 03:11:42 GMT</pubDate>
            <atom:updated>2021-02-03T03:11:42.027Z</atom:updated>
            <content:encoded><![CDATA[<h3>Design Research Hack: When you want your design to be user-centered design and you don’t have access to users!</h3><p>For the last few years, I’ve been a user experience researcher on an enterprise software platform. Because this platform is very powerful, flexible and complex — learning how to use it can require some effort. Even after years of exposure to the various capabilities and their use cases, I find I still learn something new. I expect that won’t change. I won’t pretend that I know all the ‘ins and outs’ of all the features or all of their supporting use cases. It can take years of on-hands experience to gain that level of knowledge!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/450/1*YF8zJgs9XVSOFzCWG2zMWg.png" /><figcaption>Successful design requires teamwork and collaboration!</figcaption></figure><h3>The problem at hand…</h3><p>As a design researcher tasked with working across multiple, complicated capabilities that feed into the platform, I am very conscious that I am not my user. <strong>I need to institute a process of ongoing user testing research in my process to have any chance of success. I need to interview users, share designs with them, and get their feedback.</strong></p><p>Finding knowledgeable users that are capable of providing insights to the design team, is often not an easy nor viable method. And because of the varieties of use cases and roles of people using this software, it can be very challenging to find qualified and available people out in the wild, to engage in user testing. Identifying and ramping up new users is even more time consuming and often is not the most effective use of resources.</p><p>Online testing tools, that provide speedy and plentiful results, can fail us. It’s frequently near impossible to get meaningful insights or to trust that the participants are a good realistic representation of one of our user types. (<em>Don’t get me wrong, online tools do have their time and place).</em></p><p>And of course, there is always time. We all want fabulous, powerful insights, but often don’t have the time required to do the deep dives we would like to do to get there. In our agile world, we try to align our efforts into sprints and timebox our research in ways that challenge us. We want to stay a few steps ahead of the designers — and even more so, the developers.</p><h3><strong>What is a design researcher to do?</strong></h3><p><strong>If you are indeed working at a large software company, you have a wealth of knowledge available to you — if you just know where to look!</strong> My breakthrough came through one day when I was watching a YouTube video produced by someone internally in our technical sales team. The narrator of the video was friendly, engaging, and knowledgeable — so I reached out to him to have a quick Q&amp;A session. He ended up to be a great resource and collaborator — engaging and educating the design team. He provided relevant product history and summed up his interactions with some customers. Years later, we still regularly meet to discuss customer feedback or requests, as well as research sessions to review new designs. He has also pointed me to other internal people to help out with research efforts — and my network of knowledgeable participants has grown! (<em>If you are lucky enough to have a lab services team that help implement and extend your product, hit them up too</em>).</p><p>While <strong>technical sales people are not our users</strong>, they can be an invaluable source of useful and relevant information. They interface regularly with customers and are incentivized to make the platform attractive. <strong>Building close relationships with customers, they develop strong empathy and understanding of users. They are able to provide a unique perspective where they can aggregate the experience of many customers to communicate to the design team.</strong></p><p>Most technical sales people that I’ve invited to research sessions, have not only provided quick and valuable feedback, but were excited to collaborate with the design team. I highly recommend to designers and researchers, that have internal sales in their companies, to build relationships and collaborate on a regular basis. <em>The one caveat that I offer here is to understand the difference between a feature request and a customer pain point. Sales people can sometimes be interested in focusing on features that may not serve end users or solve for their pain points. It helps to understand the difference.</em></p><p>Once I was able to identify and connect with willing participants internally, I moved my focus outwards. <strong>IBM has a great network of business partners and that’s where I found my next set of collaborators</strong>. Business partners may not provide the brutally honest feedback that you will receive from tech sales, but remember their motivation is a little different. We have invited a few of our partners to collaborate with us in our Enterprise Design Thinking workshops and the value of our collaboration cannot be overstated. They provide a different perspective that helps us to get a well-rounded view of our product and customers.</p><h3>In summary…</h3><p><strong>When time and resources are tight, look around your company and see who might be able to provide product or customer insights.</strong> In large companies, you might have to get creative with finding the right people that can help. Look to see what has been publicly published on YouTube or discussion boards to <strong>find your internal subject matter experts</strong> (SMEs). Reach out to them. Even when they are the wrong person, they will often point you to other people that are more relevant.</p><p><strong>Connect with business partners. </strong>Investigate and see who already collaborates with your project managers or executives. It helps to have a formal introduction from someone at your company that already has an existing relationship with your partner, but if not, don’t be afraid to reach out and introduce yourself to explain that you would like to collaborate with them on design research.</p><p>And when you do identify your research collaborators, you can work with them to do the first pass of feedback on designs before sharing with your customers. <strong>These internal collaborators will help you identify the low-hanging fruit so that you can refine the designs and get more meaningful feedback from customers and users later.</strong> Meet with these folks regularly. Show them how you’ve improved the designs based on their feedback. Use this method of internal review to iterate and create stronger designs before sharing out to customers!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fd8184321d9d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Staying Sane in a Creative Career]]></title>
            <link>https://hopeturner.medium.com/staying-sane-in-a-creative-career-f65c57f331f5?source=rss-73e0ce48c6af------2</link>
            <guid isPermaLink="false">https://medium.com/p/f65c57f331f5</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[career-advice]]></category>
            <category><![CDATA[career-paths]]></category>
            <category><![CDATA[gen-x]]></category>
            <dc:creator><![CDATA[Hope Turner]]></dc:creator>
            <pubDate>Thu, 14 Mar 2019 19:25:29 GMT</pubDate>
            <atom:updated>2019-03-14T19:25:29.082Z</atom:updated>
            <content:encoded><![CDATA[<p>Someone recently asked me how I managed to stay in my chosen career of design for so long. As a creative person, they asked, how did I deal with avoiding creative burn-out? How did I know that I would end up where I’ve found myself? Wasn’t I bored doing the same thing for so long? Was it true that all designers did was to play video games?</p><p>Let’s start with the easy question… Nope! Designers don’t play video games all day. Another urban myth debunked. To answer those harder questions, let’s start at the beginning…</p><p>When I was in second grade, my teacher asked me what I wanted to be when I grew up. My split-second response was that I wanted to be an artist. When my family heard this news, they laughed and said something about waiting to see what I decided when I was older. They thought that as college loomed closer that I would aspire to something much more practical and prosperous, i.e., doctor or lawyer.</p><p>After graduating high school, I stayed true to my calling. I applied, and was accepted, to art school at Virginia Commonwealth University, School of the Arts. (My parents groaned and envisioned life for me as continually struggling to make ends meet — hawking velvet Elvis paintings out of the back of a run-down van, on a street corner somewhere). Four years later, I graduated with a shiny new BFA degree, that stated I had indeed completed the esteemed Communication Arts &amp; Design program.</p><p>While I was in college, my assumption was that I would find a job as a graphic designer for a magazine or newspaper. When I graduated in 1993, most design school graduates had traditional training, which meant that their career opportunities were based in the “print” world. Few designers left school with even the most basic of digital skills. Luckily during my junior year, the administration replaced some drafting tables with computers and I quickly discovered a passion for Macs and Photoshop. It was then that I knew that I was destined for a career in “multimedia,” even though I wasn’t even sure what that entailed. But it was exciting and new, who didn’t want a piece of that?</p><p>And I’ll tell you now… It’s been a wild ride. This career has not come without challenges. It’s been exciting, frustrating, boring, scary and exciting again. More than a few times. There has been plenty of uncertainty and discomfort along the way. I have worked on quite a range of creative projects: print marketing materials, internationally and nationally broadcast commercials, corporate intranets, e-commerce web sites, logo design and branding, touch screen kiosks, product design and design research. I have worked for ad agencies, software development companies, design firms, in-house at large corporations, small start-ups, and for myself, as a freelancer.</p><p>In my current job at IBM, I recently made the transition into a new role as a design researcher from a ux product designer position. In past jobs, I had taken on small pieces of research and assisted others in their research efforts, but this is the first time that it became my main focus and responsibility. It’s been a big adjustment for me, moving from agile design deliverables to more slow moving, strategic research projects that require deep digging in a highly technical domain that I am still learning about. It requires a different skill set to engage with product management, development, design, and customers. I have some days that are truly challenging because I’m less experienced in this discipline. It can be tough to handle the feelings of unrest and uneasiness brought from not knowing what you don’t know.</p><h3>What I’ve learned along the way</h3><p>What I’ve learned over the past 20+ years of my design career is, that the key to remaining sane, engaged, and relevant through the years, is flexibility. Having a sense of adventure and curiosity, helps to manage the fear brought forth by uncertainty. Being open to learning new software or a process is critical. Accepting challenges, when faced with new opportunities that seem risky, or take you well out of your comfort zone, can keep your career from becoming stale.</p><p>When I do find myself struggling, as one does in this line of work, I evaluate myself and my feelings to see where I can make changes to improve my situation or attitude. If you could somehow hear my inner dialogue at these times, it might sound like this… just not quite as linear and clear-cut…</p><h3><strong>10 Tips To Help Keep You Sane</strong></h3><p>1. <strong>Be open-minded.</strong> Try to avoid being resistant to change. Change is hard. Change is scary. Keep an open mind when opportunities present themselves. Stay curious.</p><p>2. <strong>Be brave.</strong> Don’t be afraid to say yes. Try to level up. This partners well with “be open minded.” Think about the rewards in addition to the risk. It’s hard to grow without taking risks. (This is where I channel my inner Brené Brown).</p><p>3. <strong>Keep current with latest design trends and tools.</strong> Network with other creative people. Check Amazon periodically for new design/research books. Keep learning. Get inspired.</p><p>4. <strong>Take the time to re-evaluate the way you work.</strong> Just because you’ve been doing something the same way for years, doesn’t necessarily mean that you should continue. It’s easy to grow comfortable and crank out work without much effort. Auto-pilot is dangerous. Make time to audit your process.</p><p>5. <strong>Take a break.</strong> Breaking out of your day-to-day routine can help free you from the mundane. Working remotely from home, a coffee shop, or even a different location in your office, provides a change of environment that might inspire you be more creative and generate the bigger ideas. If you are in the office, stepping away for a little while to grab coffee or take a quick break outside can help you to reset and readjust your focus. Overthinking things can be counterproductive and breaks can derail that train.</p><p>6. <strong>Consider what you’re working on.</strong> Check in with yourself and ask if the work you are doing is stretching you and moving you forward. Does it propel you out of bed in the morning? Are you content in your discipline? Is it time to branch out and try something new? Do you need new skills?</p><p>7. <strong>Keep challenging yourself if your job isn’t challenging you.</strong> If you’ve exhausted all means to fight burn-out and your creative juices have dried up, it might be time to consider interviewing elsewhere for a new job. Maybe you want to interview at a new company, or maybe it’s another department at your current company. Sometimes picking up some freelance or volunteer design work will get you over the hump when your normal day job just isn’t doing it for you. Collaborating with others can help you generate new ideas and spark creativity.</p><p>8. <strong>Find your joy.</strong> Find a product or project that makes you happy or inspires you. Working on something that supports your personal beliefs or helps you learn a new and interesting domain can give you a sense of satisfaction. Having a sense of purpose makes a huge difference.</p><p>9. <strong>Do a sanity check.</strong> Most creative people that I know, are collaborative people. We rely on feedback and constructive criticism. If you’re feeling stuck or dissatisfied, solicit advice from trust-worthy people that are knowledgeable about your career and field — whether it’s a coworker, friend or someone you work with on another team. Having a mentor can also help keep you on track and focused. As good as it is to be introspective, it’s also good to get an outside perspective and get that sanity check!</p><p>10. <strong>Be kind to yourself.</strong> Don’t beat yourself up if you’re not in the place you want to be. Be introspective, but not overly critical, about your work or job. Think about actionable steps you can take to move closer towards a goal. If it seems that baby steps are all you can manage, try not to be discouraged and realize that it’s progress.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f65c57f331f5" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>