<?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 Girish Tarwatkar on Medium]]></title>
        <description><![CDATA[Stories by Girish Tarwatkar on Medium]]></description>
        <link>https://medium.com/@girishtarwatkar?source=rss-f66416316fd1------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*BMQRnd3no-BUxAlMoHVYZw.png</url>
            <title>Stories by Girish Tarwatkar on Medium</title>
            <link>https://medium.com/@girishtarwatkar?source=rss-f66416316fd1------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 15:10:38 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@girishtarwatkar/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[Accessibility Is Not a Feature. It’s a Responsibility.]]></title>
            <link>https://medium.com/@girishtarwatkar/accessibility-is-not-a-feature-its-a-responsibility-5128eb83c580?source=rss-f66416316fd1------2</link>
            <guid isPermaLink="false">https://medium.com/p/5128eb83c580</guid>
            <dc:creator><![CDATA[Girish Tarwatkar]]></dc:creator>
            <pubDate>Thu, 21 May 2026 19:27:56 GMT</pubDate>
            <atom:updated>2026-05-21T19:27:56.908Z</atom:updated>
            <content:encoded><![CDATA[<p>The moment I opened the <a href="https://www.apple.com/">apple.com</a>, something immediately caught my attention.</p><p>It wasn’t a product.</p><p>It wasn’t a flashy animation.</p><p>It wasn’t a marketing headline.</p><p><strong>It was a disabled person featured prominently in the hero section.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*w1CdLsEqSIIC3AY0PQkLzw.png" /><figcaption>Apple homepage hero banner</figcaption></figure><p>That single design decision says a lot about Apple’s approach to accessibility and inclusive design.</p><p>Most companies treat accessibility as a technical checklist hidden deep inside support documentation or compliance pages.</p><p>Apple puts it front and center.</p><p>Visible from the very first interaction.</p><p>And honestly, that matters more than many designers realize.</p><h3><strong>Representation Creates Inclusion</strong></h3><p>When users visit a digital product and immediately see people like themselves represented, it creates a sense of belonging.</p><p>For people with disabilities, this is even more meaningful because many digital experiences unintentionally exclude them through:</p><ul><li>Poor contrast</li><li>Missing keyboard accessibility</li><li>Non-readable interfaces for screen readers</li><li>Tiny touch targets</li><li>Complex navigation</li><li>Motion-heavy experiences</li><li>Inaccessible forms and interactions</li></ul><p>Apple’s hero section communicates something powerful without saying much:</p><blockquote><strong>“Technology should work for everyone.”</strong></blockquote><p>That is not just branding.<br> That is product philosophy.</p><h3>Accessibility Is Good UX</h3><p>Accessibility is often misunderstood as a limitation for creativity.</p><p>But in reality, accessibility improves usability for everyone.</p><p>Some simple examples:</p><ul><li>Captions help users in noisy places</li><li>Voice control helps multitasking users</li><li>Better contrast improves outdoor readability</li><li>Larger tap targets improve mobile interaction</li><li>Clear navigation reduces cognitive load</li></ul><p>Inclusive design benefits all users — not just users with disabilities.</p><p>And that is why accessibility should never be treated as an afterthought.</p><h3>Designing Beyond Compliance</h3><p>Many teams still approach accessibility only from a compliance perspective:</p><ul><li>WCAG checklist</li><li>Legal requirements</li><li>QA validation</li><li>Accessibility audits before release</li></ul><p>But accessibility should start much earlier.</p><p>During:</p><ul><li>Research</li><li>Information architecture</li><li>Interaction design</li><li>Content strategy</li><li>Visual design</li><li>Usability testing</li></ul><p>The best accessible experiences are designed intentionally from the beginning — not patched later.</p><p>Apple’s accessibility page reflects exactly that mindset.</p><h3>The Role of Designers</h3><p>As designers, we often focus heavily on:</p><ul><li>Business goals</li><li>Engagement metrics</li><li>Conversion rates</li><li>Visual aesthetics</li><li>Feature prioritization</li></ul><p>But accessibility deserves equal priority because design decisions directly impact whether someone can independently use a product or not.</p><p>That is a huge responsibility.</p><p>Accessibility is not only about usability.</p><p>It is about dignity, independence, and equal participation.</p><h3>What Designers Can Learn From This</h3><p>A few simple reminders for every UX team:</p><ul><li>Design for different abilities from day one</li><li>Test products with real accessibility scenarios</li><li>Include accessibility reviews in design critiques</li><li>Treat accessibility as a product quality benchmark</li><li>Make inclusive representation visible in the UI</li></ul><p>Because accessible products do not just reach more users.</p><p>They create dignity, independence, and equal access.</p><p>And that is what meaningful design should do.</p><h3>A Small Design Decision With a Big Message</h3><p>Featuring a disabled person in the hero section may seem like a small creative choice.</p><p>But it sends a strong message:</p><ul><li>Accessibility is important</li><li>Inclusion matters</li><li>Disabled users are valued users</li><li>Technology should empower everyone</li></ul><p>And that is exactly what meaningful product design should do.</p><p>#Accessibility #InclusiveDesign #UXDesign #ProductDesign #Apple #UserExperience #AccessibilityMatters #DesignThinking</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5128eb83c580" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How a Small UX Detail in the Paytm App Caught My Eye — And Why It Matters]]></title>
            <link>https://medium.com/@girishtarwatkar/how-a-small-ux-detail-in-the-paytm-app-caught-my-eye-and-why-it-matters-5880dc595eef?source=rss-f66416316fd1------2</link>
            <guid isPermaLink="false">https://medium.com/p/5880dc595eef</guid>
            <dc:creator><![CDATA[Girish Tarwatkar]]></dc:creator>
            <pubDate>Sun, 27 Jul 2025 19:42:01 GMT</pubDate>
            <atom:updated>2025-07-27T19:42:01.300Z</atom:updated>
            <content:encoded><![CDATA[<h3>How a Small UX Detail in the Paytm App Caught My Eye — And Why It Matters</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NgKRoEtMZZ4j93e6tK2Lvg.png" /><figcaption>Smart use of real estate: surfacing feature updates where users already are.</figcaption></figure><p>As a Senior Product UX Designer, I’m always on the lookout for smart, intentional product decisions-even (and especially) the subtle ones. Recently, while using the Paytm app, I noticed a thoughtful addition: a <strong>“What’s New”</strong> section placed right within the Money Transfer module.</p><p>At first glance, it might seem like a minor tweak. But from a product and UX lens, it’s a great example of <strong>context-aware communication and discovery</strong>.</p><h3>Why This Caught My Attention</h3><p>Typically, product updates are shown via:</p><ul><li>App store changelogs (which most users ignore)</li><li>Push notifications (which are easy to dismiss)</li><li>In-app popups (which interrupt the experience)</li></ul><p>But this pattern does something smarter — it <strong>shows updates at the right time, in the right place</strong>, <em>without interrupting the user journey</em>.</p><p>By placing “What’s New” directly within a high-traffic section of the app, Paytm:</p><ul><li><strong>Improves feature visibility</strong> without being aggressive</li><li><strong>Encourages exploration</strong> without breaking flow</li><li><strong>Reinforces transparency</strong> by showing that the product evolves and improves regularly</li></ul><p>It’s a great way to make users feel informed, without asking for their attention.</p><h3>The Product Thinking Behind It</h3><p>This is more than just a UI addition — it reflects mature product thinking:</p><ul><li><strong>Meet users where they are</strong> — inside the product, not outside it</li><li><strong>Minimize friction</strong> — no extra taps, no overlays</li><li><strong>Build habit and trust</strong> — users begin to expect value from returning</li></ul><p>It also has the potential to improve adoption rates of newly launched features — something we often struggle with when updates are buried in release notes or emailers.</p><h3>A Reminder for All of Us in Product &amp; Design</h3><p>Not all impactful UX comes from big redesigns.<br>Sometimes, it’s the <em>smallest, quietest changes</em> that do the most — by guiding the user gently, not forcefully.</p><p>If you’re working on a feature rollout or driving engagement, ask yourself:</p><blockquote><strong><em>How can we keep users informed </em>without asking for their attention<em>?</em></strong><em><br></em><strong><em>Can we bring value </em>into<em> the user flow instead of pushing it on them?</em></strong></blockquote><p>This pattern in Paytm is a great reminder that <em>microUX = macro impact</em>.</p><h3>Final Thoughts</h3><p>As designers and folks, it’s important we notice, learn from, and appreciate these moments — even if we didn’t build them ourselves.</p><p>👏 Well done, <a href="https://medium.com/u/a0179fc86114">Paytm</a><br> A small touch, but a powerful one.</p><p>#UXDesign #ProductDesign #MicroUX #DesignDetails #FeatureDiscovery #Paytm #ProductThinking #UserExperience #DesignObservation</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5880dc595eef" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>