{"id":1347,"date":"2024-06-26T12:00:00","date_gmt":"2024-06-26T12:00:00","guid":{"rendered":"http:\/\/suimy.me\/?p=1347"},"modified":"2024-06-26T17:04:35","modified_gmt":"2024-06-26T17:04:35","slug":"how-to-make-a-strong-case-for-accessibility","status":"publish","type":"post","link":"http:\/\/suimy.me\/index.php\/2024\/06\/26\/how-to-make-a-strong-case-for-accessibility\/","title":{"rendered":"How To Make A Strong Case For Accessibility"},"content":{"rendered":"<p>              <title>How To Make A Strong Case For Accessibility<\/title><\/p>\n<article>\n<header>\n<h1>How To Make A Strong Case For Accessibility<\/h1>\n<address>Vitaly Friedman<\/address>\n<p>                  2024-06-26T12:00:00+00:00<br \/>\n                  2024-06-26T16:35:11+00:00<br \/>\n                <\/header>\n<p>Getting support for accessibility efforts isn\u2019t easy. There are many <a href=\"https:\/\/a11ymyths.com\/\">accessibility myths<\/a>, wrong assumptions, and expectations that make accessibility look like a complex, expensive, and time-consuming project. Let\u2019s fix that!<\/p>\n<p>Below are some practical techniques that have been working well for me to <strong>convince stakeholders<\/strong> to support and promote accessibility in small and large companies.<\/p>\n<p>.course-intro{&#8211;shadow-color:206deg 31% 60%;background-color:#eaf6ff;border:1px solid #ecf4ff;box-shadow:0 .5px .6px hsl(var(&#8211;shadow-color) \/ .36),0 1.7px 1.9px -.8px hsl(var(&#8211;shadow-color) \/ .36),0 4.2px 4.7px -1.7px hsl(var(&#8211;shadow-color) \/ .36),.1px 10.3px 11.6px -2.5px hsl(var(&#8211;shadow-color) \/ .36);border-radius:11px;padding:1.35rem 1.65rem}@media (prefers-color-scheme:dark){.course-intro{&#8211;shadow-color:199deg 63% 6%;border-color:var(&#8211;block-separator-color,#244654);background-color:var(&#8211;accent-box-color,#19313c)}}<\/p>\n<p class=\"course-intro\">This article is <strong>part of our ongoing series<\/strong> on <a href=\"\/category\/ux\">UX<\/a>. You might want to take a look at <a style=\"font-weight:700\" href=\"https:\/\/smart-interface-design-patterns.com\/\">Smart Interface Design Patterns<\/a>\u00a0\ud83c\udf63 and the <a href=\"https:\/\/smashingconf.com\/online-workshops\/workshops\/interface-design-course-vitaly-friedman\/\">upcoming live UX training<\/a> as well. Use code <a style=\"text-decoration:none !important\" href=\"https:\/\/smart-interface-design-patterns.com\/\"><strong>BIRDIE<\/strong><\/a> to <strong>save 15%<\/strong> off.<\/p>\n<h2 id=\"launching-accessibility-efforts\">Launching Accessibility Efforts<\/h2>\n<p>A common way to address accessibility is to speak to stakeholders through the lens of corporate responsibility and ethical and legal implications. Personally, I\u2019ve never been very successful with this strategy. People typically dismiss concerns that they can\u2019t relate to, and as designers, <strong>we can\u2019t build empathy with facts<\/strong>, charts, or legal concerns.<\/p>\n<p>The problem is that people often don\u2019t know how accessibility applies to them. There is a common assumption that accessibility is dull and boring and leads to \u201cunexciting\u201d and unattractive products. Unsurprisingly, businesses often neglect it as an <strong>irrelevant edge case<\/strong>.<\/p>\n<figure class=\"\n  \n  \n  \"><\/p>\n<p>    <a href=\"https:\/\/medium.com\/booking-research\/building-accessibility-research-practices-75d82098f286\"><\/p>\n<p>    <img loading=\"lazy\" width=\"800\" height=\"1326\" src=\"data:image\/gif;base64,R0lGODlhAQABAAAAACH5BAEKAAEALAAAAAABAAEAAAICTAEAOw==\" alt=\"Travel adaptation of Microsoft\u2019s Inclusive Design Toolkit\" class=\"lazyload\" data-src=\"https:\/\/res.cloudinary.com\/indysigner\/image\/fetch\/f_auto,q_80\/w_400\/https:\/\/files.smashing.media\/articles\/how-make-strong-case-accessibility\/1-travel-adaptation-microsoft-inclusive-design-toolkit.jpeg\"><\/p>\n<p>    <\/a><figcaption class=\"op-vertical-bottom\">\n      Mapping accessibility to the needs of a product, example by Booking.com. (<a href=\"https:\/\/files.smashing.media\/articles\/how-make-strong-case-accessibility\/1-travel-adaptation-microsoft-inclusive-design-toolkit.jpeg\">Large preview<\/a>)<br \/>\n    <\/figcaption><\/figure>\n<p>So, I use another strategy. I start conversations about accessibility by <strong>visualizing it<\/strong>. I explain the <strong>different types of accessibility needs<\/strong>, ranging from permanent to temporary to situational \u2014 and I try to explain what <em>exactly<\/em> it actually means to our products. Mapping a more generic understanding of accessibility to the specifics of a product helps everyone explore accessibility from a point that they can relate to.<\/p>\n<p>And then I launch a small effort \u2014 just a few <strong>usability sessions<\/strong>, to get a better understanding of where our customers struggle and where they might be blocked. If I can\u2019t get access to customers, I try to proxy test via sales, customer success, or support. Nothing is more impactful than seeing real customers struggling in their real-life scenario with real products that a company is building.<\/p>\n<figure class=\"\n  \n  \n  \"><\/p>\n<p>    <a href=\"https:\/\/www.linkedin.com\/posts\/vitalyfriedman_accessibility-activity-7124747846431436800-rG2w\/\"><\/p>\n<p>    <img loading=\"lazy\" width=\"800\" height=\"798\" src=\"data:image\/gif;base64,R0lGODlhAQABAAAAACH5BAEKAAEALAAAAAABAAEAAAICTAEAOw==\" alt=\"WCAG 2.2 Accessibility Guidelines map\" class=\"lazyload\" data-src=\"https:\/\/res.cloudinary.com\/indysigner\/image\/fetch\/f_auto,q_80\/w_400\/https:\/\/files.smashing.media\/articles\/how-make-strong-case-accessibility\/2-wcag-accessibility-guidelines-illustration.jpeg\"><\/p>\n<p>    <\/a><figcaption class=\"op-vertical-bottom\">\n      New WCAG 2.2 Accessibility Guidelines, a poster by fine folks at <a href=\"https:\/\/www.linkedin.com\/company\/intopia-digital\/?lipi=urn%3Ali%3Apage%3Ad_flagship3_detail_base%3B%2B6vEnbAXR7iICoERG4TppA%3D%3D\">Intopia<\/a>. (<a href=\"https:\/\/files.smashing.media\/articles\/how-make-strong-case-accessibility\/2-wcag-accessibility-guidelines-illustration.jpeg\">Large preview<\/a>)<br \/>\n    <\/figcaption><\/figure>\n<p>From there, I move forward. I explain inclusive design, accessibility, <strong>neurodiversity<\/strong>, <strong>EAA<\/strong>, <strong>WCAG<\/strong>, <strong>ARIA<\/strong>. I bring people with disabilities into testing as we need a proper representation of our customer base. I ask for small commitments first, then ask for more. I reiterate over and over and over again that accessibility doesn\u2019t have to be expensive or tedious if done early, but it can be <strong>very expensive<\/strong> when <strong>retrofitted<\/strong> or done late.<\/p>\n<p>Throughout that entire journey, I try to <strong>anticipate objections<\/strong> about costs, timing, competition, slowdowns, dullness \u2014 and keep explaining how accessibility can reduce costs, increase revenue, grow user base, minimize risks, and improve our standing in new markets. For that, I use a few <strong>templates<\/strong> that I always keep nearby just in case an argument or doubts arise.<\/p>\n<h2 id=\"useful-templates-to-make-a-strong-case-for-accessibility\">Useful Templates To Make A Strong Case For Accessibility<\/h2>\n<h3 id=\"1-but-accessibility-is-an-edge-case\">1. \u201cBut Accessibility Is An Edge Case!\u201d<\/h3>\n<p>\u274c \u201c<strong>But accessibility is an edge case.<\/strong> Given the state of finances right now, unfortunately, we really can\u2019t invest in it right now.\u201d<\/p>\n<p>\ud83d\ude45\ud83c\udffd\u2640\ufe0f \u201cI respectfully disagree. 1 in 6 people around the world experience disabilities. In fact, our competitors <em>[X, Y, Z]<\/em> have launched accessibility efforts (<em>[references]<\/em>), and we seem to be lagging behind. Plus, it doesn\u2019t have to be expensive. But it will be very expensive once we retrofit much later.\u201d<\/p>\n<h3 id=\"2-but-there-is-no-business-value-in-accessibility\">2. \u201cBut There Is No Business Value In Accessibility!\u201d<\/h3>\n<p>\u274c \u201cWe know that accessibility is important, but at the moment, we need to focus on efforts that will <strong>directly benefit business<\/strong>.\u201d<\/p>\n<p>\ud83d\ude45\ud83c\udffc\u2642\ufe0f \u201cI understand what you are saying, but actually, accessibility directly benefits business. Globally, the extended market is estimated at <a href=\"https:\/\/www.w3.org\/WAI\/business-case\/#fn:18\"><strong>2.3 billion people<\/strong><\/a>, who control an incremental $6.9 trillion in annual disposable income. Prioritizing accessibility very much aligns with your goal to <strong>increase leads<\/strong>, <strong>customer engagement<\/strong>, mitigate risk, and reduce costs.\u201d (via <a href=\"https:\/\/www.smashingmagazine.com\/2024\/02\/web-designer-accessibility-advocacy-toolkit\/\">Yichan Wang<\/a>)<\/p>\n<h3 id=\"3-but-we-don-t-have-disabled-users\">3. \u201cBut We Don\u2019t Have Disabled Users!\u201d<\/h3>\n<p>\u274c \u201cWhy should we prioritize accessibility? Looking at our data, <strong>we don\u2019t really have any disabled users<\/strong> at all. Seems like a waste of time and resources.\u201d<\/p>\n<p>\ud83d\ude45\u2640\ufe0f \u201cWell, if a product is inaccessible, users with disabilities can\u2019t and won\u2019t be using it. But if we do make our product more accessible, we open the door for prospect users for years to come. Even small improvements can have a high impact. It doesn\u2019t have to be expensive nor time-consuming.\u201d<\/p>\n<h3 id=\"4-screen-readers-won-t-work-with-our-complex-system\">4. \u201cScreen Readers Won\u2019t Work With Our Complex System!\u201d<\/h3>\n<p>\u274c \u201cOur application is very complex and used by expert users. Would it even <strong>work at all with screen readers<\/strong>?\u201d<\/p>\n<p>\ud83d\ude45\ud83c\udffb\u2640\ufe0f \u201cIt\u2019s not about designing only for screen readers. Accessibility can be permanent, but it can also be temporary and situational \u2014 e.g., when you hold a baby in your arms or if you had an accident. Actually, it\u2019s universally useful and beneficial for everyone.\u201d<\/p>\n<h3 id=\"5-we-can-t-win-market-with-accessibility-features\">5. \u201cWe Can\u2019t Win Market With Accessibility Features!\u201d<\/h3>\n<p>\u274c \u201cTo increase our market share, we need <strong>features that benefit everyone<\/strong> and improve our standing against competition. We can\u2019t win the market with accessibility.\u201d<\/p>\n<p>\ud83d\ude45\ud83c\udffe\u2642\ufe0f \u201cModern products succeed not by designing more features, but by <strong>designing better features<\/strong> that improve customer\u2019s efficiency, success rate, and satisfaction. And accessibility is one of these features. For example, voice control and auto-complete were developed for accessibility but are now widely used by everyone. In fact, the entire customer base benefits from accessibility features.\u201d<\/p>\n<h3 id=\"6-our-customers-can-t-relate-to-accessibility-needs\">6. \u201cOur Customers Can\u2019t Relate To Accessibility Needs\u201d<\/h3>\n<p>\u274c \u201cOur research clearly shows that our <strong>customers are young and healthy, and they don\u2019t have accessibility needs<\/strong>. We have other priorities, and accessibility isn\u2019t one of them.\u201d<\/p>\n<p>\ud83d\ude45\u2640\ufe0f \u201cI respectfully disagree. People of all ages can have accessibility needs. In fact, accessibility features show your commitment to inclusivity, reaching out to every potential customer of any age, regardless of their abilities.<\/p>\n<p>This not only resonates with a diverse audience but also positions your brand as socially responsible and empathetic. As you know, our young user base increasingly <strong>values corporate responsibility<\/strong>, and this can be a significant differentiator for us, helping to build a loyal customer base for years to come.\u201d (via <a href=\"https:\/\/www.smashingmagazine.com\/2024\/02\/web-designer-accessibility-advocacy-toolkit\/\">Yichan Wang<\/a>)<\/p>\n<h3 id=\"7-let-s-add-accessibility-later\">7. \u201cLet\u2019s Add Accessibility Later\u201d<\/h3>\n<p>\u274c \u201cAt the moment, we need to focus on the core features of our product. We can always <strong>add accessibility later<\/strong> once the product is more stable.\u201d<\/p>\n<p>\ud83d\ude45\ud83c\udffc \u201cI understand concerns about timing and costs. However, it\u2019s important to note that integrating accessibility from the start is <strong>far more cost-effective<\/strong> than retrofitting it later. If accessibility is considered after development is complete, we will face <strong>significant additional expenses<\/strong> for auditing accessibility, followed by potentially extensive work involving a redesign and redevelopment.<\/p>\n<p>This process can be significantly more expensive than embedding accessibility from the beginning. Furthermore, delaying accessibility can expose your business to <strong>legal risks<\/strong>. With the increasing number of lawsuits for non-compliance with accessibility standards, the cost of legal repercussions could far exceed the expense of implementing accessibility now. The financially prudent move is to work on accessibility now.\u201d<\/p>\n<p>You can find more useful ready-to-use templates in Yichan Wang\u2019s <a href=\"https:\/\/www.smashingmagazine.com\/2024\/02\/web-designer-accessibility-advocacy-toolkit\/\">Designer\u2019s Accessibility Advocacy Toolkit<\/a> \u2014 a fantastic resource to keep nearby.<\/p>\n<h2 id=\"building-accessibility-practices-from-scratch\">Building Accessibility Practices From Scratch<\/h2>\n<p>As mentioned above, nothing is more impactful than <strong>visualizing accessibility<\/strong>. However, it requires building accessibility research and accessibility practices from scratch, and it might feel like an impossible task, especially in large corporations. In \u201c<a href=\"https:\/\/medium.com\/booking-research\/building-accessibility-research-practices-75d82098f286\">How We\u2019ve Built Accessibility Research at Booking.com<\/a>\u201d, <a href=\"https:\/\/www.linkedin.com\/in\/ACoAABwTwRgBMVwjQS20ThRxGE3YPNRvonGR87k?lipi=urn%3Ali%3Apage%3Ad_flagship3_pulse_read%3BA6l3Kt%2BkS567Gmf%2BADQrBA%3D%3D\">Maya Alvarado<\/a> presents a fantastic case study on how to build accessibility practices and inclusive design into UX research from scratch.<\/p>\n<p>Maya rightfully points out that <strong>automated accessibility testing alone isn\u2019t reliable<\/strong>. Compliance means that a user can use your product, but it doesn\u2019t mean that it\u2019s a great user experience. With manual testing, we make sure that customers actually meet their goals and do so effectively.<\/p>\n<figure class=\"\n  \n  \n  \"><\/p>\n<p>    <a href=\"https:\/\/www.linkedin.com\/posts\/yjwoo_inclusivedesign-universaldesign-accessibledesign-activity-7143719973570396160-liy1\/?utm_source=share&amp;utm_medium=member_desktop\"><\/p>\n<p>    <img loading=\"lazy\" width=\"800\" height=\"686\" src=\"data:image\/gif;base64,R0lGODlhAQABAAAAACH5BAEKAAEALAAAAAABAAEAAAICTAEAOw==\" alt=\"Visualization of Universal design vs. Inclusive design vs. Accessible design in the form of circles, where an accessible is the smallest, and universal is the biggest.\" class=\"lazyload\" data-src=\"https:\/\/res.cloudinary.com\/indysigner\/image\/fetch\/f_auto,q_80\/w_400\/https:\/\/files.smashing.media\/articles\/how-make-strong-case-accessibility\/3-universal-vs-inclusive-vs-accessible-design.png\"><\/p>\n<p>    <\/a><figcaption class=\"op-vertical-bottom\">\n      Universal design vs. Inclusive design vs. Accessible design. A visualization by Eugene Woo. (<a href=\"https:\/\/files.smashing.media\/articles\/how-make-strong-case-accessibility\/3-universal-vs-inclusive-vs-accessible-design.png\">Large preview<\/a>)<br \/>\n    <\/figcaption><\/figure>\n<p>Start by gathering colleagues and stakeholders interested in accessibility. Document what research was done already and where the gaps are. And then whenever possible, include 5\u201312 users with disabilities in accessibility testing.<\/p>\n<p>Then, run a <strong>small accessibility initiative around key flows<\/strong>. Tap into critical touch points and research them. As you are making progress, extend to components, patterns, flows, and service design. And eventually, incorporate <strong>inclusive sampling<\/strong> into all research projects \u2014 at least 15% of usability testers should have a disability.<\/p>\n<p>Companies often struggle to <strong>recruit testers with disabilities<\/strong>. One way to find participants is to reach out to local chapters, local training centers, non-profits, and public communities of users with disabilities in your country. Ask the admin\u2019s permission to post your research announcement, and it won\u2019t be rejected. If you test on site, <strong>add extra $25\u2013$50<\/strong> depending on disability transportation.<\/p>\n<p>I absolutely love the idea of extending <a href=\"https:\/\/inclusive.microsoft.design\/\">Microsoft\u2019s Inclusive Design Toolkit<\/a> to meet specific user needs of a product. It adds a different dimension to disability considerations which might be less abstract and much easier to relate for the entire organization.<\/p>\n<p>As Maya noted, inclusive design is about building a door that can be opened by anyone and lets everyone in. <strong>Accessibility isn\u2019t a checklist<\/strong> \u2014 it\u2019s a practice that goes beyond compliance. A practice that involves actual people with actual disabilities throughout all UX research activities.<\/p>\n<h2 id=\"wrapping-up\">Wrapping Up<\/h2>\n<p>To many people, accessibility is a <strong>big mystery box<\/strong>. They might have never seen a customer with disabilities using their product, and they don\u2019t really understand what it involves and requires. But we can <strong>make accessibility relatable<\/strong>, approachable, and visible by bringing accessibility testing to our companies \u2014 even if it\u2019s just a handful of tests with people with disabilities.<\/p>\n<p>No manager really wants to <strong>deliberately ignore the needs<\/strong> of their paying customers \u2014 they just need to understand these needs first. Ask for small commitments, and get the ball rolling from there.<\/p>\n<p><strong>Set up an accessibility roadmap<\/strong> with actions, timelines, roles and goals. Frankly, this strategy has been working for me much better than arguing about legal and moral obligations, which typically makes stakeholders defensive and reluctant to commit.<\/p>\n<p><strong>Fingers crossed!<\/strong> And a huge <strong>thank-you<\/strong> to everyone working on and improving accessibility in your day-to-day work, often without recognition and often fueled by your own enthusiasm and passion \u2014 thank you for your incredible work in pushing accessibility forward! \ud83d\udc4f\ud83c\udffc\ud83d\udc4f\ud83c\udffd\ud83d\udc4f\ud83c\udffe<\/p>\n<h2 id=\"useful-resources\">Useful Resources<\/h2>\n<h3 id=\"making-a-case-for-accessibility\">Making A Case For Accessibility<\/h3>\n<ul>\n<li>\u201c<a href=\"https:\/\/www.deque.com\/blog\/the-business-case-for-accessibility\/\">How To Make The Business Case For Accessibility<\/a>\u201d, by R Gregory Williams<\/li>\n<li>\u201c<a href=\"https:\/\/medium.com\/booking-research\/building-accessibility-research-practices-75d82098f286\">How We\u2019ve Built Accessibility Research at Booking.com<\/a>\u201d, by Maya Alvarado<\/li>\n<li>\u201c<a href=\"https:\/\/www.smashingmagazine.com\/2024\/02\/web-designer-accessibility-advocacy-toolkit\/\">Designer\u2019s Accessibility Advocacy Toolkit<\/a>\u201d, by Yichan Wang<\/li>\n<li>\u201c<a href=\"https:\/\/medium.com\/google-design\/making-the-case-for-accessibility-350da9e30c84\">Making The Case for Accessibility<\/a>\u201d, by Susanna Zaraysky<\/li>\n<li>\u201c<a href=\"https:\/\/www.smashingmagazine.com\/2021\/07\/strong-case-for-accessibility\/\">Making A Strong Case For Accessibility<\/a>\u201d, by Todd Libby<\/li>\n<li>\u201c<a href=\"https:\/\/www.deque.com\/resources\/type\/accessibility-case-studies\/\">Accessibility Case Studies and Success Stories<\/a>\u201d, by Deque<\/li>\n<li>\u201c<a href=\"https:\/\/www.linkedin.com\/posts\/vitalyfriedman_ux-design-accessibility-activity-7031928918429331456-ImIn\/?lipi=urn%3Ali%3Apage%3Ad_flagship3_pulse_read%3BA6l3Kt%2BkS567Gmf%2BADQrBA%3D%3D\">Inclusive Design Toolkits and Templates<\/a>\u201d, by yours truly<\/li>\n<\/ul>\n<h3 id=\"accessibility-testing\">Accessibility Testing<\/h3>\n<ul>\n<li>\u201c<a href=\"https:\/\/dscout.com\/people-nerds\/accessible-user-research-1\">A Comprehensive Guide to Accessible UX Research<\/a>\u201d, by Brian Grellmann<\/li>\n<li>\u201c<a href=\"https:\/\/tetralogical.com\/blog\/2022\/08\/01\/inclusive-user-research-recruiting-participants\/\">Inclusive User Research: Recruiting Participants<\/a>\u201d, by Ela Gorla<\/li>\n<li>\u201c<a href=\"https:\/\/medium.com\/design-bridges\/accessibility-testing-babe2d84e817\">Testing With Blind Users: A Cheatsheet<\/a>\u201d, by Slava Shestopalov<\/li>\n<li>\u201c<a href=\"https:\/\/www.nngroup.com\/articles\/mobile-accessibility-research\/\">Mobile Accessibility Research with Screen-Reader Users<\/a>\u201d, by Tanner Kohler<\/li>\n<li>\u201c<a href=\"https:\/\/www.smashingmagazine.com\/2018\/03\/tips-conducting-usability-studies-participants-disabilities\/\">How To Conduct UX Research With Participants With Disabilities<\/a>\u201d, by Peter McNally<\/li>\n<li>\u201c<a href=\"https:\/\/www.answerlab.com\/insights\/answering-your-accessibility-questions\">How To Conduct Accessibility UX Research<\/a>\u201d, by AnswerLab<\/li>\n<\/ul>\n<h2 id=\"meet-smart-interface-design-patterns\">Meet Smart Interface Design Patterns<\/h2>\n<p>If you are interested in <strong>UX and design patterns<\/strong>, take a look at <a href=\"https:\/\/smart-interface-design-patterns.com\/\"><strong>Smart Interface Design Patterns<\/strong><\/a>, our <strong>10h-video course<\/strong> with 100s of practical examples from real-life projects \u2014 with a live UX training later this year. Everything from mega-dropdowns to complex enterprise tables \u2014 with 5 new segments added every year. <a href=\"https:\/\/www.youtube.com\/watch?v=aSP5oR9g-ss\">Jump to a free preview<\/a>. Use code <a href=\"https:\/\/smart-interface-design-patterns.com\"><strong>BIRDIE<\/strong><\/a> to <strong>save 15%<\/strong> off.<\/p>\n<figure style=\"margin-bottom: 0\"><a href=\"https:\/\/smart-interface-design-patterns.com\/\"><img loading=\"lazy\" style=\"border-radius: 11px\" width=\"950\" height=\"492\" src=\"data:image\/gif;base64,R0lGODlhAQABAAAAACH5BAEKAAEALAAAAAABAAEAAAICTAEAOw==\" alt=\"Smart Interface Design Patterns\" class=\"lazyload\" data-src=\"https:\/\/res.cloudinary.com\/indysigner\/image\/fetch\/f_auto,q_80\/w_400\/https:\/\/archive.smashing.media\/assets\/344dbf88-fdf9-42bb-adb4-46f01eedd629\/7cc4e1de-6921-474e-a3fb-db4789fc13dd\/b4024b60-e627-177d-8bff-28441f810462.jpeg\"><\/a><figcaption class=\"op-vertical-bottom\">Meet <a href=\"https:\/\/smart-interface-design-patterns.com\/\">Smart Interface Design Patterns<\/a>, our video course on interface design &amp; UX.<\/figcaption><\/figure>\n<div class=\"btn--lined btn--lined--white-border\" style=\"margin-top: 0.75em;margin-bottom: 0.75em\"><a class=\"btn btn--large btn--green btn--text-shadow\" href=\"https:\/\/smart-interface-design-patterns.com\/\">Jump to the video course\u00a0\u2192<\/a><\/div>\n<\/p>\n<p class=\"ticket-price__desc\" style=\"font-size: .8em!important;text-align: center;line-height: 1.5;margin: 0\">100 design patterns &amp; real-life<br \/>\nexamples.<br \/>10h-video course + live UX training. <a href=\"https:\/\/www.youtube.com\/watch?v=aSP5oR9g-ss\">Free preview<\/a>.<\/p>\n<div class=\"signature\">\n  <img src=\"data:image\/gif;base64,R0lGODlhAQABAAAAACH5BAEKAAEALAAAAAABAAEAAAICTAEAOw==\" alt=\"Smashing Editorial\" width=\"35\" height=\"46\" loading=\"lazy\" class=\"lazyload\" data-src=\"https:\/\/www.smashingmagazine.com\/images\/logo\/logo--red.png\"><br \/>\n  <span>(yk)<\/span>\n<\/div>\n<\/article>\n","protected":false},"excerpt":{"rendered":"<p>How To Make A Strong Case For Accessibility How To Make A Strong Case For Accessibility Vitaly Friedman 2024-06-26T12:00:00+00:00 2024-06-26T16:35:11+00:00 [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[12],"tags":[],"_links":{"self":[{"href":"http:\/\/suimy.me\/index.php\/wp-json\/wp\/v2\/posts\/1347"}],"collection":[{"href":"http:\/\/suimy.me\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/suimy.me\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/suimy.me\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"http:\/\/suimy.me\/index.php\/wp-json\/wp\/v2\/comments?post=1347"}],"version-history":[{"count":1,"href":"http:\/\/suimy.me\/index.php\/wp-json\/wp\/v2\/posts\/1347\/revisions"}],"predecessor-version":[{"id":1348,"href":"http:\/\/suimy.me\/index.php\/wp-json\/wp\/v2\/posts\/1347\/revisions\/1348"}],"wp:attachment":[{"href":"http:\/\/suimy.me\/index.php\/wp-json\/wp\/v2\/media?parent=1347"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/suimy.me\/index.php\/wp-json\/wp\/v2\/categories?post=1347"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/suimy.me\/index.php\/wp-json\/wp\/v2\/tags?post=1347"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}