rajathtirumangalam

Accessibility that works after the interface responds.

Most systems are technically accessible.
They pass audits. They meet guidelines.

In real use, things break in quieter ways:

  • a state changes, but the user doesn’t know
  • an error appears, but isn’t perceived
  • an action completes, but leaves uncertainty

I work in that gap.

I design systems that stay usable when real users, real environments, and real constraints collide—not just when everything behaves as expected.

17+ years in technology.

14+ years in accessibility (CPWA).

Built for scale, not edge cases. Proven in real systems.

Real Work. Real Breakdowns.

This work spans physical spaces, digital systems, and emerging experiences—where accessibility often passes, but still fails users.

  • Audited physical spaces where accessibility fails beyond compliance
  • Contributed to prototypes of accessible self-checkout systems in real retail environments
  • Worked on making 3D and immersive experiences accessible
  • Presented accessibility work at CSUN Assistive Technology Conference (2019)
  • Built NVDA add-ons used in real workflows
  • Tested systems beyond compliance across NVDA, JAWS, and VoiceOver

Most of these failures don’t appear in audits. They appear in use.

Where accessibility breaks (even when it passes)

These are the patterns I see repeatedly—across products, platforms, and environments.

  • State changes that never reach screen readers
  • Success messages that don’t confirm outcomes
  • Dynamic updates with no user awareness
  • Buttons that speak—but don’t inform

Tools I’ve Built

I build NVDA add-ons to solve interaction gaps that standards don’t catch.

  • QuickInfo — fast access to structured page information
  • AudioToggles — control audio feedback efficiently
  • Stay Awake — prevents workflow interruptions

Books & Writing

I write about the layer where accessibility passes—but systems still fail users.

  • The Invisible User: What Your Code Assumes — how systems break for users even when they meet accessibility standards
  • TalkBack – Android: ಬಳಸುವ ಸರಳ ಮಾರ್ಗದರ್ಶಿ — a practical guide to using Android with accessibility features
  • The Invisible User: What Your Android Code Assumes (in progress) — extending accessibility thinking into native mobile systems

Start Here

If your product passes accessibility checks but still feels unclear, inconsistent, or hard to use—you’re already in the gap.

This is where I focus: understanding what breaks after compliance.