rajathtirumangalam

Breakdowns

This is where I document what breaks in real accessibility—after systems pass audits, meet guidelines, and still fail users.

These are not checklists. These are patterns, failures, and gaps that show up in actual use.

Start here

  • Busting Myths About Visually Impaired Individuals

    Shattering Stereotypes: The Truth About Visually Impaired Individuals with Humor and Insight

  • Vision Lost, Vibes Found: Rajath Tirumangalam’s Unconventional Journey

    Embark on an extraordinary adventure with Rajath Tirumangalam, the mastermind behind #BlindAdventures and #VisionaryHumor. In his tale of #ResilientJourney, Rajath boldly navigates life, smashing stereotypes with a dash of humor and an unstoppable spirit. Join him in the symphony of #BeyondStereotypes as he discovers the magic of #UnleashingPotential, inviting you into his world with #LifeWithRajath…

  • The 34,900 Problem: How to Bulk Clean Your Gmail Without Losing the Emails That Matter

    We’ve all been there. You look at that little number next to your Inbox—maybe it’s 500, maybe it’s 35,000—and you feel that spark of “digital dread.” As a professional, that number isn’t just clutter; it’s a wall between you and the work that actually matters. Manual cleaning is a nightmare. Gmail’s UI often lags when…

  • When success messages don’t confirm success

    I submit a form. The button is activated.Something happens. But I don’t know if it worked. There’s no confirmation.Or worse, there is—but I never hear it. Maybe a message appeared visually.Maybe it was placed somewhere I’m not focused on.Maybe it disappeared too quickly. So I’m left wondering: Did it go through?Should I try again?Did I…

  • State changed. Nobody told the user.

    State changed. Nobody told the user. I activate something. Nothing happens. Or at least, nothing that I can perceive. Maybe the page updated.Maybe a panel opened.Maybe something important changed somewhere on the screen. But I don’t know that. Because nothing told me. Technically, the system did everything right.The state changed.The UI updated. But accessibility isn’t…

  • Button. Button. Button. That’s not accessibility.

    I open an app and start navigating. “Button.” “Button.” “Button.” That’s all I hear. No context. No purpose. No indication of what each one does. Just… button. Technically, everything is there. The elements are accessible. The screen reader is reading them. It would probably pass an audit. But in real use, this isn’t usable. Because…

  • Accessibility Is Not a Feature — It’s a Relationship

    Accessibility bugs often look like silence. When a screen reader only says “Button,” trust disappears. One small string can turn confusion into confidence — and that changes everything.