<?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 Dipesh Manandhar on Medium]]></title>
        <description><![CDATA[Stories by Dipesh Manandhar on Medium]]></description>
        <link>https://medium.com/@dipeshmanandhar33?source=rss-2e13f6cd310b------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*NzqEW98rkwE0Bohq4htoOA.png</url>
            <title>Stories by Dipesh Manandhar on Medium</title>
            <link>https://medium.com/@dipeshmanandhar33?source=rss-2e13f6cd310b------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 01:01:30 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@dipeshmanandhar33/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[How I Audit a Client’s Website Before That Crucial First Meeting]]></title>
            <link>https://medium.com/design-bootcamp/how-i-audit-a-clients-website-before-that-crucial-first-meeting-1aa8d7235964?source=rss-2e13f6cd310b------2</link>
            <guid isPermaLink="false">https://medium.com/p/1aa8d7235964</guid>
            <category><![CDATA[redesign]]></category>
            <category><![CDATA[audit]]></category>
            <category><![CDATA[ui]]></category>
            <dc:creator><![CDATA[Dipesh Manandhar]]></dc:creator>
            <pubDate>Sun, 19 Jul 2026 19:40:33 GMT</pubDate>
            <atom:updated>2026-07-19T19:40:33.040Z</atom:updated>
            <content:encoded><![CDATA[<p>I still remember the anxiety of my early discovery calls. I’d secured a meeting with a potential client, but I had no creative brief, no Google Analytics access, and limited time to prepare. Showing up empty-handed risked making me look unprepared, but after allot of trail and error i was to create a pre-meeting auditing system that could change the entire dynamic of that first conversation.</p><p>This phase isn’t about doing a month’s worth of work for free; it’s about replacing assumptions with hard evidence. It builds immediate credibility by showing the client I already understand their digital footprint and, more importantly, their users’ pain points.</p><p>To be clear: a pre-meeting audit is <em>not</em> a deep-dive, technical overhaul. It’s a diagnostic health check to identify surface-level usability issues, performance bottlenecks, and accessibility barriers.</p><p>Here is the exact process I follow to land clients, and I hope it helps you refine your own workflow.</p><h3>Start with a Normal Visitor Walkthrough</h3><p>Before I activate a single technical crawler, I perform a cognitive walkthrough. Tapping into basic behavioural psychology, I want to experience the site exactly how a first-time visitor does and relying on fast, instinctual thinking rather than deep analysis. Does the interface make the next step obvious?</p><p>This manual method is fast, cost-efficient, and helps me find glaring usability flaws like hidden system statuses or heavy technical jargon. At this stage, I only record the obvious.</p><p><strong>What I evaluate manually:</strong></p><ul><li><strong>The 5-Second Test:</strong> Does the homepage immediately explain what this company does?</li><li><strong>Navigation &amp; Architecture:</strong> Is the menu a logical map, or a dumping ground for internal links?</li><li><strong>Calls to Action (CTAs):</strong> Are the primary actions obvious, or are they fighting for attention with secondary links?</li><li><strong>System Feedback:</strong> If I submit a form or add something to a cart, is there clear visual feedback (a spinner, a success toast)?</li><li><strong>Visual Consistency:</strong> Do the typography, spacing, and button styles remain consistent as I click deeper into the site?</li></ul><p>My Pro Tips</p><ul><li>I always use a temporary email service to test their newsletter signup or account-registration flows. It lets me audit their onboarding friction safely without bloating my own personal inbox.</li><li>I use <a href="https://www.uxcheck.co/"><strong><em>UX Check</em></strong></a><strong><em> </em></strong>to quickly list out UI/UX errors and start my design documentation.</li><li>I fire up <a href="https://chromewebstore.google.com/detail/visbug/cdockenadnadldjbbgcallicgledbeoc"><strong>Visbug</strong></a>, to visually test and manipulate the page’s design directly in the browser.</li></ul><h3>Map Out the Website’s Size and Structure</h3><p>It might sound simple but knowing the scale of the project will always be your advantage and you can establish a fair trade.</p><p><strong>What to look for:</strong></p><ul><li>Approximate number of indexed pages.</li><li>Deeply nested or “orphaned” pages that users can’t easily find.</li><li>Broken links and dead ends.</li></ul><p><strong>The Tools to Use:</strong></p><ul><li><a href="https://www.screamingfrog.co.uk/seo-spider/"><strong>Screaming Frog SEO Spider</strong></a><strong>:</strong> This is my heavyweight champion for site crawling. The free tier covers up to 500 URLs, which is perfect for quickly extracting a page list, spotting missing H1 tags, and catching 404 errors.</li><li><a href="https://chromewebstore.google.com/detail/check-my-links/aajoalonednamcpodaeocebfgldhcpbe"><strong>Check My Links</strong></a><strong>: </strong>A faster, lighter alternative for single pages. It highlights broken links in red, perfect for checking high-traffic landing pages on the fly.</li><li><a href="https://chromewebstore.google.com/detail/website-page-counter-for/hiblffephcchplieefnofjdfkchdbldh"><strong>Website Page Counter for SEO</strong></a>: A simple Chrome extension I use to get a quick page count.</li><li><a href="https://www.deadlinkchecker.com/"><strong>Dead Link Checker</strong></a>: A handy tool for webmasters, SEO professionals and agencies used to Sitemap extractors and Identify and correct broken links on their site.</li><li><a href="https://validator.w3.org/"><strong>Markup Validation Service</strong></a>: A free online tool that checks your <strong>HTML code</strong> for errors and ensures it follows official web standards.</li></ul><p><strong>My Pro Tip:</strong> Master <strong>Chrome DevTools</strong>. It is invaluable for inspecting the DOM, monitoring network requests, debugging layout issues, and identifying missing image alt text on the spot.</p><h3>Identify the technology stack</h3><p>Understanding what powers the website helps you uncover technical limitations, maintenance risks, and opportunities for future scalability. It also tells you if the site is weighed down by unnecessary third-party scripts.</p><p><strong>What to look for:</strong></p><ul><li><strong>CMS &amp; Frameworks:</strong> Are they using WordPress, Shopify, Webflow, or a custom stack (React, Vue, Tailwind)? This dictates development complexity.</li><li><strong>Hosting &amp; Infrastructure:</strong> Where does it live (Vercel, AWS, Cloudflare), and do they use a CDN?</li><li><strong>Performance Overhead:</strong> Are they weighed down by excessive, outdated third-party marketing trackers, or have they modernized with leaner, privacy-focused analytics like Plausible?</li><li><strong>Scalability:</strong> Can this stack support their future features without a complete rebuild?</li><li><strong>Third-Party Integrations:</strong> Identify analytics, CRM, marketing automation, live chat, payment gateways, booking systems, or embedded services that may affect performance or maintenance.</li></ul><p><strong>The Tools to Use:</strong></p><ul><li><a href="https://chromewebstore.google.com/detail/wappalyzer-technology-pro/gppongmhjkpfnbhagpmjfkannfbllamg?hl=en"><strong>Wappalyzer</strong></a><strong>:</strong> This browser extension instantly reveals a site’s DNA (alternatives like <a href="https://builtwith.com/"><strong>builtwith</strong></a><strong> </strong>or <a href="https://chromewebstore.google.com/detail/whatruns/cmkdbmfndkfgebldhnkbfhlneefdaaip"><strong>WhatRuns</strong></a><strong> </strong>works too<strong>)</strong></li></ul><p><strong>My Pro Tip:</strong> Focus on whether the technology stack matches the website’s needs. An overly complex setup can lead to slower performance, higher maintenance costs, and scalability challenges.</p><h3>Test responsive behaviour</h3><p>With over <strong>60% of web traffic</strong> coming from mobile, responsive design is non-negotiable. But preset device sizes in design software often hide the real issues.</p><p>Instead of just checking “Desktop” and “Mobile,” gradually drag your browser window from wide to narrow. Watch how the layout reflows. Find the exact breakpoints where text wraps awkwardly, cards break out of their containers, or horizontal scrolling accidentally triggers.</p><p><strong>What I evaluate:</strong></p><ul><li>Does the design collapse gracefully when dimensions change?</li><li>Are touch targets actually usable? (I always check if buttons meet the 48x48px mobile standard).</li><li>Do complex data tables ruin the mobile experience?</li></ul><p><strong>The Tools to Use:</strong></p><ul><li><strong>Chrome DevTools:</strong> Perfect for simulating specific devices and emulating touch interactions.</li><li><a href="https://polypane.app/"><strong>Polypane</strong></a><strong>:</strong> When I need to go deep, this tool lets me view a website across multiple viewports simultaneously.</li><li><a href="https://chromewebstore.google.com/detail/mobile-simulator-responsi/ckejmhbmlajgoklhgbapkiccekfoccmk?hl=en"><strong>Mobile Simulator</strong></a><strong>:</strong> A quick Chrome extension for previewing common device sizes.</li></ul><p><strong>My Pro tips</strong>: Browser emulators are useful for initial testing, but always validate your website on real mobile devices before launch, as they more accurately reflect touch interactions, browser behavior, and performance.</p><h3>Run a basic accessibility check</h3><p>Digital accessibility isn’t just a legal requirement; it’s foundational inclusive design. While automated tools are great, they don’t catch everything. Because a full accessibility audit takes days, I stick to the essentials for a pre-meeting check.</p><h4>What I look for:</h4><ul><li>Keyboard navigation and visible focus states.</li><li>Correct heading hierarchy (H1–H6).</li><li>Readability at 200% zoom and on different screen sizes.</li><li>Descriptive link text and meaningful image alt text.</li><li>Sufficient colour contrast for text and UI elements.</li></ul><p><strong>The Tools to Use:</strong></p><ul><li><a href="https://www.accessibilitychecker.org/"><strong>AccessibilityChecker.org</strong></a><strong>:</strong> Great for regional compliance, as it allows you to check against specific country standards. There are many other alternatives, chose one you like.</li><li><a href="https://chromewebstore.google.com/detail/stark-accessibility-check/fkfaapnmfippddbeemjjbclenphooipm"><strong>Stark Accessibility Checker</strong></a><strong>:</strong> Detects common issues such as colour contrast failures, missing labels, and ARIA errors. Alternative: <a href="https://chromewebstore.google.com/detail/axe-devtools-web-accessib/lhdoppojpmngadmnindnejefpokejbdd?hl=en"><strong>axe DevTools</strong></a></li><li><a href="https://chromewebstore.google.com/detail/taba11y-tab-order-accessi/aocppmckdocdjkphmofnklcjhdidgmga?hl=en"><strong>Taba11y</strong></a><strong>:</strong> I love this tool because it visually draws the keyboard tab order on the screen, immediately highlighting navigation traps.</li><li><a href="https://chromewebstore.google.com/detail/funkify-disability-simula/ojcijjdchelkddboickefhnbdpeajdjg?hl=en"><strong>Funkify</strong></a>: An eye-opening simulator that helps me experience the site through the lens of users with various disabilities.</li></ul><p><strong>My Pro Tip:</strong> Put your mouse away. I navigate the site using only Tab, Shift+Tab, Enter, and Esc. You’d be amazed at the usability traps you uncover when you rely strictly on a keyboard.</p><h3>Performance, SEO, and Trust Signals</h3><p>Slow pages destroy engagement. If a site takes longer than 2.5 seconds to load its main content (Largest Contentful Paint), users will bounce.</p><h4>What I look for:</h4><ul><li><strong>Performance:</strong> Slow loading pages, large unoptimised images, render-blocking resources, and poor Core Web Vitals.</li><li><strong>SEO basics:</strong> Proper heading hierarchy, page titles, meta descriptions, XML sitemap, and structured data.</li><li><strong>Metadata:</strong> If you share the website link on Slack or Twitter, does it pull a nice image and description (Open Graph data), or does it look broken.</li><li><strong>Security:</strong> HTTPS, valid SSL certificate, and essential HTTP security headers.</li><li><strong>Indexing:</strong> Outdated, duplicate, or unintended pages appearing in search results.</li></ul><p><strong>The Tools to Use for performance:</strong></p><ul><li><a href="https://chromewebstore.google.com/detail/lighthouse/blipmdconlkpinefehnmjammfjpmpbjk?hl=en"><strong>Lighthouse</strong></a><strong>:</strong> Audits performance, accessibility, SEO, and best practices. Aletnatively use <a href="https://www.webpagetest.org/"><strong>WebPageTest</strong></a> to tests website speed across different devices, locations, and network conditions.</li><li><a href="https://webspeedtest.cloudinary.com/"><strong>Cloudinary Website Speed Test</strong></a>: Cloudinary is useful when image delivery is the suspected problem. It should not be treated as a complete website-speed audit.</li></ul><p><strong>The Tools to Use for SEO</strong></p><ul><li><a href="https://chromewebstore.google.com/detail/blue-button-the-webpage-x/ahbcoeleapdfhmlnjglbiaddohfncace"><strong>Blue Button</strong></a>: One click reveals the page’s title, meta description, heading structure, and Open Graph tags. Alternatives: <a href="https://chromewebstore.google.com/detail/page-audit/gmnbmbjdcjbbmdbjlmdkjddmjmpdciod"><strong>Page Audit</strong></a> and <a href="https://chromewebstore.google.com/detail/detailed-seo-extension/pfjdepjjfjjahkjfpkcgfmfhmnakjfba"><strong>Detailed SEO Extension</strong></a></li><li><a href="https://www.seobility.net/en/seocheck/"><strong>Seobility</strong></a>: It is an SEO auditing and website monitoring tool that helps identify technical issues such as broken links, duplicate content, crawl errors, and on-page optimisation problems. It also provides keyword tracking, backlink monitoring, and actionable recommendations to improve a website’s search engine performance. Alternative: <a href="https://www.seotesteronline.com/"><strong>SEO Tester Online</strong></a></li><li><a href="https://search.google.com/test/rich-results"><strong>Google Rich Results Test</strong></a>: It is a free, official web developer tool used to validate structured data (schema markup) on a website. It verifies if a webpage’s markup qualifies for rich snippets, such as carousels, review stars, recipe details, or product prices, which enhance visibility beyond standard text links.</li><li><a href="https://search.google.com/search-console/welcome?utm_source=about-page"><strong>Google Search Console</strong></a>: Monitors indexing, search performance, and crawl issues.</li><li><strong>Google Site Search (</strong><strong>site:clientdomain.com):</strong> Type this directly into Google. It provides a rough view of what pages are indexed. You might uncover old staging sites, messy PDF uploads, or obsolete content the client forgot about.</li></ul><p><strong>The Tools to Use for Security:</strong></p><ul><li><a href="https://securityheaders.com//"><strong>Security Headers</strong></a><strong>:</strong> Run the URL through this site to check for basic HTTP security headers. You aren’t doing a full vulnerability assessment, but spotting missing security basics is a great conversation starter for enterprise clients.</li><li><a href="https://www.ssllabs.com/ssltest/"><strong>SSL Labs</strong></a>: Analyses SSL/TLS configuration and certificate health.</li></ul><p><strong>My Pro Tip:</strong> Don’t judge performance by homepage speed alone. Test key pages such as landing pages, blogs, product pages, and contact forms to identify real-world bottlenecks.</p><h3>Organize My Findings for the Meeting</h3><p>By this point, I usually have dozens of issues jotted down. The biggest mistake you can make is dumping a 50-page technical report on the client’s desk during a discovery call. It overwhelms them and kills the collaborative energy.</p><p>Instead, I compile my findings into a structured, digestible format. I group the issues into clear themes like “Navigation Friction,” “Performance Bottlenecks,” or “Mobile Usability.”</p><p>Then, I assign a simple 4-point severity score to each issue:</p><ol><li><strong>Cosmetic:</strong> Visual inconsistencies that don’t stop the user.</li><li><strong>Minor:</strong> Annoyances that cause slight friction.</li><li><strong>Major:</strong> Issues that significantly hinder the user experience.</li><li><strong>Critical:</strong> Immediate conversion killers (e.g., broken forms, keyboard traps, un-clickable text elements masquerading as buttons).</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KAgZBYks019a72mzTa5faQ.png" /></figure><h3>Conclusion</h3><p>My ultimate goal in that first discovery call is to guide the conversation, not dictate it. By using the data gathered from this rapid audit, I can ask informed, highly specific questions. When you can pinpoint exactly where their users are struggling before they even hand you a brief, you instantly stop being just another freelancer and you start being a strategic partner.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1aa8d7235964" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/how-i-audit-a-clients-website-before-that-crucial-first-meeting-1aa8d7235964">How I Audit a Client’s Website Before That Crucial First Meeting</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[Beyond the Dashboard: Mitigating Goodhart’s Law in UX Metrics]]></title>
            <link>https://medium.com/design-bootcamp/beyond-the-dashboard-mitigating-goodharts-law-in-ux-metrics-6bae80b3af8a?source=rss-2e13f6cd310b------2</link>
            <guid isPermaLink="false">https://medium.com/p/6bae80b3af8a</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[data-analytics]]></category>
            <dc:creator><![CDATA[Dipesh Manandhar]]></dc:creator>
            <pubDate>Tue, 05 May 2026 21:23:56 GMT</pubDate>
            <atom:updated>2026-05-05T21:23:56.327Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6dk-eItnqB0Fz1R04r9ltQ.png" /></figure><p>We have all been there: a project dashboard is glowing <strong>“Green”</strong> with healthy-looking metrics, yet the team feels a deep sense of unease because the actual user experience is failing. This phenomenon is often called the <strong>“Watermelon Effect”.</strong></p><p>It looks great on the outside, but it is “Red” (failing) on the inside. This disconnect is a classic symptom of <strong>Goodhart’s Law</strong>, a principle that every designer and researcher must master to build truly effective products.</p><h3><strong>What is Goodhart’s Law?</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PpQIqMjO7zDcSFZM5vtyYQ.png" /></figure><p>Originally formulated by economist <strong>Charles Goodhart</strong> in 1975, it suggests that any statistical regularity will collapse once pressure is placed upon it for control purposes.</p><p>In the world of design and product development, this means that as soon as we reward a team for hitting a specific number, we provide a powerful incentive to <strong>manipulate that measurement</strong>. Often, people are not being malicious; they are simply “gaming” the system to meet the demands placed upon them.</p><p>A famous historical example is the “<strong>Cobra Effect</strong>” in colonial India:</p><blockquote>Officials offered a bounty for cobra skins to reduce the snake population, only for entrepreneurial citizens to start breeding cobras specifically for their skins. When the fraud was discovered and the bounty ended, the breeders released the snakes, actually increasing the population.</blockquote><h3><strong>How Goodhart’s Law Sabotages UX</strong></h3><p>In digital design, Goodhart’s Law manifests when we rely on “proxy” variables rather than direct outcomes. We often measure <strong>Measures of Performance (MOPs)</strong>, the “how well we do a task” because they are easy to track, rather than <strong>Measures of Effectiveness (MOEs), </strong>the “is this actually working?”.</p><p>Here are a few ways this “<strong>target fixation</strong>” can ruin a user experience:</p><ul><li><strong>The “Time on Page” Trap:</strong> We might set a target to increase time on a page, assuming it indicates high engagement. However, a high “time on page” might actually signal that your navigation is confusing or your content is hard to digest.</li><li><strong>The “Task Completion” Illusion:</strong> If a team is pressured to increase task completion rates, they might break a complex job into multiple tiny, over-simplified steps. While the “rate” goes up, the user may feel frustrated by a fragmented, “hand-holding” experience.</li><li><strong>Shallow Testing Targets:</strong> In development, setting an arbitrary goal like 90% “code coverage” can lead engineers to write shallow tests that execute code without actually verifying the logic. The metric is met, but the product remains buggy.</li></ul><h3><strong>The Danger of the “North Star”</strong></h3><p>Many organisations fall into the trap of the “North Star” metric, a single number intended to guide everything. While alignment is good, complexity is the reality of human systems. Any single metric only captures a tiny part of the whole picture.</p><p>When we point a “<strong>metric flashlight</strong>” at only one corner of the room, we might think that area looks fine, but we miss the “<strong>monster</strong>” hiding in the dark corners i.e. the unhappy stakeholders, the declining quality, or the long-term sustainability risks.</p><h3><strong>How to Mitigate Measurement Manipulation</strong></h3><p>To avoid the perverse outcomes of Goodhart’s Law, we need to shift our focus from hitting targets to understanding impact.</p><ol><li><strong>Never Rely on a Single Number</strong> Mature teams use <strong>multiple metrics</strong> to create a balanced perspective. If you are measuring conversion rates, you should also be measuring churn or support ticket volume to ensure those conversions are actually high-quality.\</li><li><strong>Pair “Big Data” with “Thick Data”</strong> Quantitative data (Big Data) tells you <strong>what</strong> is happening, but it rarely tells you <strong>why</strong>. Qualitative research (Thick Data) such as user interviews, diary studies, and direct observation provides the context needed to interpret the numbers correctly. For example, if “<strong>time on task</strong>” is high, qualitative research can tell you if users are enjoying the depth of the tool or if they are simply lost.</li><li><strong>Use the Scientific Method</strong> Instead of just harvesting whatever data happens to be available in your analytics tool, use the scientific method. Start with a testable hypothesis, design an experiment to generate the specific data needed to answer a question, and verify the results. This ensures the <strong>data is tailored to the question</strong>, rather than the question being limited by the data.</li><li><strong>Expect Adaptation</strong> Assume that people (and AI agents) will try to game the system. Be prepared to <strong>adjust your metrics</strong> or add new ones as the environment changes. Don’t get so caught up in how people are <em>supposed</em> to interact with the system that you overlook how they are <em>actually</em> interacting with it.</li></ol><h3><strong>Conclusion</strong></h3><p>Building a great user experience is about more than just moving a needle on a dashboard. True graphical and design excellence consists of complex ideas communicated with clarity and precision, not “<strong>KPI Theater</strong>” intended to appease leadership.</p><p>To be effective, we must have the courage to look at a “Green” dashboard and ask: “I don’t believe this; where is the red?”. By prioritising <strong>effectiveness over performance</strong> and <strong>truth over targets</strong>, we can build products that don’t just look good in reports but truly resonate with users.</p><h3>Reference:</h3><ul><li><a href="https://www.cna.org/reports/2022/09/Goodharts-Law-Recognizing-Mitigating-Manipulation-Measures-in-Analysis.pdf"><strong>Goodhart’s Law: Recognizing and Mitigating the<br>Manipulation of Measures in Analysis</strong></a><strong> </strong>— CNA</li><li><a href="https://www.industriallogic.com/blog/metrics-mislead/"><strong>Metrics mislead!</strong></a> — Industrial Logic</li><li><a href="https://machine-learning-made-simple.medium.com/goodharts-law-why-everything-eventually-goes-wrong-44e66ca0c6bd"><strong>Goodhart’s Law: Why Everything eventually goes wrong</strong></a> — Medium</li><li><a href="https://www.projectmanagement.com/blog-post/79302/the-watermelon-effect--when-project-metrics-hide-disaster"><strong>The Watermelon Effect: When Project Metrics Hide Disaster </strong></a>— Project Management.com</li><li><a href="https://uxmag.com/articles/8-key-metrics-to-measure-and-analyze-in-ux-research"><strong>8 Key Metrics to Measure and Analyze in UX Research</strong></a> — UX Magazine</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6bae80b3af8a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/beyond-the-dashboard-mitigating-goodharts-law-in-ux-metrics-6bae80b3af8a">Beyond the Dashboard: Mitigating Goodhart’s Law in UX Metrics</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[Beyond the Chatbot: Why Starting With “Why” Builds a Brand That Actually Lasts]]></title>
            <link>https://medium.com/design-bootcamp/beyond-the-chatbot-why-starting-with-why-builds-a-brand-that-actually-lasts-bf1af1bc3e06?source=rss-2e13f6cd310b------2</link>
            <guid isPermaLink="false">https://medium.com/p/bf1af1bc3e06</guid>
            <category><![CDATA[start-with-why]]></category>
            <category><![CDATA[branding]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[brands]]></category>
            <dc:creator><![CDATA[Dipesh Manandhar]]></dc:creator>
            <pubDate>Mon, 16 Mar 2026 09:16:40 GMT</pubDate>
            <atom:updated>2026-03-16T09:16:40.124Z</atom:updated>
            <content:encoded><![CDATA[<p>In today’s digital world, launching a website has never been easier. With AI tools, you can generate a site, copy information and publish it. But this convenience is creating a new problem: <strong>a sea of sameness</strong>. Thousands of websites, apps, and brands now look and sound almost identical because they ignoring the most important question:</p><blockquote><strong>Why does this brand exist in the first place?</strong></blockquote><p>As a result, countless sites, apps, and brands blend into beige corporate noise, sounding identical because they obsess over the “<strong>what</strong>” (the product) and the “<strong>how</strong>” (the design, the features), while completely ignoring the “<strong>why</strong>”, the purpose that makes people care.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KQJFbI6dVpi26LJRvh6JCg.png" /></figure><blockquote>As leadership expert <strong>Simon Sinek</strong> famously argued, truly inspiring organisations communicate from the inside out. While most companies can explain what they do, few can articulate their <strong>“Why”, </strong>the belief or purpose that drives their existence beyond mere profit.</blockquote><p>This distinction is not merely a marketing exercise; it is rooted in biology. While chatbots and rational data communicate with the <strong>neocortex</strong> (the part of the brain responsible for language and analytical thought). The <strong>“Why”</strong> speaks directly to the <strong>limbic brain</strong>, which is part of our anatomy that controls all human behavior and decision-making, including the feelings of <strong>trust and loyalty</strong> that turn a casual user into a brand advocate.</p><p>To survive in this automated landscape, brands must reclaim their <strong>verbal identity</strong>, their unique voice and tone. In the absence of a speaker’s face or body language in digital environments, word choice, syntax and punctuation must carry the entire burden of establishing credibility.</p><p>This blog is for the next generation of brand builders who want to go beyond simply using chatbots for efficiency. It’s about creating a brand voice that feels purposeful and genuine and one that makes people feel welcomed, understood, and valued every time they interact with it.</p><h3><strong>The Foundation</strong></h3><p>A brand isn’t just a logo or colour palette. It is a <strong>living system</strong> whom you interact with. Without clarity at its core, every marketing campaign of the brand feels hollow and every customer interaction feels transactional. To build a brand that lasts, you must operationalise your identity through the <strong>Golden Circle framework</strong>: starting with your “Why” defining your “How” and executing your “What”.</p><h4><strong>Why (Vision &amp; Purpose)</strong></h4><p>The “Why” is your brand’s <strong>North Star</strong>. It is the bold, inspiring purpose that explains why your company exists beyond making a profit. Biologically, this level of communication speaks directly to the <strong>limbic brain</strong>, the part of our anatomy that processes feelings like trust and loyalty and is responsible for all human decision-making.</p><ul><li><strong>Vision Statement:</strong> This is your concept of the future. It focuses on “tomorrow” and what the organisation aspires to become in the next <strong>5</strong> to<strong> 10 years</strong>. A compelling vision should be a “dream” that inspires the workforce to grow beyond their current capabilities.</li><li><strong>Real-World Examples:</strong> <strong>Patagonia</strong> famously declares, “We’re in business to save our home planet”. Similarly, <strong>Apple’s</strong> vision involves a commitment to making the best products on earth and leaving the world better than they found it. They clam to <strong>Think Different</strong> and <strong>To challenge the status Quo</strong>. These aren’t just slogans; they are <strong>rallying cries</strong> that move people toward a shared cause.</li></ul><h4><strong>How (Values)</strong></h4><p>If your “Why” is the destination, your <strong>Values</strong> are the guiding principles that dictate <strong>how</strong> you will get there. They act as your brand’s <strong>Behavioural DNA</strong>, defining the non-negotiable beliefs that shape every internal decision and external interaction.</p><p>To make your values easy to understand, focus on these two levels:</p><ul><li><strong>Core vs. Permission-to-Play:</strong> Most companies list “honesty” or “integrity,” but these are merely <strong>permission-to-play values. </strong>Which is the baseline expectations for any business. True <strong>Core Values</strong> are distinctive; they define what makes your culture unique. For example, while many airlines value safety, <strong>Southwest Airlines</strong> differentiates itself with a “Warrior Spirit”.</li><li><strong>The Internal/External Link:</strong> A brand is essentially your <strong>culture turned outward</strong>. As <strong>Slack</strong> defines it, “Our culture turned inward creates our product; our culture turned outward creates our brand”. When employees live values like <strong>Empathy, Craftsmanship, and Playfulness</strong> internally, the brand naturally shows up as the “ideal colleague” to the customer.</li></ul><h4><strong>What (Mission)</strong></h4><p>The “What” grounds your lofty vision in <strong>today’s reality</strong>. While the vision is the destination, the <strong>Mission</strong> is the vehicle and the route being traveled right now. It defines what you do, whom you serve, and how you deliver unique value in the present tense.</p><ul><li><strong>Action-Oriented Direction:</strong> A strong mission provides employees with direction and customers with clarity. It should be <strong>concrete and concise</strong>, focusing on the human problem your business solves today.</li><li><strong>Real-World Examples:</strong> <strong>Google’s </strong>mission is “to organise the world’s information and make it universally accessible and useful”. <strong>Tesla’s</strong> mission is “to accelerate the world’s transition to sustainable energy”. These statements provide a practical roadmap for every tactical decision.</li></ul><p>Starting with these foundational elements ensures <strong>brand alignment</strong>, which is the harmony between your internal strategy and external execution. Without these agreed-upon principles, maintaining a consistent brand is like trying to solve a <strong>Rubik’s cube while the colours are constantly changing</strong>.</p><h3><strong>The Human Connection</strong></h3><p>Once your <strong>Why, How, and What</strong> are strategically aligned, the next layer of branding is your <strong>verbal identity</strong>. Voice and tone are how your brand’s purpose becomes tangible, transforming strategy into a lived experience for your audience. They shape how people feel when they interact with your brand, building emotional resonance and trust over time.</p><h4><strong>Brand Voice</strong></h4><p>Your brand voice is the consistent expression of your brand’s personality across every touchpoint, from high-traffic landing pages to 404 error messages. If the “Why” is your brand’s soul, the voice is its <strong>DNA</strong>. Consistency in voice is critical because it builds <strong>familiarity.</strong> Customers come to recognise your brand as they would an “old friend” who is reliable and constant.</p><ul><li><strong>Anchoring in Mission:</strong> A successful brand voice is never manufactured; it is <strong>anchored in your mission statement</strong>. For instance, a mission focused on empowerment naturally leads to a voice that is helpful and clear.</li><li><strong>Real-World Example:</strong> <strong>Slack</strong> exemplifies this by positioning itself as the “ideal colleague”, someone who is smart, humble, and collaborative, but never dominates the conversation or wastes the user’s time.</li></ul><h4><strong>Brand Tone</strong></h4><p>While voice remains static, <strong>brand tone is dynamic</strong>, acting as the “mood ring” of your identity. It refers to the specific emotional inflection or attitude used depending on the <strong>context, audience, and medium</strong>. You are still the same person, but you wouldn’t use the same tone at a party that you would in a crisis.</p><ul><li><strong>Contextual Nuance:</strong> Effective tone mapping ensures your communication is appropriate for the user’s <strong>psychological state</strong>. A success message is a moment to celebrate, while an error message requires clear, concise direction over humour.</li><li><strong>The Four Dimensions:</strong> Analysts often calibrate tone using four spectrums: <strong>Funny vs. Serious, Formal vs. Casual, Respectful vs. Irreverent, and Enthusiastic vs. Matter-of-Fact</strong>.</li></ul><p>To understand it in in-depth go to <a href="https://www.nngroup.com/articles/tone-of-voice-dimensions/"><strong><em>The Four Dimensions of Tone of Voice</em></strong></a> from NN/G.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*_WJXnjspHuCofMXS.jpg" /></figure><p><strong>Real-World Examples</strong></p><ul><li><strong>Mailchimp:</strong> They speak as an <strong>experienced and compassionate business partner</strong>. Their voice guidelines specify they are “translators” who demystify complex marketing jargon into plainspoken, genuine language. While their general tone is witty and encouraging, they shift to a <strong>transparent and apologetic tone</strong> during outages, ensuring clarity remains the priority.</li><li><strong>Apple:</strong> Their voice is <strong>minimalist, bold, and confident</strong>. They use short, punchy verbiage to signal innovation and quality without appearing arrogant. By using personal pronouns like “us,” they add humanistic warmth to their sophisticated messaging.</li><li><strong>Patagonia:</strong> Their voice is rooted in <strong>authentic, urgent activism</strong>. They prioritise their environmental mission over direct sales, using a Direct and Fact-based tone that reflects their commitment to saving the planet.</li></ul><h3>Why This Matters Now?</h3><p>The data proves that this human-centric approach is a financial imperative:</p><ul><li><strong>The Loyalty Factor:</strong> <a href="https://asana.com/resources/brand-voice"><strong>86% of consumers</strong></a> identify authenticity as a key factor in deciding which brands to support.</li><li><strong>The Consistency Dividend:</strong> Companies with a strong, unified brand presentation across all channels can see <a href="https://www.qualtrics.com/articles/strategy-research/brand-voice/"><strong>revenue increases of up to 33%</strong></a>.</li><li><strong>The Performance Gap:</strong> Strategic clarity regarding brand identity accounts for as much as <strong>31% of the performance gap</strong> between top-tier and mediocre organisations.</li></ul><h3>Conclusion</h3><p>Launching a website is a tactical milestone, but building a brand that endures is a <strong>strategic imperative</strong> that requires the courage to start with “Why”. In todays context, technological disruption is constant, your mission, vision, and values serve as the primary <strong>navigational instruments</strong> for long-term survival. Without this foundation, a website is merely a collection of pixels; with it, your brand becomes a <strong>living system of meaning</strong>.</p><p>Consistency across every touchpoint, from social media to customer support builds familiarity, making your brand feel like a <strong>reliable “old friend”</strong> whose responses are predictable and trustworthy. While AI can generate copy at scale, it often fails at <strong>empathetic communication</strong> and lacks the <strong>emotional core</strong> that makes a brand human. In a world drowning in automated content, the <strong>human “Why”</strong> is your ultimate competitive advantage. Start there and every other element will naturally follow as a coherent reflection of your brand’s soul.</p><h3>Reference:</h3><ul><li><strong>Slack Brand Guidelines (September 2020): </strong>https://a.slack-edge.com/4d5bb/marketing/img/media-kit/slack_brand_guidelines_september2020.pdf</li><li><strong>8 Brand Voice Guidelines Examples for Impactful Messaging:</strong> https://www.smashcreate.com/uncategorized/brand-voice-guidelines-examples/</li><li><strong>A Comprehensive Guide on Determining Brand Voice and Tone:</strong> https://gorevity.com/determining-brand-voice-and-tone-a-comprehensive-guide/</li><li><strong>Brand Guidelines Templates and Examples for Marketing (Slack):</strong> https://slack.com/templates/brand-guidelines-hub</li><li><strong>Brand Voice vs Tone: What It Is, Why It Matters:</strong> https://www.columnfivemedia.com/brand-voice-vs-tone/</li><li><strong>Brand Voice: Definition, Benefits &amp; Tips to Create One:</strong> https://www.qualtrics.com/articles/strategy-research/brand-voice/</li><li><strong>Defining Your Tone of Voice: Full Step-by-step Guide &amp; Exercise Templates:</strong> https://valchanova.me/brand-tone-of-voice-guide-exercises-templates/</li><li><strong>Golden Circle model: Sinek’s theory value proposition:</strong> https://simonsinek.com/golden-circle/</li><li><strong>How to Create a Unique Social Media Brand Voice:</strong> https://www.respeecher.com/blog/how-to-create-a-unique-social-media-brand-voice</li><li><strong>How to develop your customer service voice and tone:</strong> https://www.zendesk.com/blog/right-tone-of-voice/</li><li><strong>How to differentiate vision, mission and value statements:</strong> https://uk.indeed.com/career-advice/career-development/vision-mission-value-statements</li><li><strong>Just How Purpose-Driven Is Your Organizational Culture?:</strong> https://www.gallup.com/workplace/356093/purpose-driven-organizational-culture.aspx</li><li><strong>Maintaining Brand Voice at Scale: A Guide for Marketing Leaders:</strong> https://www.siegemedia.com/strategy/maintaining-brand-voice-at-scale</li><li><strong>Mastering Brand Voice and Tone for Dynamic Marketing:</strong> https://www.stellarcontent.com/blog/content-marketing/mastering-brand-voice-and-tone-for-dynamic-marketing/</li><li><strong>Microsoft Style Guide: Brand Voice:</strong> https://learn.microsoft.com/en-us/style-guide/brand-voice-above-all-simple-human</li><li><strong>The Art of Voice and Tone in UX Writing:</strong> https://uxwritinghub.com/ux-writing-voice-and-tone/</li><li><strong>The Ultimate Brand Voice Worksheet: 12 Exercises to Define Your Voice:</strong> https://www.ameliepollak.com/blog/the-ultimate-brand-voice-worksheet-12-exercises-to-define-your-voice</li><li><strong>The Ultimate Primer On Brand Voice Guidelines (and How to Create Yours!):</strong> https://amplihigher.com/the-ultimate-primer-on-brand-voice-guidelines-and-how-to-create-yours/</li><li><strong>Voice and Tone | Mailchimp Content Style Guide:</strong> https://styleguide.mailchimp.com/voice-and-tone/</li><li><strong>What is a Brand Voice? Plus, 7 Tips to Develop One:</strong> https://asana.com/resources/brand-voice</li><li><strong>UNICEF Jordan Brand Book:</strong> https://www.unicef.org/jordan/media/7166/file/ANNEX_G_-_Brand_book_V3.1.pdf</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bf1af1bc3e06" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/beyond-the-chatbot-why-starting-with-why-builds-a-brand-that-actually-lasts-bf1af1bc3e06">Beyond the Chatbot: Why Starting With “Why” Builds a Brand That Actually Lasts</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[The Silent Storyteller: Why Alt Text Matters for Designers and Developers]]></title>
            <link>https://medium.com/design-bootcamp/the-silent-storyteller-why-alt-text-matters-for-designers-and-developers-b1adceccba51?source=rss-2e13f6cd310b------2</link>
            <guid isPermaLink="false">https://medium.com/p/b1adceccba51</guid>
            <category><![CDATA[alt-text]]></category>
            <category><![CDATA[accessibility]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Dipesh Manandhar]]></dc:creator>
            <pubDate>Tue, 02 Sep 2025 11:17:29 GMT</pubDate>
            <atom:updated>2025-09-02T11:17:29.153Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="A women writing alt text for the images on her laptop a speech bubble that says ‘alt text,’." src="https://cdn-images-1.medium.com/max/1024/1*UQkMs9uGroBdK6EUROexhg.png" /><figcaption>Illustration symbolising how alt text helps designers and developers make content more accessible.</figcaption></figure><p>Alt text, short for “alternative text”, is a fundamental component of the user experience, not merely an afterthought or a compliance checkbox. It acts as a bridge between visual design and human experience, ensuring that every image contributes to a meaningful and inclusive digital journey. For designers and developers, mastering alt text is a small habit that can have a massive impact, making products usable for everyone, future-proofing designs, and improving search visibility.</p><h3>Importance &amp; Why it Matters</h3><p>Alt text is rooted in three primary objectives</p><ul><li><strong>Accessibility (&amp; It’s The Right Thing To Do)</strong>: This is the number one reason for implementing alt text. It is a primary pillar of web accessibility <strong>(WCAG)</strong>, allowing screen reader software to describe images to users with visual impairments. Without descriptive alt text, images become voids of information, making web content difficult or impossible to understand for screen reader users. Approximately <strong>1.3 billion</strong> people globally live with some form of vision impairment, and a substantial majority (83%) prefer websites that meet accessibility standards. Providing clear, concise descriptions ensures that every visitor, regardless of ability, can perceive the full content of a webpage.</li><li><strong>SEO (Search Engine Optimisation)</strong>: Search engines like Google cannot “see” images; they read the alt text to understand what an image contains. Properly descriptive alt text dramatically improves the chances of content appearing in image search results, driving organic traffic. It helps search engines understand the overall subject matter of a web page, contributing to higher page rankings in standard search results. <strong>The most effective strategy for SEO is to write descriptive alt text for the human user</strong>, which naturally includes relevant, contextual keywords that algorithms are designed to understand.</li><li><strong>User Experience for Everyone</strong>: Alt text enhances general usability by providing context when images fail to load due to issues like slow internet, broken links, or server problems. In these moments, alt text appears in place of the image, preventing a confusing user experience for <em>everyone</em>. It also supports cognitive accessibility by clarifying complex visuals.</li></ul><h3>Types of Images</h3><p>Not all images require the same type of alt text. Classifying images correctly is crucial and requires clear communication between design and development. The industry standard categorizes images into Decorative, Functional, Informative, and Complex. Below is the image from <a href="https://www.nngroup.com/articles/write-alt-text/">nn/g gourp</a> that sums it all.</p><figure><img alt="Decorative images shouldn’t have alt text. Functional images should communicate the action they afford. Informative images with long alt text should use a long description or alter the page copy." src="https://cdn-images-1.medium.com/max/1024/0*TNdfozg_vCmngRqy.png" /></figure><h4>1. <strong>Decorative Images: The Empty Alt (alt=&quot;&quot;)</strong></h4><p>These are purely visual embellishments that do not convey any meaningful content or information already provided by the surrounding text. Examples include stylistic dividers, redundant decorative icons, or purely aesthetic background elements.</p><figure><img alt="Screenshot of a website section form W3C showing an image of a line with accompanying HTML code describing what can be written." src="https://cdn-images-1.medium.com/max/1024/1*6t_baRq5cbJ6YvLHQK9cNw.png" /></figure><ul><li><strong>The Designer&#39;s Job</strong>: Annotate these images as &quot;decorative&quot; in the design handoff. A good question to ask is: <strong>&quot;If this image disappeared, would the user miss critical information?&quot;</strong> If not, it&#39;s<strong> decorative.</strong></li><li><strong>The Developer&#39;s Job</strong>: Implement this as alt=&quot;&quot; (an empty alt attribute). This instructs screen readers to <strong>skip over the image entirely</strong>, which is the desired behavior. It&#39;s critical that the attribute is present but empty; simply omitting it can lead to screen readers reading the image&#39;s file name, which is confusing.</li></ul><h4>2. <strong>Functional Images: Describe the Action</strong></h4><p>These images act as interactive elements, such as buttons, links, or icons that trigger an action.</p><figure><img alt="Screenshot of a website section form W3C showing print icon with accompanying HTML alt tag “Print this page”." src="https://cdn-images-1.medium.com/max/1024/1*FNMqtMEIprTTTOrlA7OhIQ.png" /></figure><ul><li><strong>The Designer&#39;s Job</strong>: Focus on the <em>action</em> the image performs, not its visual appearance.</li><li><strong>The Developer&#39;s Job</strong>: The alt text should describe the <strong>function or destination</strong>. For example, a magnifying glass icon for search should have alt=&quot;Search&quot;, not alt=&quot;Magnifying glass&quot;. A company logo that links to the homepage should be alt=&quot;Go to Homepage&quot; or alt=&quot;Acme Corp Home&quot;, not just alt=&quot;Logo&quot;. For SVG icons, ensure they have proper aria-labels or are wrapped in buttons with appropriate alt text.</li></ul><h4>3. <strong>Informative/Content Images: Tell The Story</strong></h4><p>These images convey important information, such as photos, illustrations, graphs, charts, or memes. Like the image below, take from <a href="https://www.nngroup.com/articles/write-alt-text/">nngorup</a>.</p><figure><img alt="Treadmill Folding Electric Treadmill Bluetooth Voice Control Exercise Treadmill for Home Office Speed Range of 0.5–7.5 mph” Alt tage from Wallmart" src="https://cdn-images-1.medium.com/max/1024/0*dXrxjqWbKfBaFtFs" /></figure><ul><li><strong>The Designer&#39;s Job</strong>: Provide context and suggest the key takeaway or story the image needs to tell. Imagine describing the image over the phone to someone who cannot see it.</li><li><strong>The Developer&#39;s Job</strong>: Write concise, descriptive text that captures the essence and meaning of the image within the context of the surrounding content. For example, a image might be alt=&quot;Nutrition labels have four sections: serving information, calories, nutrients, and percentage of daily values, for which 5% or less is low, 20% or more is high&quot;, and a photo on a blog alt=&quot;A senior woman laughing while learning to use a tablet in a community library.&quot;. If an image contains embedded text, the alt text must transcribe that text verbatim unless it&#39;s repeated elsewhere on the page.</li></ul><p><strong>For Complex Images:</strong> These images, such as charts, graphs, flowcharts, or infographics, contain a significant amount of data that cannot be effectively conveyed in a short alt text.</p><figure><img alt="Multiple Spacecraft launcher data table covering from engine to thruster" src="https://cdn-images-1.medium.com/max/1024/0*wftfFTcGVOQ2vNzt.png" /><figcaption>Data about engine, cycle types, propellent and thrust for multiple space craft like a Atlas V, Delta IV Heavy, Vulcan, Falcon 9, and Falcon Heavy.</figcaption></figure><ul><li><strong>Guideline</strong>: Provide a concise alt attribute that identifies the image (e.g., alt=&quot;Mutliple spacecraft launcher data table coving from engine to thruster&quot;) and then provide a full textual description or data table in the body text of the document, adjacent to the image. For very large datasets, a short alt text can link to an external page or downloadable file with full details. Advanced cases may use the aria-labelledby attribute to reference a block of text elsewhere on the page for a long description. Capation can also help to explain more about the image.</li></ul><h3>Guidelines for Writing Great Alt Text</h3><p>Writing effective alt text requires a delicate balance of detail and conciseness.</p><ul><li><strong>Be Specific and Contextual</strong>: The same image can require different alt text depending on the page and its context. For example, a picture of a black sneaker on a blog post about “2024 Fashion Trends” would have different alt text than the same sneaker on an e-commerce product page.</li><li><strong>Keep it Concise</strong>: While there’s no strict technical limit, aim for <strong>125–200 characters</strong> for clarity and focus. Some sources suggest under 125 characters for optimal screen reader efficiency, while others allow for more flexibility, emphasizing context over strict counts. Overly long descriptions can interrupt the flow of reading for screen reader users or be truncated. Test your alt text by reading it aloud; if it takes more than 5 seconds, it’s likely too long.</li><li><strong>Avoid Redundancy</strong>: If the information conveyed by an image is already present in the surrounding body text or an adjacent caption, an empty alt attribute (alt=&quot;&quot;) is appropriate to prevent repetition by screen readers.</li><li><strong>Do Not Start with “Image of…” or “Picture of…”</strong>: Screen readers already announce the presence of an image, so including these phrases is redundant and creates a poor user experience.</li><li><strong>Keywords, Not Keyword Stuffing</strong>: Use natural language that includes relevant keywords for SEO, but <strong>always write for a human first</strong>. Keyword stuffing (e.g., alt=&quot;Shoe, running shoe, buy shoe, best shoe&quot;) is a harmful practice that violates both accessibility principles and search engine guidelines, potentially leading to penalties.</li><li><strong>Skip Decorative Language</strong>: Avoid subjective fluff like “stunning photo of a beautiful sunset.” Stick to facts that convey the same information a sighted user would get.</li><li><strong>Include Text in the Image</strong>: If the image contains important text (like a logo with words or a screenshot), repeat that text verbatim in the alt text.</li><li><strong>Use Correct Grammar and Punctuation</strong>: Capitalise the first word and end with a period if it’s a full sentence; this makes screen reader output clearer.</li><li><strong>Do Not Make Assumptions</strong>: When describing people in images, avoid making assumptions about race, gender, or motivation unless it is directly relevant to the content.</li></ul><h3>Collaboration between Developer and Designer</h3><p>Alt text is a shared responsibility that begins with the designer and culminates in the developer’s careful implementation.</p><p><strong>The Designer’s Role</strong>: Designers should treat alt text as a core part of the design process, not an afterthought. This involves:</p><ul><li><strong>Annotating images</strong>: Clearly marking each image as “decorative,” “functional,” or “informative” in design mockups and handoffs.</li><li><strong>Providing the text</strong>: Writing specific alt text for all informative and functional images using realistic content instead of placeholder text.</li><li><strong>Adding context</strong>: Including notes on the function of interactive images or a link to a longer description for complex visuals, transferring the design intent to the technical team.</li></ul><p><strong>The Developer’s Role</strong>: Developers are the gatekeepers who must correctly implement the alt attribute in the HTML code based on the designer’s specifications. This requires understanding the purpose of alt text and communicating with designers if the provided alt text is redundant or unclear in the context of the final product.</p><p><strong>Handoff Blueprint</strong>: Integrating alt text early in design workflows prevents costly retrofits and enhances inclusivity.</p><p><strong>Testing</strong>: Implement alt tags consistently and validate them during QA. Test with screen readers like <strong>VoiceOver (Mac/iOS)</strong> and <strong>NVDA (Windows)</strong> to simulate the user experience. Automated accessibility checkers (e.g., WAVE or Lighthouse) can also help identify issues. Add alt text reviews to design critique and code review checklists.</p><h3>Captions</h3><p><strong>Alt text is an <em>alternative</em> to the image</strong> for non-visual users or when the image is unavailable, but <strong>Captions <em>supplement</em> the image</strong> for all users, providing visible text that adds context, commentary, or a longer description. Alongside descriptive filenames, <strong>using descriptive captions when possible</strong> is advised as it can contribute to a better understanding of the content by search engines and improve visibility.</p><blockquote>Captions are read 300% more often than body copy.</blockquote><p>One crucial interplay between captions and alt text is the avoidance of redundancy. If the information an image conveys is <strong>already present in an adjacent caption</strong> or the surrounding body text, then the alt text for that image may be made empty (alt=&quot;&quot;). This prevents screen readers from repeating information, which can be frustrating for users.</p><p>For complex images like charts, graphs, flowcharts, or infographics that contain significant data, a short alt text often isn’t sufficient to convey all the necessary information. In these scenarios, captions or other adjacent text in the document can be used to provide the full textual description or a data table. The alt text would then provide a concise overview (e.g., alt=&quot;Bar chart of sales trends; see details below&quot;) while the caption or body text provides the comprehensive detail.</p><p>When images fail to load due to slow connections or broken links, alt text appears in place of the image, providing context. If a descriptive caption is also present, it can further support the user’s understanding, contributing to a resilient user experience for everyone.</p><h3>Conclusion</h3><p>Treating alt text with care is a mark of a mature, empathetic product team. It is a tiny detail that makes a massive impact, fostering inclusivity, quality, and a superior user experience. By adopting a human-first mentality and embracing a shared taxonomy for image types, every image becomes an opportunity to build products that are not only more beautiful and functional but also more open, inclusive, and resilient.</p><p>If you want to learn to write a helpful alt text visit: <a href="https://developers.google.com/tech-writing/accessibility/self-study/write-alt-text#write-useful-text">Developer Writing</a></p><h3><strong>Key Citations</strong></h3><p><strong>Harvard University</strong>: <a href="https://accessibility.huit.harvard.edu/describe-content-images">Write helpful Alt Text to describe images</a></p><p><strong>NNgroup</strong>: <a href="https://www.nngroup.com/articles/write-alt-text/">Alt Text: What to Write</a></p><p><strong>Material Design System</strong>: <a href="https://m3.material.io/foundations/content-design/alt-text">Alt text</a></p><p><strong>W3C Web Accessibility Initiative (WAI)</strong>: <a href="https://www.w3.org/WAI/tutorials/images/">Images Tutorial</a></p><p><strong>Developer Google</strong>: <a href="https://developers.google.com/tech-writing/accessibility/self-study/write-alt-text">Write helpful alt text</a></p><p><strong>Siteimprove</strong>: <a href="https://help.siteimprove.com/support/solutions/articles/80000863904-accessibility-image-alt-text-best-practices">Accessibility: Image Alt text best practices</a></p><p><strong>WebAIM</strong>: <a href="https://webaim.org/techniques/alttext/">Alternative Text</a></p><p><strong>Accessibility</strong>: <a href="https://accessibility.psu.edu/images/imageshtml/">Image ALT Tag Tips for HTML</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b1adceccba51" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/the-silent-storyteller-why-alt-text-matters-for-designers-and-developers-b1adceccba51">The Silent Storyteller: Why Alt Text Matters for Designers and Developers</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[Designing Legally Compliant and User-Friendly Terms & Conditions & Privacy Policies]]></title>
            <link>https://medium.com/design-bootcamp/designing-legally-compliant-and-user-friendly-terms-conditions-privacy-policies-610680576b10?source=rss-2e13f6cd310b------2</link>
            <guid isPermaLink="false">https://medium.com/p/610680576b10</guid>
            <category><![CDATA[data-privacy]]></category>
            <category><![CDATA[terms-and-conditions]]></category>
            <category><![CDATA[privacy]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[legal]]></category>
            <dc:creator><![CDATA[Dipesh Manandhar]]></dc:creator>
            <pubDate>Tue, 05 Aug 2025 08:56:22 GMT</pubDate>
            <atom:updated>2025-08-05T08:56:22.230Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="Illustration showing the relationship between legal documents (Terms &amp; Conditions and Privacy Policies) and user experience design, highlighting the balance between compliance requirements and user-friendly presentation." src="https://cdn-images-1.medium.com/max/1024/1*GnQXOyyuju-ecW0UMS37Jg.jpeg" /><figcaption>Balancing Legal Compliance and User Experience: The Art of Designing Accessible Terms &amp; Conditions and Privacy Policies</figcaption></figure><p>Let’s be honest, most of us click “<strong>I agree</strong>” without giving a second thought of what we are agreeing on. As UX designers, we strive for intuitive flows and seamless experiences, yet often overlook one of the most critical touch points: the dreaded <strong>Terms &amp; Conditions</strong> (T&amp;Cs) and <strong>Privacy Policies</strong>. While these documents might look like legal checkboxes, they are <strong>pivotal for building user trust</strong>, <strong>ensuring compliance</strong>, and <strong>creating a transparent user experience</strong>. For anyone building digital products, understanding and designing these crucial legal safeguards with a user-centric approach is no longer just good practice — it’s essential.</p><h3>What Are Terms &amp; Conditions and Privacy Policies?</h3><p>Think of your digital product’s legal documents as its foundational rulebook.</p><p><strong>Terms &amp; Conditions (T&amp;C): </strong>Also known as <strong>Terms of Service</strong> or <strong>Terms of Use</strong>, these are the <strong>rules for using your service</strong> and <strong>act as a contract between you</strong>, <strong>the service provider</strong>, and <strong>your users</strong>. T&amp;Cs outline user account rules, intellectual property, payment terms, cancellation procedures, and dispute resolution. In essence, the T&amp;C “protects the website or app’s rights” and sets user expectations.</p><p><strong>Privacy Policy:</strong> This document specifically explains <strong>how you collect, use, store, and protect personal data</strong>. It discloses what data is gathered, why it’s needed, how it’s used or shared, and what rights users have regarding their data (e.g., to access or delete it). Crucially, a Privacy Policy “protects the user’s rights” regarding their data.</p><h3>Why Clear Policies Matter for UX and Trust?</h3><p>While policy pages might not be users’ favourite content, they are <strong>crucial for fostering trust</strong>.</p><ul><li><strong>Building Trust and Transparency:</strong> Opaque or confusing policies <strong>erode user trust</strong>, making users feel a company cares more about liability than its customers. Conversely, <strong>well-organised, plain-language policies reassure users</strong> that you are transparent about their data and rights, building brand credibility and loyalty. When users feel informed and respected, they are more willing to engage deeply with your product.</li><li><strong>Improving User Experience:</strong> A poorly designed policy creates frustration and a negative perception of your product. <strong>Clear, friendly policies help build trust</strong> and reduce support inquiries by preemptively answering questions.</li><li><strong>Ensuring Informed Consent:</strong> Users can only give genuine consent if they understand what they are agreeing to. Well-designed policies empower users to make informed decisions about using your services and sharing their data.</li><li><strong>Reducing Legal Risk:</strong> While legal teams ensure core compliance, a user-friendly presentation can help prevent misunderstandings that could lead to disputes or legal issues.</li></ul><h3>When Are These Policies Absolutely Necessary?</h3><p>If your site or app involves user accounts, data entry, or commerce, you need clear T&amp;C and Privacy Policies.</p><ul><li><strong>Privacy Policies are legally required in many regions whenever you collect personal data</strong>. This includes names, email addresses, IP addresses, cookies, browsing history, or payment information. Laws like the <strong>EU’s GDPR</strong>, California’s <strong>CCPA/CPRA</strong>, Canada’s <strong>PIPEDA</strong>, and Brazil’s <strong>LGPD</strong> mandate specific disclosures and rights. Even if you don’t collect data, platforms like the Apple App Store may require a privacy policy.</li><li><strong>Terms &amp; Conditions are not usually legally mandated, but are highly recommended</strong> and often expected. They are essential if your service involves user accounts, user-generated content, fees, e-commerce, or liability considerations.</li></ul><p><strong>In practice, it’s always recommended to provide both</strong>. If your digital product interacts with users in any meaningful way, you likely need these policies.</p><h3>Principles for Clear and Compliant Design</h3><p>Crafting policies that are both legally sound and user-friendly requires a user-centric approach.</p><h4>1. Use Plain Language and Summaries</h4><ul><li><strong>Avoid dense legalese</strong>. Studies show users distrust “vague or complex” language.</li><li><strong>Write in plain language</strong> wherever possible, using short sentences (15–20 words max) and active voice.</li><li>Use concrete examples (e.g., “<strong>We collect your email to send order confirmations</strong>”) instead of abstract phrases.</li></ul><h4>2. Structure for Readability and Navigation</h4><p>Break content into bite-sized chunks.</p><ul><li>Use <strong>clear headings and subheadings</strong> liberally (in sentence case, not ALL CAPS).</li><li>Employ <strong>bullet points for key clauses, obligations, rights, and options</strong>.</li><li>Include a <strong>functional table of contents</strong> at the top with links to each section, so users can jump directly to their questions.</li><li>Leave plenty of white space, use at least <strong>14pt font</strong> (preferably 16px for body text and letter spacing must not be less than 0%), and bold headings.</li><li>Consider <strong>progressive disclosure</strong>, showing an overview and letting users click to expand subsections or detailed legal language in collapsible panels.</li></ul><h4>3. Design for Accessibility</h4><p>Ensure your policies are accessible to all users, including those with disabilities.</p><ul><li>Follow basic accessibility guidelines (WCAG): ensure text meets <strong>contrast standards</strong> and is resizable.</li><li>Use <strong>legible fonts and responsive layouts</strong> for mobile devices.</li><li>Make content <strong>structurally accessible</strong> with proper HTML headings (H2/H3), lists, and <strong>landmarks</strong> for screen readers.</li><li>Provide <strong>meaningful link text</strong> (e.g., “Learn more about data sharing” instead of “click here”).</li><li>Test your policy pages with tools like <strong>WAVE</strong> or <strong>Axe</strong>.</li></ul><h4>4. Include Key Legal and UX Components</h4><p>Your policies must cover essential elements for legal compliance and user-friendliness.</p><p><strong>What you must have in your Privacy Policy?</strong></p><ul><li><strong>Scope and Effective Date:</strong> Who the policy applies to and when it’s effective/last updated.</li><li><strong>Who’s Responsible:</strong> Identify your company or website owner.</li><li><strong>Data Collected:</strong> Be explicit about <em>what</em> personal information you collect (e.g., names, emails, usage data, cookies) and <em>how</em> (e.g., forms, third-parties).</li><li><strong>Purpose of Use:</strong> Explain <em>why</em> each data type is used (e.g., “We use your email to send order confirmations and updates”).</li><li><strong>Data Sharing:</strong> Disclose if and with whom data is shared (e.g., partners, analytics, advertisers). If you <em>do not</em> share, state this clearly.</li><li><strong>Data Analytics</strong>: Disclose the use of data analytics (like google analytics, Microsoft Clarity or Hotjar) in the policy section as well as in the footer section of your websites</li><li><strong>User Rights:</strong> Detail users’ rights (e.g., to access, correct, delete data, or opt-out of sales) and how to exercise them.</li><li><strong>Retention and Deletion:</strong> How long data is kept and how users can request deletion.</li><li><strong>Cookies/Tracking:</strong> Explain use of cookies or trackers (can be a separate Cookie Policy).</li><li><strong>Children’s Privacy:</strong> If applicable, state if your service is age-restricted or COPPA-compliant.</li><li><strong>Contact Info:</strong> Provide an email or address for privacy questions.</li><li><strong>Policy Updates:</strong> Explain how users will be notified of changes (e.g., email, on next login). Include a change-log or “last updated” note.</li><li>Example: <a href="https://www.facebook.com/terms/">Meta</a>, <a href="https://www.spotify.com/np-en/legal/privacy-policy/">Spotify</a>, <a href="https://slack.com/intl/en-gb/trust/privacy/privacy-policy">Slack</a> and <a href="https://www.dropbox.com/privacy">Dropbox</a></li></ul><p><strong>What you must have in your Terms &amp; Conditions?</strong></p><ul><li><strong>Introduction/Acceptance of Terms:</strong> Explain what the agreement is and that continuing to use the service means accepting terms.</li><li><strong>Privacy Policy Link:</strong> Embed a link to your Privacy Policy.</li><li><strong>User Obligations/Rules:</strong> Clearly list allowed and forbidden behavior (e.g., no spamming, no hate content).</li><li><strong>Account Termination:</strong> Explain how and why accounts can be suspended or deleted.</li><li><strong>Intellectual Property:</strong> State your ownership of the service, content, and trademarks, and what users can/can’t do with them.</li><li><strong>Payment/Fees (if any):</strong> Describe pricing, subscription terms, refund policy, and what happens on late payment.</li><li><strong>Disclaimers &amp; Liability:</strong> Include standard disclaimers (e.g., “AS IS” service, no warranties) and limits on your liability.</li><li><strong>Governing Law &amp; Disputes:</strong> Which laws govern the agreement and how disputes will be handled (e.g., arbitration or court).</li><li><strong>Contact Info:</strong> Provide a way to contact support or legal questions.</li><li>Example: <a href="https://www.canva.com/policies/terms-of-use/">Canva</a>, <a href="https://www.youtube.com/t/terms">Youtube</a>, <a href="https://www.notion.so/notion/Terms-and-Privacy-28ffdd083dc3473e9c2da6ec011b58ac">Notion</a> and <a href="https://www.airbnb.com/help/article/2908">Airbnb</a></li></ul><h4>5. Align with Industry Standards and Country-Specific Laws</h4><p>Your policies must reflect applicable laws.</p><ul><li><strong>GDPR (EU):</strong> Demands transparency and grants rights (access, rectification, deletion, portability). Article 12 requires <em>clear</em> communication of privacy information. <br><strong>Link</strong>: <a href="https://eur-lex.europa.eu/eli/reg/2016/679/oj">GDPR (EUR-Lex)</a></li><li><strong>CCPA/CPRA (California):</strong> Gives Californians rights to know, opt-out, and delete their data, requiring disclosure of data categories and uses, and annual updates. <br><strong>Link</strong>: <a href="https://oag.ca.gov/privacy/ccpa">California Office of the Attorney General — CCPA</a><br><strong>Link (Text of CPRA)</strong>: <a href="https://www.oag.ca.gov/system/files/initiatives/pdfs/19-0021A1%20(Consumer%20Privacy%20-%20Version%203)_1.pdf">Consumer Privacy — Version 3</a></li><li><strong>PIPEDA (Canada):</strong> Emphasises openness and clear statement of practices. To private-sector organizations across Canada handling personal information in the course of commercial activity.<br><strong>Link</strong>: <a href="https://www.priv.gc.ca/en/privacy-topics/privacy-laws-in-canada/the-personal-information-protection-and-electronic-documents-act-pipeda/">Office of the Privacy Commissioner of Canada — PIPEDA</a></li><li><strong>Australia — Privacy Act 1988</strong>: 13 principles covering collection, use, disclosure, data quality, access, and correction.<br>Link: <a href="https://www.legislation.gov.au/C2024A00128/latest">Privacy and Other Legislation Amendment Act 2024</a>, <a href="https://www.legislation.gov.au/C2004A03712/latest/versions">Privacy Act 1988</a><br>Link: <a href="https://www.oaic.gov.au/__data/assets/pdf_file/0030/40989/app-guidelines-combined-December-2022.pdf">Australian Privacy Principles Guidelines</a></li><li><strong>Adapt to Country-Specific Laws:</strong> Many countries have their own privacy laws (e.g., Brazil’s LGPD, India’s PDPB). If your product has a global reach, you might need to tailor policies or provide region-specific addendums.</li></ul><h3>Examples of Good and Bad Practices</h3><h4>Good Practices</h4><ul><li><strong>Explicit Consent (Clickwrap):</strong> Use <strong>clickwrap</strong> for T&amp;C acceptance, requiring users to check “I Agree” at registration, purchase, or installation. This improves enforceability.</li><li><strong>Placement:</strong> Put a Privacy Policy and T&amp;C <strong>in your footer or settings</strong> where users expect to find them. For apps, include links in the App Store/Google Play listing and within the app.</li><li><strong>Clear Language:</strong> Examples like Canva’s Privacy Policy use a friendly, approachable tone without legalese. Instead of “The data controller will process electronic mail addresses for transactional correspondence,” say, “<strong>We use your email to send transaction updates</strong>”.</li><li><strong>Layout:</strong> Clear headings, bullet lists, and embedded links. Google’s or Mozilla’s policies break text up, use simple language, and put summaries at the top. Pinterest’s T&amp;C use clear sections for easy access.</li><li><strong>Transparency &amp; Version Control:</strong> Including a “Last Updated” date, as Canva does and use a versioning system (e.g., Git) to track policy changes.</li><li><strong>Notification of Updates:</strong> Policies must evolve. So update it on certain intervals. A banner saying “Privacy Policy updated” with a summary and an accept button must be added after every update is provided to users.</li><li><strong>Collaborate with Legal Teams:</strong> Legal expertise is crucial for accuracy and compliance. Work closely with your legal department throughout the design process. Also, conduct usability testing with target users to identify areas of confusion.</li></ul><h4>Bad Practices</h4><ul><li><strong>Hidden Policies:</strong> Burying policies in obscure site sections reduces trust.</li><li><strong>Dense Text:</strong> A single, unbroken wall of text spanning multiple pages. Forever 21’s policy was criticised for lacking summaries and using large text blocks.</li><li><strong>All-Caps:</strong> Policies written entirely in all-caps feel like “yelling”.</li><li><strong>Silent Updates:</strong> Updating policies without user notification.</li><li><strong>Overly Complex Language:</strong> Policies that require legal expertise to understand alienate users.</li></ul><h3>Tools and Resources</h3><p>While there isn’t a single tool to design perfect legal documents, some resources can assist</p><ul><li><strong>Termly, Iubenda, OneTrust, PrivacyPolicies &amp; Cookiebot:</strong> These platforms offer templates and generators for privacy policies and terms and conditions, helping you cover essential legal bases. Remember to customise them to your specific needs.</li><li><strong>PlainLanguage.gov:</strong> Provides guidelines and resources for writing in plain language.</li><li><strong>Readability Score Tools (e.g., Hemingway Editor):</strong> These tools can help you assess the readability of your text.</li></ul><h3>Conclusion</h3><p>Designing effective <strong>Terms &amp; Conditions</strong> and <strong>Privacy Policies</strong> isn’t a one-time task. As your product evolves and legal landscapes change, these documents will need to be reviewed and updated. This not only helps you stay compliant (avoiding hefty fines — GDPR penalties can be millions) but also <strong>builds trust</strong>. When users feel informed and respected, they’re more likely to stick around and recommend your service. In UX terms, your policy pages should be as carefully crafted as any other part of the experience — after all, transparency is a core pillar of good design.</p><p>Start with templates, learn from examples and always consult legal experts to ensure compliance. Your users will thank you for making the fine print feel less like a chore.</p><h3><strong>Reference links</strong></h3><p><a href="https://www.nngroup.com/articles/privacy-policies-terms-use-pages/#:~:text=Policy%20pages%20may%20not%20feel,the%20wellbeing%20of%20its%20customers">Privacy Policies and Terms of Use: 5 Common Mistakes</a> — nngroup</p><p><a href="https://www.termsfeed.com/blog/privacy-policies-vs-terms-conditions/#:~:text=A%20Terms%20and%20Conditions%20agreement,website%20or%20a%20mobile%2Fdesktop%20app">Privacy Policies vs. Terms &amp; Conditions</a> — termsfeed</p><p><a href="https://www.iubenda.com/en/help/132171-sample-terms-of-service-template#:~:text=,Your%20contact%20information">Terms of Service Template for your Site</a> — iubenda</p><p><a href="https://termly.io/resources/articles/privacy-policy-vs-terms-and-conditions/#:~:text=Privacy%20policies%20are%20required%20by,three%20major%20data%20privacy%20regulations">Privacy Policy vs. Terms and Conditions</a> — termly</p><p><a href="https://www.termsfeed.com/blog/privacy-policy-needs-to-include/#:~:text=What%20Information%20is%20Being%20Collected%2C,and%20How">What Does a Privacy Policy Need to Include?</a> — termsfeed</p><p><a href="https://termly.io/resources/articles/data-privacy-web-accessibility-compliance-link/#:~:text=Someone%20providing%20you%20with%20personal,explicitly%20allowing%20you%20to%20do">Data Privacy &amp; Web Accessibility Compliance: What’s The Link?</a> — termly</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=610680576b10" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/designing-legally-compliant-and-user-friendly-terms-conditions-privacy-policies-610680576b10">Designing Legally Compliant and User-Friendly Terms &amp; Conditions &amp; Privacy Policies</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[Beyond the Interface: Why Behavior Shifts and What Designers Can Learn]]></title>
            <link>https://medium.com/design-bootcamp/beyond-the-interface-why-behavior-shifts-and-what-designers-can-learn-0472834df4db?source=rss-2e13f6cd310b------2</link>
            <guid isPermaLink="false">https://medium.com/p/0472834df4db</guid>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[user-behavior]]></category>
            <dc:creator><![CDATA[Dipesh Manandhar]]></dc:creator>
            <pubDate>Sun, 01 Jun 2025 09:21:17 GMT</pubDate>
            <atom:updated>2025-06-01T09:21:17.595Z</atom:updated>
            <content:encoded><![CDATA[<p>Imagine walking into a bustling marketplace versus entering a quiet library. In the marketplace, you’re surrounded by noise, colours, and activity, and your attention is drawn in multiple directions. In the library, the atmosphere is calm, and your focus is on finding specific information or enjoying a quiet read. These different environments evoke different behaviours and expectations from you as a visitor.</p><p>Similarly, when we navigate the digital world, our behavior changes depending on the type of website we’re visiting. On an e-commerce site, we might be leisurely browsing for deals or impulsively adding items to our cart. On a news site, we’re quickly scanning headlines to stay informed. On a job portal, we’re meticulously reviewing job listings and tailoring our applications. Understanding these variations in user behavior is crucial for product designers, as it allows them to craft experiences that resonate with users’ intentions and enhance their overall satisfaction.</p><p>In this article, we’ll explore how user behavior differs across various types of websites. By delving into user types, session durations, revisit patterns, and key insights, we’ll uncover actionable strategies to design user-centric digital products that truly meet the needs of your audience.</p><h3><strong>E-commerce Site</strong></h3><p>E-commerce are <strong>Goal-oriented</strong> or <strong>Exploratory</strong> site. User are either looking to buy a specific item or they are simply browsing for options, deals, trends.</p><h4><strong>Duration per Session</strong></h4><p>Sessions typically last <strong>5–20 minutes</strong> , during which users browse product catalogs, search for deals, compare multiple product, move them shopping carts</p><h4><strong>User Type</strong></h4><p>There are 3 types of general users for e-commerce site according to there repeated visiting site</p><ul><li><strong>Transactional users</strong>: Return only when they need to buy something new.</li><li><strong>Loyal customers</strong>: Visit regularly for deals, wish lists, and price tracking.</li><li><strong>Cart abandoners</strong>: May return within a few days to complete a purchase, especially if nudged by a retargeting ad or email.</li></ul><h4><strong>Key Insights</strong></h4><ul><li>Mobile devices drive over <strong>70%</strong> of traffic <a href="https://www.semrush.com/blog/mobile-vs-desktop-usage/">Mobile vs. Desktop Use and Trends in 2025</a>, but desktop users convert at <strong>1.7 times</strong> higher rates <a href="https://www.smartinsights.com/ecommerce/ecommerce-analytics/ecommerce-conversion-rates/">E-commerce conversion rate benchmarks — 2025 update</a>.</li><li><strong>22% of shoppers</strong> use price comparison tools, and <strong>26% abandon</strong> carts for better prices <a href="https://www.hostinger.com/uk/tutorials/ecommerce-statistics">Ecommerce statistics 2025: key findings and shopping trends [latest research]</a>.</li><li><strong>79% of Amazon shoppers</strong> are influenced by top-rated products, with <strong>70% checking reviews</strong> before buying <a href="https://wisernotify.com/blog/online-review-stats/">77 Shocking Online Review Statistics (New 2025 Data)</a> and <a href="https://www.sciencedirect.com/science/article/abs/pii/S096969892200159X">Measuring the impact of online reviews on consumer purchase decisions — A scale development study.</a></li></ul><h4><strong>Design Implications</strong></h4><ul><li><strong>Mobile-first</strong>: Ensure fast, intuitive mobile experiences to capture most traffic.</li><li><strong>Desktop focus</strong>: Enhance desktop for higher conversions with detailed info and comparisons.</li><li><strong>Price transparency</strong>: Show competitive pricing and integrate price tools to reduce cart abandonment.</li><li><strong>Review prominence</strong>: Display reviews prominently and encourage feedback for trust.</li></ul><h3><strong>News &amp; Media Site</strong></h3><p>News and Media sties are <strong>Information-oriented</strong>. They deliver timely, accurate news to inform users.</p><h4><strong>Duration per Session</strong></h4><p>Sessions typically last <strong>3–10 minutes</strong>, with users engaging in quick reading sessions, scanning headlines or skimming articles, especially on mobile devices.</p><h4><strong>User Type</strong></h4><p>There are 2 types of general users for news media site according to there repeated visiting site.</p><ul><li><strong>Frequent readers</strong>: Return multiple times a day for updates, particularly during peak times like early morning, lunch breaks, and late evening.</li><li><strong>Casual visitors</strong>: Visit a few times a week when specific headlines or social media links pique their interest.</li></ul><h4><strong>Key Insights</strong></h4><ul><li>Social media is a primary news source, with <strong>34.5% of adult social media users</strong> citing reading news stories as a main reason for using social platforms <a href="https://datareportal.com/reports/digital-2025-sub-section-state-of-social">Digital 2025: The State of Social Media</a>.</li><li>Traditional news websites face challenges, with <strong>74% of media leaders worried about declining referral traffic</strong> from search engines and social platforms <a href="https://reutersinstitute.politics.ox.ac.uk/journalism-media-and-technology-trends-and-predictions-2025">Journalism, Media, and Technology Trends and Predictions 2025</a>.</li><li><strong>Young audiences (under 40)</strong> increasingly turn to non-traditional sources like podcasters and YouTubers for personalised, engaging news <a href="https://www.twipemobile.com/what-will-the-news-media-industry-look-like-in-2025/">What Will the News Media Industry Look Like in 2025?</a></li></ul><h4><strong>Design Implications</strong></h4><ul><li><strong>Mobile-first</strong>: Ensure fast, intuitive mobile experiences to capture most traffic.</li><li><strong>Desktop focus</strong>: Enhance desktop for higher conversions with detailed info and comparisons.</li><li><strong>Price transparency</strong>: Show competitive pricing and integrate price tools to reduce cart abandonment.</li><li><strong>Review prominence</strong>: Display reviews prominently and encourage feedback for trust.</li></ul><h3><strong>Job Portal</strong></h3><p>Job portal are primarily <strong>goal-oriented</strong>, where user are seeking employment or applying to jobs.</p><h4><strong>Duration per Session</strong></h4><p>Sessions typically last <strong>15–30 minutes</strong>, during which users browse job listings, update profiles, or apply for jobs, reflecting the focused nature of job searching.</p><h4><strong>User Type</strong></h4><p>There are 3 types of general users for job portal site according to there repeated visiting site.</p><ul><li><strong>Active job seekers</strong>: Return frequently (daily to weekly) for about 1–3 months until hired, driven by urgency and the need to stay updated.</li><li><strong>Passive job seekers</strong>: May revisit every few months to explore opportunities, often triggered by life changes or career curiosity.</li><li><strong>New users</strong>: Spend more time initially setting up their profile and refining search preferences, as they are less familiar with the platform.</li></ul><h4>Key Insights</h4><ul><li><strong>Benefits in Postings</strong>: 61% of postings mention benefits, expected to range between 55%-60% in 2025, most common in low-wage roles <a href="https://www.hiringlab.org/2024/12/10/indeed-2025-us-jobs-and-hiring-trends-report/">Indeed’s 2025 US Jobs &amp; Hiring Trends Report</a>.</li><li><strong>Skills-Based Hiring</strong>: The share of postings requiring a bachelor’s degree fell to 17.6% in October 2024, and experience requirements dropped to 32.6% <a href="https://www.hiringlab.org/2024/12/10/indeed-2025-us-jobs-and-hiring-trends-report/">Indeed’s 2025 US Jobs &amp; Hiring Trends Report</a>.</li><li><strong>Upskilling and Reskilling</strong>: 39% of skill sets will be transformed by 2030, with 50% of workers having completed training <a href="https://www.weforum.org/publications/the-future-of-jobs-report-2025/digest/">The Future of Jobs Report 2025.</a></li></ul><h4>Design Implications</h4><ul><li><strong>Mobile Optimisation</strong>: Ensure job portals are mobile-friendly, as many users access them on mobile devices during commutes or breaks.</li><li><strong>Remote and Hybrid Job Filters</strong>: Provide clear filters for remote and hybrid positions, as these remain in demand.</li><li><strong>AI Assistance</strong>: Incorporate AI tools to help users tailor resumes and cover letters, ensuring ethical use to avoid misuse concerns.</li><li><strong>Notification Systems</strong>: Enhance notification systems (email, SMS, app) to drive re-engagement, especially for active job seekers.</li><li><strong>Upskilling and Reskilling Resources</strong>: Integrate resources or partnerships for upskilling, given the rapid evolution of skills.</li></ul><h3><strong>Streaming Service (Video/Music)</strong></h3><p>Streaming Service sites are <strong>entertainment-oriented. </strong>They provide engaging video/music content for leisure.</p><h4><strong>Duration per Session</strong></h4><ul><li><strong>Music</strong>: Sessions last <strong>20–60 minutes</strong>, often running in the background during other activities.</li><li><strong>Video</strong>: Sessions range from <strong>10–120 minutes</strong>, from short clips to binge-watching entire series.</li></ul><h4><strong>User Type</strong></h4><p>There are 2 types of general users for Streaming Service according to there repeated visiting site.</p><ul><li><strong>Daily/weekly users</strong>: Highly engaged, returning frequently for new content or routines, like regular moviegoers.</li><li><strong>Occasional users</strong>: Visiting when recommended content or new releases spark interest, similar to casually attending a concert.</li></ul><h4>Key Insights</h4><ul><li><strong>Auto-play and recommendations</strong> increase session length by keeping users engaged with seamless content transitions Streaming Media Trends 2025.</li><li><strong>Evening and weekend usage</strong> peaks, with 65% of streaming occurring during these times Nielsen Streaming Report 2025.</li><li><strong>Subscription models</strong> influence engagement, with premium subscribers spending 30% more time than free users <a href="https://explodingtopics.com/blog/video-streaming-stats">Statista Streaming Statistics 2025.</a></li><li><strong>Mobile devices</strong> account for over 60% of streaming traffic, emphasizing the need for mobile-first design <a href="https://explodingtopics.com/blog/mobile-internet-traffic">Mobile Streaming Trends 2025</a>.</li></ul><h4>Design Implications</h4><ul><li><strong>Mobile Optimisation</strong>: Ensure fast, intuitive mobile interfaces to capture the majority of users.</li><li><strong>Personalized Recommendations</strong>: Leverage AI to suggest content based on user preferences, enhancing engagement.</li><li><strong>Seamless Auto-play</strong>: Implement smooth transitions between content to extend session times.</li><li><strong>Subscription Incentives</strong>: Highlight premium features to convert free users to subscribers.</li><li><strong>Content Variety</strong>: Offer diverse formats (short clips, long-form series, playlists) to cater to both user types.</li></ul><h3><strong>Social Media Platform</strong></h3><p>Social media sites are <strong>exploratory </strong>or <strong>Connection-oriented</strong>. Users browse social media for contents, discovering trends or they specific interactions like messaging or following brands. Users are also checking platforms daily for updates, news, and social interactions.</p><h4><strong>Duration per Session</strong></h4><p>Sessions typically last <strong>5–30 minutes</strong>, depending on the user’s intent and content type. Scrolling through short-form videos often leads to shorter, frequent sessions, while engaging in conversations or longer content extends session times.</p><h4><strong>Repeat Visits</strong></h4><p>There are 2 types of general users for social media site according to there repeated visiting site</p><ul><li><strong>Habitual users</strong>: Visit multiple times daily, driven by habits, notifications, or content updates.</li><li><strong>Occasional users</strong>: Visit a few times per week, often triggered by specific interests or social cues.</li></ul><h4>Key Insights<strong>:</strong></h4><ul><li>Short-form videos (e.g., Reels, TikToks) dominate, with US users spending <strong>45.8 minutes daily</strong> on TikTok <a href="https://www.sendible.com/insights/latest-social-media-trends-report">Sendible Social Media Trends</a>.</li><li>Social search is growing, with <strong>90% of marketers</strong> prioritising optimisation for product discovery <a href="https://explodingtopics.com/blog/social-media-trends">Exploding Topics Social Media</a>.</li><li>Users engage with <strong>6.83 platforms monthly</strong>, requiring multi-platform strategies <a href="https://sproutsocial.com/insights/social-media-statistics/">Sprout Social Statistics</a>.</li></ul><h4>Design Implications</h4><ul><li><strong>Mobile Optimization</strong>: Ensure fast load times, intuitive navigation, and responsive design for mobile users, who dominate access.</li><li><strong>Video-Centric Content</strong>: Prioritize short-form video content to capture attention and encourage sharing.</li><li><strong>Personalization through AI</strong>: Use AI to deliver tailored content recommendations, enhancing user experience.</li><li><strong>Social Search Features</strong>: Incorporate search functionalities to help users discover products, brands, and trends.</li><li><strong>Engaging Notifications</strong>: Design relevant, timely notifications to drive re-engagement without overwhelming users.</li><li><strong>Influencer and Community Focus</strong>: Foster communities and collaborate with influencers to build trust and authenticity.</li></ul><h3><strong>SaaS</strong></h3><p>SaaS are primarily <strong>task-oriented</strong> sites. User use Saas for work or businesses or personal projects. They enable users to complete work tasks efficiently.</p><h4><strong>Duration per Session</strong></h4><p>Sessions typically last <strong>10–60 minutes</strong>, depending on task complexity, from quick updates to in-depth project work.</p><h4><strong>Repeat Visits</strong></h4><ul><li><strong>Daily users</strong>: Users who use platforms like <strong>Slack</strong> or <strong>Jira</strong> regularly during there work hours.</li><li><strong>Occasional users</strong>: Users who access tools like accounting software for specific tasks, similar to visiting a workshop for projects.</li></ul><h4>Key Insights</h4><ul><li><strong>Market Growth</strong>: The SaaS industry was valued at over $317 billion in 2024, with projections indicating continued growth in 2025 Vena SaaS Statistics 2025.</li><li><strong>AI and Machine Learning</strong>: AI integration is standard, with tools like Salesforce’s Agentforce automating tasks and providing predictive analytics, with 33% of enterprise apps expected to include agentic AI by 2028 Zylo SaaS Trends 2025.</li><li><strong>Data Security and Privacy</strong>: 65% of customers prioritise robust security due to data breach concerns, requiring advanced measures like zero-trust architecture Userpilot User Behavior Trends 2025.</li><li><strong>Usage-Based Pricing</strong>: This model is gaining traction, with 25% of SaaS companies adopting it for flexibility and cost-effectiveness Zylo SaaS Trends 2025.</li><li><strong>Multi-App Usage</strong>: Large organizations use an average of 447 SaaS apps, necessitating seamless integration SaaS Academy SaaS Statistics 2024.</li></ul><h4>Design Implications</h4><ul><li><strong>AI Integration</strong>: Use AI for personalised onboarding, feature recommendations, and predictive analytics to enhance user satisfaction.</li><li><strong>Security Focus</strong>: Implement advanced security measures, like zero-trust architecture, and transparent privacy policies to build trust.</li><li><strong>Flexible Pricing</strong>: Offer usage-based or hybrid pricing models to cater to diverse user needs and budgets.</li><li><strong>Accessibility Compliance</strong>: Ensure UI/UX meets accessibility standards, such as the EU Accessibility Act, to reach all users.</li><li><strong>Integration Capabilities</strong>: Develop APIs for seamless interaction with other SaaS tools, enhancing productivity in multi-app environments.</li><li><strong>Vertical Specialisation</strong>: Tailor solutions for specific industries, like healthcare or construction, to meet unique needs.</li><li><strong>Voice and Conversational Interfaces</strong>: Implement voice-activated commands or chatbots for easier interaction, especially for mobile users.</li></ul><p>Understanding user behavior is the foundation of exceptional product design. From the <strong>goal-oriented or exploratory</strong> shoppers on e-commerce platforms to the <strong>task-oriented</strong> professionals using SaaS tools, each website type — E-commerce, News &amp; Media, Job Portals, Streaming Services, Social Media, and SaaS — serves distinct user needs and intents. By analyzing session durations, revisit patterns, and key trends, designers can craft experiences that resonate with users in 2025.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=0472834df4db" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/beyond-the-interface-why-behavior-shifts-and-what-designers-can-learn-0472834df4db">Beyond the Interface: Why Behavior Shifts and What Designers Can Learn</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[Redesigning backend developer portfolio: A Case Study]]></title>
            <link>https://medium.com/design-bootcamp/redesigning-backend-developer-portfolio-a-case-study-663f4a1ba437?source=rss-2e13f6cd310b------2</link>
            <guid isPermaLink="false">https://medium.com/p/663f4a1ba437</guid>
            <category><![CDATA[backend]]></category>
            <category><![CDATA[research]]></category>
            <category><![CDATA[case-study]]></category>
            <category><![CDATA[developer]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Dipesh Manandhar]]></dc:creator>
            <pubDate>Tue, 04 Feb 2025 10:25:53 GMT</pubDate>
            <atom:updated>2025-02-04T15:12:08.456Z</atom:updated>
            <content:encoded><![CDATA[<h4>Even though it was a major redesign in UX, we kept UI as close to the original as possible because of it’s uniqueness and popularity.</h4><p>As a budding UI/UX designer, one of my earliest projects turned into a remarkable milestone in my career. A friend, just starting his journey as a backend developer, approached me with a request: create a portfolio website that truly represents the <strong>soul</strong> of a developer. The initial outcome? A portfolio website styled like <strong>VS Code</strong>.</p><p>The design was a hit when I posted it as a case study. But fast forward three years, both of us had grown in our respective careers. My friend needed a redesign because of the user issues feedback that he was getting. So, skilled with my experienced, here is how i redesign a popular website.</p><h3>The Backstory: A VS Code-Inspired Portfolio</h3><p>When I first tackled this project, my design skills were in their infancy. I learned heavily on inspiration from familiar developer tools opting for a layout that mimicked the interface of VS code. I used the technique i learned from <strong>Google UX Design.</strong> Despite being new to the craft, I managed to create something that resonated with the target audience i.e, developers.</p><p><strong>What worked:</strong></p><ul><li>Aesthetic appeal top developers due to its VS code familiarity.</li><li>Early design decisions aligned with basic UX principles.</li><li>Great reception on social platform, with many appreciating the unique theme.</li><li>On a personal note, recognition from people all over the globe.</li></ul><h3>The Turning Point: Why a Redesign Was Necessary</h3><p>Three years later, the cracks in the initial design began to show. While the website had served its purpose initially, usability issues became more apparent as my friend’s career grew. Users struggled to navigate the site effectively, particularly on mobile devices. Armed with new skills and tools, I approached this redesign as a way to correct past mistakes and enhance user experience.</p><h4>Identifying Issues: Data-Driven Insights</h4><p>This time, I started with a <strong>data-driven approach</strong> to identify and address usability problems. Leveraging <strong>Microsoft Clarity</strong>, a behavioural analytics tool, I uncovered critical insights into how users interacted with the portfolio site. Before diving into specific errors, let’s examine the <strong>general stats</strong> of the website:</p><h4>General Stats of the Website</h4><p>Our niche portfolio website attracted <strong>51 visitors</strong> in <strong>16 days</strong>, a reasonable level of traffic. While a 60% scroll depth is generally considered good for portfolio sites, ours performed exceptionally well, reaching an impressive <strong>99.03%</strong>, likely due to its short and concise content that minimized unnecessary scrolling. However, while the ideal active time ranges between <strong>2–5 minutes</strong>, our site averaged only <strong>1.6 minutes</strong>, falling short of this benchmark.</p><figure><img alt="4 different stats of protfolio websites containing sessions, pages per session, scroll depth and active time spent." src="https://cdn-images-1.medium.com/max/1024/1*kj6MwUGHo-1K4M2o4ShLUQ.png" /><figcaption>A Screenshot of Clarity stats about the profolio website</figcaption></figure><h4><strong>Usability Errors and Issues</strong></h4><p><strong>JavaScript errors</strong>: It negatively impacted the aesthetics of the design, creating confusion and interrupting smooth user interaction.</p><p><a href="https://drive.google.com/file/d/1dlrX8wuLs4txB8FMyrrefpThH1049QBW/view?usp=sharing">Saragam Ghimire - Clarity.mp4</a></p><h4><strong>Colour contrast problems</strong></h4><p>Many text elements failed to meet the minimum <strong>colour contrast ratio</strong> required for accessibility. This made content harder to read, especially for users with visual impairments.</p><figure><img alt="Sliktide contrast checker on the left followed by about page on the right, where Sliktide is checking the contrast of text “Full stack Developer” and found it failed the test." src="https://cdn-images-1.medium.com/max/1024/1*-HLImha_KBoGMiAkovEETQ.png" /><figcaption>A screenshot of Sliktide contrast checker on the left and about page on the right, where Sliktide is checking the contrast of text “Full stack Developer” and found it failed the test.</figcaption></figure><h4><strong>Dead clicks and quick backs</strong></h4><p><strong>Dead Clicks:</strong> <strong>40% of users</strong> experienced dead clicks — clicking on non-interactive elements mistakenly thinking they were actionable.</p><ul><li><strong>Example</strong>: Users frequently clicked on the word “developer” and other visually prominent areas, assuming they were clickable.</li></ul><figure><img alt="Heat-map of Home Page of Sagaram Ghimire Portfolio website." src="https://cdn-images-1.medium.com/max/1024/1*xoiUQ1WgsSmfA6YpusWuXA.png" /><figcaption>A screenshot of Home page where heatmap test in being done.</figcaption></figure><p><strong>Quick Backs:</strong> <strong>26.67% of users</strong> quickly returned to the previous page after navigating to a new one, indicating dissatisfaction or confusion.</p><h4><strong>Lack of mobile optimisation</strong></h4><p><strong>51% of users</strong> accessed the site on mobile devices, but the design was entirely desktop-focused. This mismatch led to poor usability for over half the audience.</p><figure><img alt="Screenshot of user that visited from both PC and Mobile" src="https://cdn-images-1.medium.com/max/964/1*W1ImxBJiRL4ZNc3GIAonxA.png" /><figcaption>A screenshot of stats of portfolio website showing user visiting from Mobile and PC</figcaption></figure><p>In the new design, we prioritised a <strong>responsive layout</strong> that adapts seamlessly to <strong>mobile, tablet, and larger desktop screens</strong>, ensuring a consistent and enjoyable experience for all users.</p><h4>Additional Issues</h4><ul><li><strong>Duplicate URLs for the Home Section: </strong>The home section was accessible via two different URLs, which could confuse users and harm SEO.</li><li><strong>Missing Headings and Meta description</strong>: No H1 Tags and meta description or any sort of heading in the page. Issues with different page titles</li><li><strong>Misleading Navigation Icon: </strong>The leftmost navigation tab icon did not align with user expectations, leading to confusion about its purpose.</li><li><strong>Design and Development Gaps: </strong>Adaptation of the design in development has negatively affected the visual appeal and cohesion of the design.</li><li><strong>Missing Links</strong>: Pages has very low internal Link as well as no backlink.</li><li><strong>Unwanted page</strong>: Pages like Language, Hobbies, Volunteering and Certificate doesn’t have viewer and didn’t have good content either.</li><li><strong>Performance and SEO rating</strong>: Using Lightroom plugin, i found that performance and SEO matrix were below 76. For SEO, specifically there we no keyword that was driving the traffic to the website. Also, Domain name is to long which affect SEO.</li></ul><figure><img alt="Lightroom plugin results screenshot which contain different parameters being measured" src="https://cdn-images-1.medium.com/max/1024/1*0BOJ_FS6ArhyqfoE6APS0A.png" /><figcaption>A Screenshot of Lightroom plugin and its result being displayed</figcaption></figure><h3>The Redesign Process</h3><p>With a clear understanding of the site’s shortcomings, I embarked on a redesign journey with a more <strong>user-centric approach</strong>. Here’s how I tackled the issues:</p><h4>Research and Empathy: <strong>Gathering user information</strong></h4><p>First steps was to identify who the users are. This was properly defined when we designed it the first time along with user persona. So, i will just recap it</p><ul><li>Developers and Tech industry</li><li>People who want to collaborate with Saragam</li></ul><p>This time, I have started with the question where the users are, what devices they are using, what screen size they are using. Also what browser they are using.</p><figure><img alt="A image of Multiples stats related to screen resoulution, device market share and Browser Market share" src="https://cdn-images-1.medium.com/max/1024/1*LlgmBPS-14OjJ6zbYAd_GQ.png" /><figcaption>A image of Multiples stats related to screen resolution, device market share and Browser Market share</figcaption></figure><p>After identifying the users preference in screen, devices and browser. I created primary screens (<strong>1366*768</strong> for desktop, <strong>360*800</strong> for mobile and <strong>768*1024</strong> for tablet) and breakpoint accordingly for the design.</p><p>Even though <strong>51%</strong> of user were from mobile and tablet, we decide to go with <strong>Desktop First Approach</strong>, because most of the client who approached us were using desktop. Also we found out that most mobile user spend less time in the site than the desktop user which had decreased our active screen time to <strong>1.6 mins</strong>. And they never got pass more than 2 pages. For a simple reminder, this might also be because of the lack of mobile friendly design, we won’t know until we test with this new design.</p><h4>Create a Design System along with Documentation</h4><p>One of the reason why the design remained inconsistent was lack of design system. So, for this iteration i created a complete design system along with best practices for design and accessibility codes that the developer must add in the development. <strong>Naming system</strong> is also incorporated in the design system, so it would be easier for further iteration.</p><p><strong>Colour system</strong> inside the design system were inspired from one of the most popular VS code theme <strong>One dark Pro</strong>. Font system remains the same but have different sizes for desktop and mobile.</p><p>For this project, I also have created a proper documentation of the design system which not only contants the active design system component but also its uses (do’s and don’t), its interaction feature and its accessibility features.</p><figure><img alt="A screenshot of Design System’s Button Components and its Doucmentation" src="https://cdn-images-1.medium.com/max/1024/1*giCcI7s53gD6CeMRzZOTzA.png" /><figcaption>Image of Documentation of Button component in Design System</figcaption></figure><h4><strong>Solving Accessibility Problems</strong></h4><p>To ensure portfolio website complies with the <strong>Web Content Accessibility Guidelines (WCAG) 2.1</strong> at the <strong>AA level</strong>, Following key <strong>principles</strong> and <strong>success criteria </strong>have been worked upon.</p><p><strong>1.Perceivable</strong></p><ul><li>Colour Contrast for all the font an Icon reached to <strong>WCAG AA standard</strong>.</li><li>Minimum Font size <strong>12</strong> to enhance readability for all devices.</li><li>Every <strong>icons</strong>, <strong>image</strong> and <strong>decoration</strong> have there alt tag defined.</li></ul><p><strong>2.Operable</strong></p><ul><li>Button and clickable elements size are increased up to <strong>42*42 pixel</strong> at least for mobile and other devices.</li><li><strong>Error stats</strong> are properly designed for all user.</li><li><strong>Focus Indicators</strong> have been tasted for clickable sections</li><li>Links are easily <strong>identifiable</strong> and there is <strong>no broken links</strong>.</li><li><strong>Keyboard Accessibility</strong> and <strong>Tab order</strong> are fixed so all people have similar experience.</li><li><strong>Landmarks</strong> has been assigned to help keyboard user to navigate easily and also to maintain hierarchy in the page.</li><li>Specialised feature have <strong>ARIA Label</strong> assign so it can be easily readable.</li><li>Dynamic content like popup will have ARIA label and priority assigned.</li><li><strong>Responsive design</strong> is also being tested</li></ul><h3>Final Outcome</h3><figure><img alt="Multiple pages of Saragm’s protfolio page with home page at the centre of it." src="https://cdn-images-1.medium.com/max/1024/1*h264b-TmEVueZUAG5gyBlA.png" /><figcaption>A image of that contain multiple pages of the project in slanted form with homepage at the centre of it.</figcaption></figure><h3>Next Step</h3><p>We are thinking about the theme of the VS code how it changes colour according to the theme. So, we are thinking as next update we will work multiple colour theme. Also, crucially we will keep on collecting data from Analytics and Clarity and see where we need to improve</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=663f4a1ba437" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/redesigning-backend-developer-portfolio-a-case-study-663f4a1ba437">Redesigning backend developer portfolio: A Case Study</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[Enhancing Accessibility Through Visual Testing: A Key Component of WCAG Compliance]]></title>
            <link>https://medium.com/design-bootcamp/enhancing-accessibility-through-visual-testing-a-key-component-of-wcag-compliance-3f586cb713f5?source=rss-2e13f6cd310b------2</link>
            <guid isPermaLink="false">https://medium.com/p/3f586cb713f5</guid>
            <category><![CDATA[inclusive-design]]></category>
            <category><![CDATA[visual-accessibility]]></category>
            <category><![CDATA[accessibility]]></category>
            <category><![CDATA[wcag-compliance]]></category>
            <category><![CDATA[web-accessibility]]></category>
            <dc:creator><![CDATA[Dipesh Manandhar]]></dc:creator>
            <pubDate>Wed, 25 Dec 2024 09:28:02 GMT</pubDate>
            <atom:updated>2026-07-28T02:05:13.634Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="Text reading ‘Visual Accessibility’ with bold, colorful letters and abstract shapes in the background, emphasizing inclusivity and design for visually impaired individuals." src="https://cdn-images-1.medium.com/max/1024/1*QdE8KmLKsMuK1KUYQUcw4g.jpeg" /><figcaption>A vibrant representation of visual accessibility, highlighting the importance of inclusive design through colorful typography and geometric shapes.</figcaption></figure><p>Accessibility is no longer optional in web design, it’s a necessity. Websites must serve diverse audiences, including users with visual impairments, and the <strong>Web Content Accessibility Guidelines (WCAG)</strong> set the global standard for achieving this goal. Meeting compliance, particularly <strong>WCAG 2.1 AA</strong>, has become not only an industry best practice but also a safeguard against legal risks and a pathway to fostering inclusivity.</p><p><strong>Testing for visual accessibility</strong> plays a critical role, addressing up to <strong>70%</strong> of WCAG compliance issues. This process involves manually assessing a website’s visual clarity, ease of navigation, and overall usability for individuals with visual impairments. While automated tools are essential for identifying technical shortcomings, they cannot capture every accessibility issue, especially those tied to nuanced design elements or user interactions.</p><p>By integrating manual visual accessibility reviews with automated tools, designers and developers can pinpoint subtle design flaws and refine solutions to create a truly inclusive digital experience. This dual approach ensures that accessibility goes beyond checkboxes, resulting in a more user-centred and equitable web.</p><p>Here are different ways of conducting an Visual Accessibility Testing.</p><h3><strong>Colour Contrast</strong></h3><figure><img alt="A grid of four blue squares displaying text with varying color contrasts, alongside a contrast checking tool showing errors in accessibility compliance and contrast ratio details." src="https://cdn-images-1.medium.com/max/1024/1*RJ051IA_vYnAlDKGrP9p4Q.jpeg" /><figcaption>Illustration of color contrast testing in design, showing a grid of text examples and a contrast checker tool that highlights issues with accessibility compliance for text readability.</figcaption></figure><p>Colour contrast refers to the difference in luminance or brightness between two colours, such as text and its background. Ensuring adequate contrast makes text, icons, and critical content readable, especially for users with colour blindness or low vision.</p><h4><strong>How to test?</strong></h4><p>Use tools like the <a href="https://webaim.org/resources/contrastchecker/"><strong>WebAIM Contrast Checker</strong></a><strong> </strong>to verify that text is distinguishable from its background.</p><h4><strong>WCAG Guidlines</strong></h4><blockquote><strong>Success Criterion 1.4.3 Contrast (Minimum) (AA)</strong>: Maintain a contrast ratio of at least <strong>4.5:1</strong> for regular text (18pt regular or 14pt bold) and <strong>3:1</strong> for large text.</blockquote><blockquote><strong>Success Criterion 1.4.6 Contrast (Enhanced) (AAA)</strong>: Increase contrast to <strong>7:1</strong> for regular text and <strong>4.5:1</strong> for large text for better readability.</blockquote><blockquote><strong>Success Criterion 1.4.11 Non-Text Contrast (AA)</strong>: Ensure icons, buttons, and form fields have a contrast ratio of <strong>3:1</strong>.</blockquote><h3><strong>Font Size &amp; Style</strong></h3><figure><img alt="Three sets of uppercase and lowercase ‘Aa’ displayed in different font sizes: 16px, 36px, and 52px, demonstrating varying text scales for design purposes." src="https://cdn-images-1.medium.com/max/1024/0*W5wotFGHTLKs5IfJ.jpg" /><figcaption>A comparison of font sizes in design, showcasing text scalability at 16px, 36px, and 52px to emphasize the importance of readability and visual hierarchy.</figcaption></figure><p>Fonts are a fundamental aspect of website design, conveying information and impacting usability. Accessible font design considers <strong>size</strong>, <strong>style</strong>, and <strong>color</strong> to ensure legibility and readability, especially for users with visual impairments or reading difficulties.</p><h4><strong>Best Practices</strong></h4><ul><li>Use clear, legible fonts (e.g., sans-serif).</li><li>Avoid overly decorative or complex styles.</li><li>Ensure sufficient differentiation between uppercase and lowercase letters.</li><li>Align text to the left wherever possible.</li><li>Use a text size greater than <strong>11px</strong>.</li><li>Create a text hierarchy with headers (e.g., <strong>H1</strong> for main titles, <strong>H2</strong> for subsections).</li><li>Underline links and use a distinct color for them.</li></ul><h4><strong>How to test?</strong></h4><p>Use tools like <strong>Stark — Contrast &amp; Accessibility Checker</strong> for <a href="https://www.figma.com/community/plugin/732603254453395948/stark-contrast-accessibility-checker">Figma designs</a> and <a href="https://www.getstark.co/">websites</a>.</p><h4><strong>WCAG Guidlines</strong></h4><blockquote><strong>Success Criterion 1.4.4 Resize Text (Level AA)</strong>: Text must be resizable up to <strong>200%</strong> without losing content or functionality.</blockquote><blockquote><strong>Success Criterion 1.4.12 Text Spacing (Level AA)</strong>: Users must be able to override styles to ensure sufficient text spacing for readability. Minimum requirements include:<br> • <strong>Line height (line spacing)</strong>: At least <strong>1.5 times</strong> the font size.<br> • <strong>Spacing following paragraphs</strong>: At least <strong>2 times</strong> the font size.<br> • <strong>Letter spacing (tracking)</strong>: At least <strong>0.12 times</strong> the font size.<br> • <strong>Word spacing</strong>: At least <strong>0.16 times</strong> the font size.</blockquote><h3>Testing with Assistive Technologies for Blind or Partially Blind Users</h3><figure><img alt="Welcome to VoiceOver dialog box with a description about VoiceOver functionality and options to proceed." src="https://cdn-images-1.medium.com/max/1017/0*VKSjlPN7xvW76Z6i.png" /><figcaption>VoiceOver welcome screen offering users guidance on using the screen reader to control the computer using only the keyboard.</figcaption></figure><p>To ensure your website is truly accessible, test it with assistive technologies. These tools simulate the experiences of visually impaired users, identifying potential barriers.</p><h4><strong>How to test?</strong></h4><p><strong>Magnification Software</strong>: Tools like <strong>ZoomText</strong> or <strong>browser zoom</strong> features help users enlarge content for better readability. Testing with these tools ensures <strong>layout issues</strong>, <strong>text clipping</strong>, or <strong>overlapping elements</strong> are resolved.</p><p><strong>Screen Readers</strong>: Screen readers like <strong>NVDA</strong>, <strong>JAWS</strong>, and <strong>VoiceOver</strong> audibly interpret web content, enabling navigation without visual reliance. Ensure content is well-structured, with accurate labels and intuitive navigation.</p><h4><strong>WCAG Guidlines</strong></h4><blockquote><strong>1. Perceivable:</strong> Ensure content is perceivable by screen readers</blockquote><blockquote><strong>Success Criterion 1.1.1 Non-text Content (Level A): </strong>Provide text alternatives for images, charts, and multimedia so screen readers can interpret and describe them.</blockquote><blockquote><strong>Success Criterion 1.3.1 Info and Relationships (Level A): </strong>Use semantic HTML to convey relationships (e.g., headings, lists, tables) so AT can recognize the document structure.</blockquote><blockquote><strong>Success Criterion 1.4.3 Contrast (Minimum) (Level AA): </strong>Ensure text and visual elements have sufficient contrast so that users who rely on text magnification or screen readers can clearly discern them.</blockquote><blockquote><strong>3. Understandable:</strong> Ensure clear and predictable content for AT users</blockquote><blockquote><strong>Success Criterion 3.1.1 Language of Page (Level A): </strong>Define the language of the page using the lang attribute (e.g., &lt;html lang=”en”&gt;) so screen readers can use the appropriate pronunciation rules.</blockquote><blockquote><strong>Success Criterion 3.3.2 Labels or Instructions (Level A): </strong>Provide clear instructions, labels, and error messages for form fields to ensure AT can guide users effectively.</blockquote><blockquote><strong>4. Robust:</strong> Ensure compatibility with a wide range of AT</blockquote><blockquote><strong>Success Criterion 4.1.2 Name, Role, Value (Level A): </strong>Use ARIA roles, states, and properties (where applicable) to ensure AT can interpret custom components correctly. Examples include using role=”button” for custom buttons and ensuring ARIA attributes like aria-expanded are updated dynamically.</blockquote><blockquote><strong>Success Criterion 4.1.3 Status Messages (Level AA): </strong>Ensure dynamic status updates (e.g., “Item added to cart”) are announced by screen readers using live regions like aria-live.</blockquote><h3><strong>Check Keyboard Navigation</strong></h3><figure><img alt="Keyboard with blue keys featuring accessibility symbols for mobility, hearing, and visual impairments." src="https://cdn-images-1.medium.com/max/1024/0*WOgapfrsv306EJV6.jpg" /><figcaption>Close-up of a keyboard with highlighted accessibility keys representing wheelchair access, hearing assistance, and visual impairment support.</figcaption></figure><p>For users with visual impairments, a keyboard often serves as their primary input device. Paired with assistive technologies like screen readers (e.g., <strong>NVDA</strong>, <strong>VoiceOver</strong>, or <strong>JAWS</strong>), users navigate through <strong>interactive elements</strong>, <strong>form fields</strong>, and <strong>content using specific keyboard</strong> keys. Proper implementation of keyboard navigation ensures:</p><ul><li><strong>Accessibility:</strong> It allows users who cannot use a mouse to interact with all functionality on the website.</li><li><strong>Compatibility:</strong> It ensures seamless operation with screen readers, magnifiers, and other assistive devices.</li></ul><h4>How to test?</h4><p><strong>Tab Order Test: </strong>Press the <strong>Tab</strong> key to navigate through all interactive elements, such as links, buttons, and form fields. Map the logical order of navigation and ensure no elements are skipped or unreachable.</p><p><strong>Common Keyboard Functions</strong></p><ul><li><strong>Tab:</strong> Move to the next interactive element (e.g., link, button, form field).</li><li><strong>Shift + Tab:</strong> Move to the previous interactive element.</li><li><strong>Enter/Return:</strong> Activate a focused element, such as a link, button, or menu option.</li><li><strong>Spacebar:</strong> Activate a focused button or toggle a checkbox; scroll down in scrollable areas.</li><li><strong>Arrow Keys:</strong> Navigate through dropdown menus, sliders, or other controls; scroll content vertically or horizontally.</li><li><strong>Escape (Esc):</strong> Close modals, dropdown menus, or other pop-up elements.</li></ul><p><strong>Additional Keys</strong></p><ul><li><strong>Ctrl + Tab / Alt + Tab:</strong> Switch between browser tabs (dependent on browser settings).</li><li><strong>Ctrl + Plus/Minus:</strong> Zoom in or out within the browser window (important for magnification users).</li><li><strong>Home/End:</strong> Jump to the beginning or end of a page or content block.</li><li><strong>Ctrl + Home/End:</strong> Move to the top or bottom of the web page.</li></ul><h4><strong>WCAG Guidlines</strong></h4><blockquote><strong>Success Criterion 2.1.1 Keyboard (Level A): </strong>All functionality must be operable via a keyboard alone, as screen reader users often rely on keyboard navigation.</blockquote><blockquote><strong>Success Criterion 2.1.2 No Keyboard Trap (Level A): </strong>Keyboard users must be able to navigate into and out of all interactive elements without getting “<strong>trapped</strong>” in any component.</blockquote><blockquote><strong>Success Criterion 2.4.1 Bypass Blocks (Level A): </strong>Provide mechanisms to skip repetitive blocks of content (e.g., “<strong>Skip to main content</strong>” links) to aid screen reader navigation. This is very important if you have big navigation (e.g e-commerce sites)</blockquote><blockquote><strong>Success Criterion 2.4.2 Page Titled (Level A): </strong>Provide a descriptive title for the page to help users understand its purpose.</blockquote><blockquote><strong>Success Criterion 2.4.3 Focus Order (Level A): </strong>Focusable elements must follow a logical and meaningful order.</blockquote><blockquote><strong>Success Criterion 2.4.6 Headings and Labels (Level AA): </strong>Use descriptive headings and labels for sections, forms, and inputs to make navigation easier for AT users.</blockquote><blockquote><strong>Success Criterion 2.4.7 Focus Visible (Level AA):</strong>Any interactive element must have a visible focus indicator to show users where the current focus is located.</blockquote><h4><strong>Landmark for Navigation</strong></h4><p>Using semantic landmarks enhances keyboard navigation for users relying on assistive technologies. Employ elements like:</p><ul><li>&lt;header&gt;</li><li>&lt;nav&gt;</li><li>&lt;main&gt;</li><li>&lt;footer&gt;</li></ul><p>These landmarks improve navigation consistency and comply with criteria like <strong>1.3.1 Info and Relationships</strong>, <strong>2.4.1 Bypass Blocks</strong>, <strong>2.4.2 Page Titled, 2.4.6 Headings and Labels</strong> and <strong>4.1.2 Name, Role, Value</strong>.</p><h3>Evaluating Image and Graphic Accessibility</h3><figure><img alt="Blue circle with a white universal accessibility symbol, depicting a person with arms outstretched." src="https://cdn-images-1.medium.com/max/820/0*abk2HslrhZRqVrUl.jpg" /><figcaption>Universal accessibility icon representing inclusivity and support for all users, used in digital and physical accessibility contexts.</figcaption></figure><p>Images and icons play a vital role in guiding users, but their accessibility is often overlooked. Proper alt text, contrast, and semantic implementation are essential for inclusive designs.</p><h4><strong>How to test?</strong></h4><ul><li>Use tools like <a href="https://wave.webaim.org/"><strong>WAVE Accessibility Checker</strong></a> or <a href="https://silktide.com/"><strong>Silktide Accessibility Checker</strong></a>.</li><li>Test with keyboard navigation to verify usability.</li></ul><h4><strong>WCAG Guidlines</strong></h4><blockquote><strong>Success Criterion 1.1.1 Non-text Content (Level A): </strong>Provide text alternatives for images, charts, icons and decorative so screen readers can interpret and describe them.</blockquote><blockquote><strong>Success Criterion 1.4.11 Non-Text Contrast (Level AA)</strong>: Essential non-text elements (icons, buttons, form fields) must have a contrast ratio of 3:1.</blockquote><h3><strong>Test Dynamic Content and Forms</strong></h3><figure><img alt="Confirmation pop-up on LinkedIn asking the user if they want to permanently delete a post, with ‘Cancel’ and ‘Delete’ button options displayed. The background shows the user’s LinkedIn profile page." src="https://cdn-images-1.medium.com/max/1024/1*91LFKjoCF-QIQKhC46A4qg.png" /><figcaption>LinkedIn’s delete post confirmation dialog ensures users make intentional choices before permanently removing content.</figcaption></figure><p>Dynamic content, such as <strong>modal dialogs</strong> or <strong>live updates</strong>, must remain accessible to all users.</p><h4><strong>How to test?</strong></h4><ul><li>Use manual keyboard testing to check form labeling, focus management, and content accessibility.</li><li>Verify that dynamic content is announced to screen readers and can be closed with the <strong>Esc</strong> key.</li></ul><h4><strong>WCAG Guidlines</strong></h4><blockquote><strong>Success Criterion 2.4.1 Bypass Blocks (Level A): </strong>Provide mechanisms like “<strong>Skip</strong> to main content” links to help users bypass dynamic elements if needed.</blockquote><blockquote><strong>Success Criterions (2.4.3 Focus Order (Level A), 2.4.7 Focus Visible (Level AA)): </strong>When dynamic content appears (e.g., modals), move keyboard focus to the new content, and restore focus when it’s closed.</blockquote><blockquote><strong>Success Criterion 4.1.3 Status Messages (Level AA): </strong>Ensure dynamic status updates (e.g., “Item added to cart”) are announced to screen readers without interrupting the user’s workflow.</blockquote><h3><strong>Tips for a Advance </strong>Visual Testing</h3><h4><strong>Collaborate with Experts</strong></h4><p>Work with accessibility consultants or visually impaired users.</p><h4><strong>Document Findings</strong></h4><p>Track barriers, prioritise fixes, and use an accessibility checklist.</p><h4><strong>Repeat Testing</strong></h4><p>Re-test after updates to ensure ongoing compliance.</p><h3>Conclusion</h3><p>Accessibility is not just a feature, it’s a responsibility. By prioritising visual testing and aligning with WCAG guidelines, you create digital experiences that are inclusive, equitable, and user-friendly for everyone, regardless of their abilities. From optimising colour contrast and font readability to ensuring seamless keyboard navigation and assistive technology compatibility, each step brings you closer to a truly accessible website.</p><p>Remember, accessibility is not a one-time task but an ongoing process. It’s about continuously evolving your design and development practices to meet the diverse needs of your audience. When you commit to accessibility, you’re not only adhering to standards but also fostering a culture of inclusivity, ensuring that no one is left behind in the digital world.</p><p><strong>Start today, commit to accessibility and build a web that works for all.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3f586cb713f5" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/enhancing-accessibility-through-visual-testing-a-key-component-of-wcag-compliance-3f586cb713f5">Enhancing Accessibility Through Visual Testing: A Key Component of WCAG Compliance</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[Mastering Web Accessibility: Essential Tools and Techniques for Inclusive Design]]></title>
            <link>https://medium.com/design-bootcamp/mastering-web-accessibility-essential-tools-and-techniques-for-inclusive-design-e64e8a5e2c22?source=rss-2e13f6cd310b------2</link>
            <guid isPermaLink="false">https://medium.com/p/e64e8a5e2c22</guid>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[digital-accessibility]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[assistive-technology]]></category>
            <category><![CDATA[accessibility]]></category>
            <dc:creator><![CDATA[Dipesh Manandhar]]></dc:creator>
            <pubDate>Thu, 28 Nov 2024 11:37:26 GMT</pubDate>
            <atom:updated>2024-11-28T11:37:26.183Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="A image of screenreader being used to test accessibility" src="https://cdn-images-1.medium.com/max/1024/1*sCr9KnKv27AFOxMsaQGeAQ.png" /><figcaption>A screen reader device being used for testing accessibility</figcaption></figure><p>Testing web accessibility is a crucial step in creating inclusive digital experiences. With the growing emphasis on adhering to <strong>Web Content Accessibility Guidelines (WCAG)</strong> and other standards like Section 508, accessibility audits help ensure your website is usable by everyone, including those with disabilities.</p><p>It’s important to note that accessibility is not solely the responsibility of designers. It requires a collaborative effort from the entire team — including <strong>developers</strong>, <strong>content creators</strong>, <strong>project managers</strong>, and <strong>QA testers</strong>. Every role contributes to identifying and resolving accessibility issues, ensuring that inclusivity is a shared priority throughout the project’s lifecycle.</p><p>This blog provides an overview of practical tools and techniques to help designers, developers and content creators identify and fix accessibility issues, keeping websites compliant and user-friendly.</p><h3>Why Accessibility Testing Matters</h3><ul><li><strong>Inclusivity:</strong> Helps make digital content accessible for users with disabilities, including vision, hearing, motor, and cognitive impairments.</li><li><strong>Legal Compliance:</strong> Adheres to standards like WCAG, ADA, Section 508, DDA, ACA, and more, protecting your organisation from lawsuits.</li><li><strong>Better Usability:</strong> Accessible design improves the overall user experience, benefiting all users, especially those accessing content on different devices.</li><li><strong>SEO Benefits:</strong> Accessible websites often perform better in search engine rankings due to cleaner structure and metadata.</li></ul><h3>General Accessibility</h3><h4>WAVE (Web Accessibility Evaluation Tool)</h4><figure><img alt="A screenshot of WAVE Web Accessibility Evaluation tool." src="https://cdn-images-1.medium.com/max/1024/1*L8zO0FLn5BL3DBL_sHVjTw.png" /><figcaption>WAVE accessibility site screenshot</figcaption></figure><p><strong>Developed by:</strong> WebAIM</p><p>WAVE is a tool designed to identify and address accessibility issues on websites. It visually highlights potential problems directly on the page, making it easier for developers and content creators to evaluate compliance with <strong>WCAG</strong> (Web Content Accessibility Guidelines) and Section 508 standards. WAVE is widely used for ensuring website inclusivity and is also valued by <strong>attorneys</strong> for its role in conducting preliminary assessments of accessibility compliance in legal cases.</p><p>Among its key features, WAVE highlights <strong>accessibility errors</strong>, <strong>contrast issues</strong>, and <strong>structural problems</strong> while evaluating <strong>ARIA</strong> (Accessible Rich Internet Applications) attributes and element order. The tool offers visual feedback on problem areas, enabling developers and content creators to easily spot and fix issues.</p><p>Learn more through the <a href="https://www.youtube.com/watch?v=ITUDiTgAZY0">Introduction to WAVE</a>.</p><h4><strong>Accessibility Checker</strong></h4><figure><img alt="A screenshot of Accessibility checker website" src="https://cdn-images-1.medium.com/max/1024/1*SOBTSIWwscpuHcbdcVoAeA.png" /><figcaption>Accessbility Checker site screenshot</figcaption></figure><p><strong>Developed by:</strong> Accessibility Checker</p><p>Accessibility Checker is a web-based tool that assists developers and content creators in identifying potential accessibility issues on websites. With its easy-to-use interface, it provides valuable insights into compliance with <strong>WCAG</strong> and other national accessibility guidelines.</p><p>The tool supports ongoing monitoring of <strong>accessibility compliance</strong>, ensuring that websites maintain inclusivity throughout their lifecycle. It identifies errors such as <strong>contrast problems</strong>, <strong>missing alt text</strong>, and <strong>structural challenges</strong>, offering actionable recommendations for improvement.</p><p>The user-friendly interface allows for continuous compliance monitoring and provides WCAG-compliant recommendations along with other common guidelines such as <strong>ADA</strong>, <strong>Section 508</strong>, <strong>DDA</strong>, <strong>ACA</strong>, and more. This helps ensure that websites remain inclusive throughout their lifecycle.</p><h4><strong>Accessibility Scanner</strong></h4><figure><img alt="A screenshot of google play store displaying Accessibility Scanner" src="https://cdn-images-1.medium.com/max/1024/1*mlOFt1oBckbAzv8BoWMQTw.png" /><figcaption>Accessibility Scanner App screenshot</figcaption></figure><p><strong>Developed by:</strong> Google</p><p>Google’s Accessibility Scanner is an Android tool designed to help developers identify and resolve accessibility issues in mobile applications. It evaluates <strong>touch target sizes</strong>, <strong>contrast ratios</strong>, and <strong>navigation structures</strong>, while also identifying <strong>missing</strong> or <strong>unclear content labels</strong>. The tool provides WCAG-compliant recommendations and integrates seamlessly into app development workflows, making it easier for developers to create inclusive designs. This ensures that mobile applications are accessible to all users, including those with disabilities.</p><p>Learn more through the <a href="https://www.youtube.com/watch?v=Yxy4p-eDEpw">How to use Accessibility Scanner</a>.</p><h4>Lighthouse</h4><figure><img alt="A screenshot of google extension of lighthouse" src="https://cdn-images-1.medium.com/max/1024/1*ReD568JqaCYToZBP99HlOQ.png" /><figcaption>Lighthouse Chorme Extension screenshot</figcaption></figure><p><strong>Developed by:</strong> Google</p><p>Lighthouse is a built-in tool in Chrome DevTools that offers accessibility insights alongside performance and SEO audits. It runs accessibility tests directly in your browser and highlights issues like <strong>missing labels</strong>,<strong> low contrast</strong>, and more. Lighthouse is easy to use, providing clear scoring and actionable feedback, making it perfect for a quick overview of accessibility compliance. This tool helps developers efficiently identify and address accessibility issues to improve user experience and ensure inclusivity.</p><h4>Silktide Accessibility Checker</h4><figure><img alt="A screenshot of google extension of silktide accessibility checker" src="https://cdn-images-1.medium.com/max/1024/1*MJSIXNVwIlrK9AZGa5ai3g.png" /><figcaption>Silktide Accessibility Checker Extension screenshot</figcaption></figure><p><strong>Developed by:</strong> Silktide</p><p>Silktide Accessibility Checker is a comprehensive tool designed to help users identify and address accessibility issues on websites. It scans websites for a wide range of accessibility problems, such as <strong>missing alt text</strong>, <strong>improper heading structures</strong>, and <strong>contrast issues</strong>. The tool provides detailed reports with descriptions of issues and actionable recommendations for fixes. It also includes compliance checks for WCAG 2.1 standards and other accessibility guidelines. Silktide Accessibility Checker offers a user-friendly interface, making it easy for developers to monitor and maintain accessibility throughout a website’s lifecycle, ensuring ongoing compliance and inclusivity.</p><h4>Inbuilt Chrome Feature</h4><figure><img alt="A screenshot of google extension of chrome default accessibility" src="https://cdn-images-1.medium.com/max/1024/1*jVS7o9g01Ku4DMXa7Dw6MA.png" /><figcaption>Accessibility feature of chrome screenshot</figcaption></figure><p>Your chrome bowser has an accessibility feature within for the developer. This feature is disabled, you can turn it on buy following steps:</p><ol><li>Right click and select inspect</li><li>Open Settings.</li><li>In the Experiments tab, search for enable full accessibility tree view in the Elements.</li><li>Enable by ticking the checkbox next to the experiment.</li><li>Close. Settings.</li></ol><p>Learn more about this feature throw <a href="https://www.youtube.com/watch?v=8dCUzOiMRy4&amp;t=144s">The art of labelling</a>. For the latest update check <a href="https://www.youtube.com/watch?v=pJL6qtfYkBo">How to use Chrome’s accessibility tree</a>.</p><h3><strong>Specific Testing Techniques</strong></h3><p>Ensuring a website is accessible goes beyond automated scans — it involves hands-on testing that simulates real-world user experiences. These specific techniques help identify usability challenges for users relying on assistive technologies or alternate interaction methods. Below, we expand on four critical areas for accessibility testing.</p><h4><strong>Keyboard Navigation</strong></h4><p>Many users with motor impairments or vision disabilities rely on keyboards instead of mice for navigation. Ensuring a logical, seamless keyboard navigation experience is essential for these users.</p><p><strong>How to Test</strong></p><ul><li>Disable your mouse or trackpad and navigate your website using just the <strong>Tab</strong>, <strong>Enter</strong>, and <strong>Arrow</strong> keys.</li><li>Ensure every interactive element (links, buttons, form fields) has a clear, visible focus indicator. Focus indicators often appear as a border or underline and help users identify where they are on the page.</li><li>Verify that the tabbing sequence follows a logical order, moving from one element to the next in a way that mirrors how content is visually arranged. For instance, the focus should move top to bottom and left to right, consistent with reading patterns.</li></ul><p><strong>Taba11y</strong></p><figure><img alt="A screenshot of google chrome extension taba11y" src="https://cdn-images-1.medium.com/max/1024/1*gx77dIE0gBYGllcb5wLggg.png" /><figcaption>taba11y Extension screenshot</figcaption></figure><p>Taba11y calculates the tab order of elements on a webpage and visually maps it out. It is used visualises tab navigation paths to ensure logical order. It also highlights focusable elements for accessibility review. It helps us improve keyboard navigation for users with motor disabilities.</p><h4><strong>Screen Reader Compatibility</strong></h4><p><strong>Voiceover</strong></p><figure><img alt="A image of VoiceOver feature displayed in iPhone" src="https://cdn-images-1.medium.com/max/1024/0*sO7UrhsuLXdLa_l4.jpg" /><figcaption>VoiceOver feature image in iphone</figcaption></figure><p>Built into Apple devices, VoiceOver provides audio descriptions of text, images, and interface elements. It supports navigation through gestures on iOS and keyboard commands on macOS, offering a seamless user experience. Additionally, VoiceOver integrates with Braille displays, making it a versatile tool for tactile accessibility. Its pre-installed nature ensures no setup or cost, making it an excellent choice for developers to test how visually impaired users experience their content within Apple’s ecosystem.</p><p>Learn more through the <a href="https://www.youtube.com/watch?v=5R-6WvAihms">Screen Reader Basics: VoiceOver</a>.</p><p><strong>Narrator</strong></p><figure><img alt="A screenshot of Narrator feature in windows setting" src="https://cdn-images-1.medium.com/max/1024/0*vOiBdjsEAigor_tm.png" /><figcaption>Narrotor features in setting in chorme</figcaption></figure><p>Microsoft’s built-in screen reader for Windows devices reads aloud text, buttons, and interface elements. It supports keyboard shortcuts for efficient navigation and integrates with Braille displays to enhance tactile usability. Like VoiceOver, Narrator is free and requires no additional installation, making it a practical option for accessibility testing. Developers can use Narrator to simulate the experiences of visually impaired users and optimise content for inclusivity.</p><p><strong>Screen Reader</strong></p><figure><img alt="A screenshot of Google chrome extension, Screen Reader" src="https://cdn-images-1.medium.com/max/1024/1*MoHo4E9XMMDtweL2nWaoeg.png" /><figcaption>Screen Reader Extension screenshot</figcaption></figure><p>This browser-based tool enables spoken feedback for web content, allowing users to navigate websites and web applications using keyboard shortcuts and voice output. Integrated directly into Chrome, it offers a straightforward and accessible way for developers to test their web content. While simpler than VoiceOver and Narrator, the Chrome Screen Reader Extension provides valuable insights into the accessibility of websites, especially for quick testing sessions.</p><h4><strong>Colour Contrast and Visual Design</strong></h4><p>Tools like Funkify and Silktide Accessibility Checker can test whether text and UI elements meet contrast ratio requirements and visual related issue.</p><p><strong>Funkify</strong></p><figure><img alt="A screenshot of Google chrome extension, Funkify" src="https://cdn-images-1.medium.com/max/1024/1*gL__RwH3WSm6TOodPwpC6A.png" /><figcaption>Funkify Extension screenshot</figcaption></figure><p>Funkify is a Chrome extension that simulates user experiences for individuals with various disabilities. It mimics conditions like colour blindness, low vision, and motor impairments, helping developers understand usability challenges from a user’s perspective. This empathy-driven design tool aids in creating accessible interfaces by providing a firsthand experience of accessibility barriers.</p><p><strong>Final Thoughts</strong></p><p>Testing web accessibility is a multifaceted process, combining automated tools, browser extensions, and manual techniques. Tools like <strong>WAVE</strong>, <strong>Accessibility Checker</strong>, and browser-based utilities such as <strong>Lighthouse, Silktide</strong> make it easier to uncover issues, while empathy-driven tools like <strong>Funkify</strong> and <strong>taba11y</strong> provide valuable insights into user experiences.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e64e8a5e2c22" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/mastering-web-accessibility-essential-tools-and-techniques-for-inclusive-design-e64e8a5e2c22">Mastering Web Accessibility: Essential Tools and Techniques for Inclusive Design</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[Global Accessibility Laws: Key Cases and Standards for Digital Inclusivity]]></title>
            <link>https://medium.com/design-bootcamp/global-accessibility-laws-key-cases-and-standards-for-digital-inclusivity-3620f3911060?source=rss-2e13f6cd310b------2</link>
            <guid isPermaLink="false">https://medium.com/p/3620f3911060</guid>
            <category><![CDATA[accessibility]]></category>
            <category><![CDATA[wcag]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[law]]></category>
            <dc:creator><![CDATA[Dipesh Manandhar]]></dc:creator>
            <pubDate>Thu, 31 Oct 2024 04:34:14 GMT</pubDate>
            <atom:updated>2024-10-31T06:28:17.782Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="A set of yellow office supplies, including pens, paper clips, a magnifying glass, and a smartphone, arranged neatly around a stack of cards with the word “ACCESSIBILITY” written on top. The background and items are monochromatic in yellow, highlighting the focus on accessibility." src="https://cdn-images-1.medium.com/max/800/1*J3NEIMHL7bYyRinegjmMSQ.png" /><figcaption>Accessibility is an essential aspect of both physical and digital spaces, ensuring equal access for all individuals, including those with disabilities.</figcaption></figure><p>Accessibility laws have become an Achilles’ heel for many small businesses that overlooked compliance when starting out. The consequences can be severe, with some forced to shut down due to legal challenges and fines. Navigating these regulations is essential, particularly as digital accessibility becomes more crucial in a global economy.</p><p>Across the globe, at least 20 countries have implemented their own accessibility laws. These include the United States, Canada, the United Kingdom, the European Union, Australia, Japan, India, and others. While the specific rules may vary, most of these policies are rooted in the Web Content Accessibility Guidelines (WCAG), an international standard that aims to make digital content accessible to people with disabilities.</p><p>For any project involving design or development, adhering to these guidelines is not optional — it’s a legal and ethical necessity. In this blog, we’ll explore key accessibility laws in a few of the most prominent countries and why they matter for businesses today.</p><h3>United States: Americans with Disabilities Act (ADA)</h3><figure><img alt="Americans with Disabilities Act (ADA) logo featuring four blue diamond shapes, each with a white symbol: a wheelchair user, an ear with sound waves, a person using a white cane, and two hands signing the letters “A” and “D” in American Sign Language (ASL)." src="https://cdn-images-1.medium.com/max/760/1*U9cM9p0wOQiJvgVTV-NqMA.jpeg" /><figcaption>Logo of the Americans with Disabilities Act (ADA) representing accessibility for individuals with disabilities, including visual, hearing, and mobility impairments, as well as sign language communication.</figcaption></figure><p>The <a href="https://www.ada.gov/law-and-regs/regulations/title-ii-2010-regulations/"><strong>Americans with Disabilities Act</strong></a><strong> (ADA)</strong> is a comprehensive civil rights law established in 1990 to prohibit discrimination against individuals with disabilities. It applies across many domains of public life, including employment, education, transportation, and both public and private spaces open to the general public.</p><h4><strong>Scope of the ADA:</strong></h4><p>The ADA covers both <strong>physical</strong> and <strong>digital accessibility</strong>. It ensures that people with disabilities have equal access to services in sectors like:</p><ul><li><strong>Employment</strong>: Employers must make reasonable accommodations for employees with disabilities.</li><li><strong>Public Services and Accommodations</strong>: This includes both physical access to buildings and digital access to services like websites and apps.</li><li><strong>Telecommunications</strong>: Ensures people with disabilities can access and communicate through telecommunication services.</li><li><strong>Miscellaneous Provisions</strong>: Includes additional civil rights protections for individuals with disabilities.</li></ul><h4><strong>Digital Accessibility and WCAG Compliance:</strong></h4><p>While the ADA doesn’t specifically dictate technical web standards, <strong>WCAG (Web Content Accessibility Guidelines)</strong> are commonly referenced in lawsuits and settlements to define what constitutes digital accessibility. Courts and the Department of Justice (DOJ) often use <strong>WCAG 2.0 or 2.1 Level AA</strong> as benchmarks for compliance with ADA regulations in the digital space.</p><h4><strong>Penalties for Non-Compliance:</strong></h4><p>The ADA doesn’t directly impose financial penalties, but organizations found in violation can face <strong>lawsuits</strong>. These may result in paying for Attorneys’ fees, Court costs and Damages to plaintiffs</p><p>In cases where the DOJ identifies a violation, they can issue <strong>compliance orders</strong> that mandate businesses make their digital content accessible. Non-compliance with these orders can lead to:</p><ul><li><strong>Fines up to $75,000</strong> for a first violation</li><li><strong>$150,000</strong> for subsequent violations</li></ul><p>Penalties can be particularly steep for <strong>larger organisations</strong> or <strong>repeat offenders</strong>.</p><h3><strong>Section 508</strong> of the <strong>Rehabilitation Act of 1973</strong></h3><figure><img alt="Section 508 logo with the number “5” on the left, a figure using a wheelchair and laptop in the center, and the number “8” on the right, representing accessibility standards for digital content and technology under the Section 508 amendment." src="https://cdn-images-1.medium.com/max/650/1*1VBEby8PHyumRjchjHHW8w.jpeg" /><figcaption>Section 508 compliance logo symbolizing digital accessibility, featuring a person using a laptop while seated in a wheelchair between the numbers 5 and 8.</figcaption></figure><p><a href="https://www.section508.gov/manage/laws-and-policies/"><strong>Section 508 of the Rehabilitation Act of 1973</strong></a> is a U.S. federal law that mandates <strong>federal agencies</strong> ensure their electronic and information technology (EIT) is accessible to individuals with disabilities. As the oldest disability law applied to federal agencies, it sets the foundation for digital accessibility in government-operated technology.</p><h4><strong>Key Components of Section 508:</strong></h4><ul><li><strong>Scope</strong>: Section 508 applies to <strong>federal agencies</strong> and their contractors. It ensures that people with disabilities have access to:</li><li><strong>Software</strong>: Applications and programs used by government agencies must be accessible.</li><li><strong>Websites</strong>: Government websites must follow strict accessibility standards to ensure inclusivity.</li><li><strong>Hardware</strong>: Physical devices like computers, phones, and kiosks used by federal agencies must also be accessible.</li><li><strong>Other Electronic and Information Technology (EIT)</strong>: Any other digital resources must accommodate users with disabilities.</li></ul><h4><strong>WCAG Compliance and Technical Standards:</strong></h4><ul><li>Section 508 explicitly adopts <strong>WCAG (Web Content Accessibility Guidelines)</strong> as the technical standard for digital accessibility.</li><li>As of the 2017 “508 Refresh”, it requires all web content to meet <strong>WCAG 2.0 Level AA</strong> standards, which set specific requirements for text readability, navigation, and alternative text for images.</li></ul><h4><strong>Penalties for Non-Compliance:</strong></h4><ul><li>Unlike the ADA, Section 508 does not impose specific <strong>financial penalties</strong> or fines.</li><li>However, agencies found to be non-compliant can face <strong>legal consequences</strong>. These typically involve orders to <strong>remediate accessibility barriers</strong> within their EIT systems. Failure to do so can result in further legal actions and reputational damage for the agency or contractor.</li></ul><h4>Which Law Should You Focus On?</h4><p>When designing websites or digital services, it’s crucial to understand which accessibility law applies to your project.</p><ul><li><strong>ADA (Americans with Disabilities Act)</strong>: Focus on the ADA if you’re working on websites or services for both <strong>public and private sectors</strong>. Specifically:<br><strong>Title II</strong> covers <strong>state and local government websites</strong>.<br><strong>Title III</strong> applies to websites and services for <strong>public accommodations</strong> (private businesses open to the public).</li><li><strong>Section 508 of the Rehabilitation Act</strong>: If you’re designing for <strong>federal government</strong> websites and digital services, ensure <strong>WCAG 2.0 Level AA compliance</strong>. This law is mandatory for all <strong>federal agencies</strong> and their contractors.</li></ul><h3>Canada: The Accessible Canada Act (ACA)</h3><figure><img alt="Accessible Canada Act banner featuring bold blue text on a light background, with red and green curved design elements on the sides, symbolizing Canada’s commitment to eliminating barriers for people with disabilities." src="https://cdn-images-1.medium.com/max/800/1*NyY23HHoq-sZ6DWKN8k6Ag.jpeg" /><figcaption>Banner for the Accessible Canada Act, aimed at promoting barrier-free accessibility across Canada for individuals with disabilities.</figcaption></figure><p>The <a href="https://laws-lois.justice.gc.ca/eng/acts/a-0.6/"><strong>Accessible Canada Act (ACA)</strong></a> is a federal law, enacted on July 11, 2019, aimed at creating a <strong>barrier-free Canada by 2040</strong>. The law focuses on improving accessibility for individuals with disabilities, ensuring they have equal opportunities and full participation in society, especially within federally regulated sectors.</p><h4>Key Components of the ACA:</h4><p><strong>Scope</strong>: The ACA applies to <strong>federally regulated sectors</strong> in Canada, including:</p><ul><li>Telecommunications</li><li>Banking</li><li>Transportation</li><li>Federal government services</li></ul><p>The ACA mandates equal access to services for people with disabilities, with a special emphasis on <strong>digital accessibility</strong>, ensuring websites, mobile apps, and other digital services are accessible.</p><h4>Digital Accessibility and WCAG Compliance:</h4><p>The ACA explicitly references <strong>WCAG 2.0 Level AA</strong> as the standard for web and digital accessibility, similar to other global accessibility laws.</p><p><strong>Compliance mechanisms</strong> include:</p><ul><li><strong>Accessibility Plans</strong>: Organisations must develop and publish plans to address accessibility.</li><li><strong>Feedback Mechanisms</strong>: Systems must be in place for people to provide feedback on accessibility issues.</li><li><strong>Audits</strong>: Regular audits ensure that companies comply with ACA requirements.</li></ul><h4>Penalties for Non-Compliance:</h4><ul><li>Penalties for not adhering to the ACA’s accessibility obligations can be severe, with fines reaching up to <strong>$250,000 per violation</strong>.</li><li>This includes failing to meet accessibility standards for <strong>digital content</strong>, making it crucial for organisations to ensure their websites and services are fully accessible to individuals with disabilities.</li></ul><h3>Canada: The Accessibility for Ontarians with Disabilities Act (AODA)</h3><figure><img alt="Accessibility for Ontarians with Disabilities Act (AODA)” text alongside four blue accessibility symbols. The symbols include a person in a wheelchair, a person with a cognitive disability, a person using a cane for visual impairment, and hands signing in American Sign Language (ASL)." src="https://cdn-images-1.medium.com/max/800/1*4MFf7RjsxGHnCCoJ9rL5Yg.jpeg" /><figcaption>Accessibility for Ontarians with Disabilities Act (AODA) logo featuring various symbols representing different types of disabilities.</figcaption></figure><p>The <a href="https://www.aoda.ca/"><strong>Accessibility for Ontarians with Disabilities Act (AODA)</strong></a> is a provincial law enacted in <strong>2005</strong>, with the goal of making <strong>Ontario fully accessible by 2025</strong>. This law covers a wide range of areas, including <strong>employment, transportation, customer service</strong>, and most notably, <strong>information and communications</strong>, which encompasses digital accessibility.</p><h4>Key Components of the AODA:</h4><p><strong>Scope</strong>: The AODA applies to <strong>public sector organisations</strong> (such as government entities) and <strong>private sector organisations</strong> with <strong>50 or more employees</strong>. It ensures that people with disabilities have equal access to:</p><ul><li><strong>Services and facilities</strong>: Physical accessibility in public and private spaces.</li><li><strong>Information and communications</strong>: Digital accessibility of websites and online content.</li></ul><h4>Digital Accessibility and WCAG Compliance:</h4><p>The AODA requires organizations to comply with <strong>WCAG 2.0 Level AA standards</strong> for web and digital content.</p><p><strong>Key Deadlines</strong>: By <strong>January 1, 2021</strong>, public sector organizations and large private organizations were required to ensure that all <strong>new websites</strong> and <strong>new web content</strong> met WCAG 2.0 Level AA standards.</p><h4>Penalties for Non-Compliance:</h4><p>Failure to comply with the AODA, including digital accessibility requirements, can result in substantial fines:</p><ul><li><strong>Corporations</strong> can face fines of up to <strong>$100,000 per day</strong>.</li><li><strong>Individuals or officers of corporations</strong> can be fined up to <strong>$50,000 per day</strong>.</li></ul><p>The AODA, like other accessibility laws, ties closely to <strong>WCAG 2.0 standards</strong>, which are critical for meeting legal requirements for web and digital accessibility in Ontario.</p><h3>Canada: The Canadian Human Rights Act (CHRA)</h3><figure><img alt="Accessibility for Ontarians with Disabilities Act (AODA)” text alongside four blue accessibility symbols. The symbols include a person in a wheelchair, a person with a cognitive disability, a person using a cane for visual impairment, and hands signing in American Sign Language (ASL)." src="https://cdn-images-1.medium.com/max/800/1*-zjTjZFYSToNG26sFmnnaw.jpeg" /><figcaption>Accessibility for Ontarians with Disabilities Act (AODA) logo featuring various symbols representing different types of disabilities.</figcaption></figure><p>The <a href="https://laws-lois.justice.gc.ca/eng/acts/h-6/"><strong>Canadian Human Rights Act (CHRA)</strong></a>, established in <strong>1977</strong>, is a federal anti-discrimination law designed to protect individuals in Canada from discrimination on various grounds, including disability. Although it is not specifically focused on accessibility, the <strong>CHRA</strong> plays a crucial role in ensuring <strong>digital accessibility</strong> as part of its broader commitment to preventing discrimination against people with disabilities.</p><h4>Key Components of the CHRA:</h4><p><strong>Scope</strong>: The CHRA applies to <strong>federal agencies</strong> and <strong>private sector organisations</strong> under federal jurisdiction. It protects individuals from discrimination in:</p><ul><li>Employment</li><li>Services</li><li>Facilities</li></ul><p><strong>Disability as a Protected Ground</strong>: The CHRA ensures that individuals with disabilities are not denied access to services or information, including <strong>digital content</strong>, based on their disability.</p><h4>Digital Accessibility and WCAG Compliance:</h4><p>Although the CHRA does not mandate specific technical standards for accessibility, <strong>WCAG 2.0 or 2.1 Level AA</strong> is often used as a benchmark for determining whether an organization’s <strong>digital platforms</strong> meet accessibility requirements.</p><p><strong>Digital Inaccessibility Complaints</strong>: Individuals can file complaints if they face barriers to accessing digital content or services. These complaints can lead to:</p><ul><li><strong>Investigations</strong> into the organisation’s practices.</li><li><strong>Remedial orders</strong> that require the organisation to address the accessibility barriers.</li></ul><h4>Penalties for Non-Compliance:</h4><p>Organizations found in violation of the CHRA’s anti-discrimination provisions may face <strong>legal actions</strong> or be required to make changes to improve accessibility. Although specific financial penalties are not outlined, failure to comply can lead to <strong>significant reputational damage</strong> and potential <strong>legal costs</strong>.</p><h4>Which Law Should You Focus On?</h4><p>When designing websites or digital services for Canadian audiences, it’s important to know which accessibility law applies to your project. Here’s a quick guide:</p><ul><li><strong>ACA (Accessible Canada Act)</strong>: Focus on the <strong>ACA</strong> if you’re designing for <strong>federal public sector organisations</strong> or <strong>federally regulated industries</strong> like <strong>banking</strong> and <strong>telecommunications</strong>.</li><li><strong>AODA (Accessibility for Ontarians with Disabilities Act)</strong>: Focus on <strong>AODA</strong> for both <strong>public</strong> and <strong>private sector organisations</strong> operating in <strong>Ontario</strong>. This includes all large private companies (50+ employees) and public entities.</li><li><strong>Canadian Human Rights Act (CHRA)</strong>: The <strong>CHRA</strong> provides general protection against discrimination for people with disabilities. Complaints can arise if websites or digital platforms hinder access to goods or services, even if they don’t fall under ACA or AODA jurisdiction.</li></ul><h3>European Union: The European Accessibility Act (EAA)</h3><figure><img alt="A blue flag with a circle of 12 yellow stars surrounding a white symbol of a person with outstretched arms, representing accessibility and inclusion in Europe." src="https://cdn-images-1.medium.com/max/626/1*ppAJkruhat2QIz9GemBySQ.jpeg" /><figcaption>European accessibility symbol surrounded by 12 yellow stars, symbolizing the European Union’s commitment to accessibility and inclusion for people with disabilities.</figcaption></figure><p>The <a href="https://ec.europa.eu/social/main.jsp?catId=1202"><strong>European Accessibility Act (EAA)</strong></a> is a landmark legislative act aimed at improving accessibility for persons with disabilities across the <strong>European Union (EU)</strong>. Adopted on <strong>June 7, 2019</strong>, the EAA requires EU member states to integrate the directive into their national laws by <strong>June 28, 2022</strong>, with full enforcement starting on <strong>June 28, 2025</strong>. The EAA complements existing EU laws on accessibility, supporting the EU’s broader goal of fostering an inclusive environment for all.</p><h4>Key Components of the EAA:</h4><p><strong>Scope</strong>: The EAA covers a wide array of <strong>products and services</strong>, both digital and physical, ensuring they are accessible to individuals with disabilities.</p><ul><li>This includes <strong>websites, mobile applications, e-commerce platforms, e-books</strong>, and <strong>self-service terminals</strong> like <strong>ATMs</strong> and <strong>ticketing machines</strong>.</li></ul><h4>Key Digital Accessibility Areas Covered</h4><ul><li><strong>Websites and Mobile Applications</strong>: Services like <strong>banking, e-commerce</strong>, and <strong>telecommunications</strong> must ensure full accessibility.</li><li><strong>E-commerce</strong>: Online shopping platforms and <strong>payment services</strong> must be accessible to users with disabilities.</li><li><strong>Digital Reading Materials</strong>: <strong>E-books</strong> and other digital publications must meet accessibility standards.</li><li><strong>Telecommunication Services</strong>: Ensures access to <strong>telecommunication services</strong> and <strong>emergency communications</strong>.</li><li><strong>Self-Service Terminals</strong>: <strong>ATMs, ticketing machines</strong>, and other automated terminals must be accessible.</li></ul><h4>Digital Accessibility and WCAG Compliance:</h4><p>The EAA closely aligns with the <strong>Web Content Accessibility Guidelines (WCAG)</strong>, which serve as the <strong>international benchmark</strong> for digital accessibility. The EAA largely adopts <strong>WCAG 2.1 Level AA</strong> standards for ensuring that websites, digital services, and platforms are accessible.</p><h4>Penalties for Non-Compliance:</h4><p>Organizations that fail to comply with the EAA’s accessibility standards may face <strong>fines or penalties</strong> enforced by national authorities. The severity of the penalties varies by member state but can include <strong>substantial financial penalties</strong>. <strong>Non-compliant products or services</strong> may be removed from the market or <strong>prevented from being sold</strong> within the EU.</p><h3>European Union: The EN 301 549 Standard</h3><figure><img alt="An infographic titled “EN 301 549” with five icons representing web accessibility, compliance, a clock showing February 2014, a website, and a mobile app, all connected by dotted lines." src="https://cdn-images-1.medium.com/max/800/1*O41BCFrrGBMJ3Gd1mi6P3w.png" /><figcaption>EN 301 549 infographic illustrating key aspects of the European standard for web and mobile accessibility, including compliance, applicable to all websites and mobile apps since February 2014.</figcaption></figure><p>The <a href="https://www.etsi.org/deliver/etsi_en/301500_301599/301549/03.02.01_60/en_301549v030201p.pdf"><strong>EN 301 549</strong></a> is a European standard for <strong>ICT (Information and Communication Technology) accessibility</strong>, providing detailed technical requirements to ensure digital products and services are accessible to people with disabilities. It is a key reference for both <strong>public</strong> and <strong>private organizations</strong> to comply with accessibility laws like the <strong>European Accessibility Act (EAA)</strong> and the <strong>EU Web Accessibility Directive</strong>.</p><h4>Key Components of EN 301 549:</h4><p><strong>Established</strong>: Initially developed in <strong>March 2014</strong> and most recently updated in <strong>2021</strong> to align with <strong>WCAG 2.1</strong> (Web Content Accessibility Guidelines).</p><p><strong>Scope</strong>: Covers a wide range of ICT products and services, including:</p><ul><li>Hardware</li><li>Software</li><li>Multimedia content</li><li>Telecommunication services</li><li>Web content and mobile applications</li></ul><h4>Digital Accessibility and WCAG Compliance:</h4><p>The standard closely aligns with <strong>WCAG 2.1 Level AA</strong>, ensuring that digital content and interfaces are usable by people with disabilities. It is applicable to <strong>public sector bodies</strong> under the EU Web Accessibility Directive and <strong>private sector organizations</strong> that want to meet accessibility standards.</p><h4>Penalties for Non-Compliance:</h4><p>Compliance with EN 301 549 is mandatory under laws such as the <strong>EAA</strong> and the <strong>EU Web Accessibility Directive</strong>. Non-compliance can result in <strong>fines, legal action</strong>, and the potential <strong>withdrawal of products from the market</strong>.</p><h3>European Union: The EU Web Accessibility Directive (Directive (EU) 2016/2102)</h3><figure><img alt="A blue background with a map of Europe, featuring a circle of 12 yellow stars surrounding a white accessibility symbol, representing the EU Web Accessibility Directive." src="https://cdn-images-1.medium.com/max/800/1*DyeX6A1ja2fcjgZBvPfQig.png" /><figcaption>EU Web Accessibility Directive symbol with 12 yellow stars representing the European Union, emphasizing the directive’s goal of making public sector websites and mobile apps accessible across Europe.</figcaption></figure><p>The <a href="https://eur-lex.europa.eu/eli/dir/2016/2102/oj"><strong>EU Web Accessibility Directive</strong></a> (Directive (EU) 2016/2102) is a critical piece of legislation aimed at ensuring <strong>public sector websites and mobile applications</strong> across the European Union (EU) are accessible to all, particularly people with disabilities. It harmonizes web accessibility requirements across <strong>EU member states</strong>, providing a unified legal framework to improve accessibility in the digital realm.</p><h4>Key Components of the Web Accessibility Directive:</h4><p><strong>Scope</strong>: The directive applies to <strong>public sector bodies</strong> within the EU, including:</p><ul><li>Government websites</li><li>Local authority websites</li><li>Public sector mobile applications</li></ul><p><strong>Accessibility Requirements</strong>: The directive ensures that <strong>digital services</strong> provided by public authorities are accessible to individuals with disabilities, including those with <strong>visual, auditory, cognitive,</strong> and <strong>motor impairments</strong>.</p><h4>Digital Accessibility and WCAG Compliance:</h4><p>The directive mandates that public sector websites and mobile apps comply with <strong>WCAG</strong> (Web Content Accessibility Guidelines), primarily <strong>WCAG 2.1 Level AA</strong>. This framework ensures that digital content and services are usable by all individuals, including those with disabilities.</p><h4>Penalties for Non-Compliance:</h4><p><strong>Member states</strong> are responsible for enforcing the directive and may impose <strong>fines or sanctions</strong> on public sector bodies that fail to meet accessibility standards. The specific <strong>penalties vary</strong> depending on the national enforcement mechanisms of each EU member state.<em>Focus on EAA, if your designing for private sector services (e.g., e-commerce, banking).</em></p><h4>Which Law Should You Focus On?</h4><p>When designing digital products or services in the EU, it’s important to understand which accessibility law or standard applies. Here’s a quick guide:</p><ul><li><strong>EAA (European Accessibility Act)</strong>: Focus on the <strong>EAA</strong> for <strong>private sector services</strong> like <strong>e-commerce, banking</strong>, and other consumer-facing platforms.</li><li><strong>EN 301 549 Standard</strong>: Focus on <strong>EN 301 549</strong> for <strong>ICT products and services</strong>, especially when dealing with <strong>public procurement</strong> or other digital platforms. This standard aligns with <strong>WCAG 2.1</strong>.</li><li><strong>EU Web Accessibility Directive</strong>: Focus on the <strong>Web Accessibility Directive</strong> for <strong>public sector websites and apps</strong>, such as those for <strong>government agencies</strong> or <strong>schools</strong>.</li><li><strong>Best Practice</strong>: To ensure compliance across all sectors, following <strong>WCAG 2.1 Level AA</strong> will cover most accessibility requirements.</li></ul><h3>United Kingdom: The Equality Act of 2010</h3><figure><img alt="The British royal coat of arms above the text “The Equality Act 2010,” representing the UK law on equality and accessibility." src="https://cdn-images-1.medium.com/max/700/1*p4bKYAxArWdoXBQEKbpcAQ.jpeg" /><figcaption>The Equality Act 2010 emblem, featuring the royal coat of arms, symbolizing the UK legislation that promotes equality and accessibility for all, including people with disabilities.</figcaption></figure><p>The <a href="https://www.gov.uk/guidance/equality-act-2010-guidance"><strong>Equality Act 2010</strong></a>, established on <strong>October 1, 2010</strong>, is the cornerstone of anti-discrimination legislation in the <strong>United Kingdom</strong>. It protects individuals from discrimination in various areas, including accessibility for people with disabilities. The Act applies to both <strong>public and private sector organisations</strong> across the UK and requires that they do not discriminate against people with disabilities, which includes ensuring access to <strong>digital services</strong> like websites and mobile apps.</p><h4>Key Components of the Equality Act:</h4><ul><li><strong>Scope</strong>: The Act covers all <strong>public and private sector organisations</strong>, ensuring that individuals with disabilities have equal access to goods, services, and information.</li><li><strong>Reasonable Adjustments</strong>: While the Act doesn’t explicitly reference <strong>WCAG</strong>, it requires organizations to make “<strong>reasonable adjustments</strong>” to ensure their websites and digital services are accessible to users with disabilities.</li></ul><h4>Digital Accessibility and WCAG Compliance:</h4><p>Although not mandated, courts and regulators frequently reference <strong>WCAG 2.1 Level AA</strong> as a standard to assess compliance with the Act’s accessibility requirements. Failing to meet WCAG standards can be considered a form of <strong>discrimination</strong>, especially if it prevents individuals with disabilities from accessing digital content.</p><h4>Penalties for Non-Compliance:</h4><p>Individuals can file <strong>discrimination complaints</strong> if they encounter barriers accessing websites or digital platforms. Courts may require organizations to make the necessary accessibility adjustments and, in some cases, impose <strong>fines</strong> or order <strong>compensation</strong> to individuals affected. <strong>Failure to resolve accessibility issues</strong> can lead to costly <strong>legal actions</strong> and damage to an organisation’s reputation.</p><h3>Australia: The Disability Discrimination Act of 1992 (DDA)</h3><figure><img alt="The Australian coat of arms with a kangaroo and emu on either side of a shield, above the text “Disability Discrimination Act 1992.”" src="https://cdn-images-1.medium.com/max/674/1*BuPE62OA1XPPRayGBKgc5A.jpeg" /><figcaption>The Disability Discrimination Act 1992 logo, featuring Australia’s coat of arms, representing the Australian law that prohibits discrimination against people with disabilities in various areas of public life.</figcaption></figure><p>The <a href="https://www.legislation.gov.au/C2004A04426/2018-04-12/text"><strong>Disability Discrimination Act 1992</strong></a><strong> (DDA), </strong>Estd in December 5, 1992, is Australia’s key legislation aimed at preventing discrimination against individuals with disabilities, including in the digital space. While the Act does not specifically mention <strong>web accessibility</strong>, it provides a legal framework for ensuring <strong>websites and mobile applications</strong> are accessible to people with disabilities.</p><h4>Key Components of the DDA:</h4><p><strong>Scope</strong>: The DDA applies to both <strong>public and private sector organizations</strong> across Australia. It prohibits discrimination based on disability in various areas such as:</p><ul><li><strong>Employment</strong></li><li><strong>Education</strong></li><li><strong>Access to premises</strong></li><li><strong>Provision of goods and services</strong>, which includes <strong>digital platforms</strong> like websites and mobile apps.</li></ul><h4>Digital Accessibility and WCAG Compliance:</h4><p>Although the DDA does not explicitly mention <strong>WCAG</strong> (Web Content Accessibility Guidelines), compliance with <strong>WCAG 2.0 or 2.1 Level AA</strong> is widely recognized as the <strong>standard</strong> for digital accessibility in Australia. Australian courts have referred to WCAG in various legal cases to determine if a website meets the DDA’s accessibility requirements.</p><h4>Penalties for Non-Compliance:</h4><p>Complaints about inaccessible websites can be submitted to the <strong>Australian Human Rights Commission (AHRC)</strong> for <strong>conciliation</strong>. If conciliation fails, the case may proceed to the <strong>Federal Court</strong>, where courts can:</p><ul><li><strong>Award compensation</strong> to affected individuals.</li><li><strong>Mandate accessibility adjustments</strong> to ensure compliance.</li></ul><h3>What Happens If Accessibility Guidelines Are Not Followed?</h3><p>Ignoring accessibility guidelines can result in significant legal consequences, including lawsuits and financial penalties. Below are some notable lawsuits where companies lost for failing to meet accessibility standards:</p><h4>United State of America: <strong>Target Corporation (2006)</strong></h4><figure><img alt="Customers entering a Target store with a ‘We’re hiring’ sign displayed on the exterior wall." src="https://cdn-images-1.medium.com/max/800/1*Q0W5yqDa1jG0zofPD7eIgg.jpeg" /><figcaption>Target store featuring a ‘We’re hiring’ sign, reflecting ongoing recruitment efforts.</figcaption></figure><p><strong>Details</strong>: The National Federation of the Blind (NFB) sued Target, claiming its website was inaccessible to blind users. The case argued that Target’s website violated the Americans with Disabilities Act (ADA).</p><p><strong>Outcome</strong>: Target settled for $6 million and agreed to make its website accessible, establishing a key precedent for digital accessibility.</p><h4>United State of America: Amazon (2015)</h4><figure><img alt="Amazon logo on a white background with a blue sky above" src="https://cdn-images-1.medium.com/max/800/1*Y3sRa2jIJc9fc2SzPXZfSg.jpeg" /><figcaption>Amazon’s iconic logo displayed on a building, symbolizing the company’s strong global presence.</figcaption></figure><p><strong>Details</strong>: Amazon faced a class-action lawsuit for not providing adequate accommodations for employees with disabilities in its warehouses.</p><p><strong>Outcome</strong>: The company settled for $1.2 million and committed to improving workplace accommodations and accessible communication systems.</p><h4>Canada: Bell Canada (2017)</h4><figure><img alt="Bell logo overlaying a cityscape of Toronto, with the CN Tower and waterfront visible under a partly cloudy sky." src="https://cdn-images-1.medium.com/max/800/1*WWddbRuukfGoPPjR_E9mvQ.jpeg" /><figcaption>Bell logo superimposed on the Toronto skyline, showcasing the company’s presence in Canada’s telecommunications landscape.</figcaption></figure><p><strong>Details</strong>: A blind customer filed a complaint with the Canadian Human Rights Tribunal, claiming Bell Canada’s billing documents were not accessible, citing the Accessible Canada Act.</p><p><strong>Outcome</strong>: Bell Canada was ordered to provide accessible formats, such as Braille or large print, reinforcing the need for companies to ensure accessible communications.</p><h4>European Union: Deutsche Bahn (2016)</h4><figure><img alt="A Deutsche Bahn (DB) train at a station platform, displaying the DB logo on its side under a large, modern station roof." src="https://cdn-images-1.medium.com/max/800/1*sLmmVtA0zc7cXzUxWQamnw.jpeg" /><figcaption>Deutsche Bahn (DB) train at a station platform, representing Germany’s high-speed rail service and extensive transportation network.</figcaption></figure><p><strong>Details</strong>: Deutsche Bahn, Germany’s national railway company, was sued for not providing accessible travel information to passengers with disabilities, violating the European Accessibility Act.</p><p><strong>Outcome</strong>: Deutsche Bahn was required to make digital platforms for train schedules, ticketing, and other services accessible, enforcing the EU’s commitment to accessible public transportation.</p><h4>United Kingdom: Royal Bank of Scotland (2012)</h4><figure><img alt="RBS logo and signage on a building, representing the Royal Bank of Scotland." src="https://cdn-images-1.medium.com/max/800/1*CTwWIksn-pzGYfLjxN1oDw.jpeg" /><figcaption>The Royal Bank of Scotland logo on a branch building, symbolizing one of the major banks in the UK.</figcaption></figure><p><strong>Details</strong>: A blind customer sued RBS for failing to provide an accessible online banking service. The case was filed under the UK’s Equality Act 2010.</p><p><strong>Outcome</strong>: RBS settled and agreed to make its online banking platform compatible with screen readers and other assistive technologies, highlighting the importance of digital accessibility for financial institutions.</p><h4><strong>Australia: </strong>Coles Supermarkets (2014)</h4><figure><img alt="Coles supermarket sign above checkout counters inside a busy store." src="https://cdn-images-1.medium.com/max/800/1*RiCu3e3zhCGVfuHb1UbtGg.jpeg" /><figcaption>Shoppers inside a Coles supermarket in Australia, with the prominent Coles logo displayed above the checkout area.</figcaption></figure><p><strong>Details</strong>: Graeme Innes, Australia’s former Disability Discrimination Commissioner, sued Coles for having an inaccessible online grocery store that did not work with screen readers. The lawsuit was filed under the Disability Discrimination Act 1992.</p><p><strong>Outcome</strong>: Coles settled and made its website accessible to visually impaired users, marking an important moment in Australia’s digital accessibility landscape.</p><p>The path to creating an accessible world is far from over, but these landmark cases across the United States, United Kingdom, Canada, Australia, and the European Union have set the standard for what’s expected of businesses and public institutions. Each case serves as a powerful reminder that accessibility is not merely a legal obligation; it’s a commitment to inclusivity, ensuring equal access to services and opportunities for everyone.</p><p>As accessibility laws continue to evolve worldwide, companies must keep pace by making their physical spaces, digital platforms, and services accessible to all. Whether you’re a business owner, developer, or designer, these cases should inspire action.</p><h3>References</h3><ul><li>“Americans with Disabilities Act (ADA).” <strong>ADA.gov</strong>. Available at: <a href="https://www.ada.gov/">https://www.ada.gov</a></li><li>“Accessible Canada Act.” <strong>Government of Canada</strong>. Available at: <a href="https://www.canada.ca/en/employment-social-development/programs/accessible-canada.html">https://www.canada.ca/en/employment-social-development/programs/accessible-canada.html</a></li><li>“Equality Act 2010.” <strong>UK Government</strong>. Available at: <a href="https://www.legislation.gov.uk/ukpga/2010/15/contents">https://www.legislation.gov.uk/ukpga/2010/15/contents</a></li><li>“Disability Discrimination Act 1992.” <strong>Australian Government</strong>. Available at: <a href="https://www.legislation.gov.au/Details/C2018C00125">https://www.legislation.gov.au/Details/C2018C00125</a></li><li>“Web Accessibility Directive (EU) 2016/2102.” <strong>European Commission</strong>. Available at: <a href="https://ec.europa.eu/digital-strategy/our-policies/web-accessibility">https://ec.europa.eu/digital-strategy/our-policies/web-accessibility</a></li><li>“EN 301 549 Accessibility Requirements.” <strong>ETSI</strong>. Available at: <a href="https://www.etsi.org/standards">https://www.etsi.org/standards</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3620f3911060" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/global-accessibility-laws-key-cases-and-standards-for-digital-inclusivity-3620f3911060">Global Accessibility Laws: Key Cases and Standards for Digital Inclusivity</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>
    </channel>
</rss>