The Support Industry Has an Accessibility Problem
Let's be direct: most customer support platforms treat accessibility like a nice-to-have. A checkbox for the enterprise sales deck. A compliance footnote buried in a PDF nobody reads.
That's not us.
We just shipped full WCAG 2.1 AA compliance across the entire cStar platform — the app, the customer-facing widget, the marketing site, all of it. Not because a lawyer told us to. Because support agents and customers with disabilities deserve tools that actually work for them.
"Behind every 'urgent' ticket is a human having a bad day."
If we mean that — and we do — then "human" includes the agent navigating with a keyboard, the customer using a screen reader, and the team lead who needs high contrast to read their dashboard.
What Changed (And Why You Should Care)
Keyboard Users Can Actually Use Everything Now
Try using your favorite support tool without a mouse. Just keyboard. Tab through it. See how far you get before something breaks — a modal you can't escape, a dropdown you can't open, a button you can't reach.
We went through every interaction in cStar and made sure keyboard-only users can do everything. Navigate tickets, reply to customers, check stats, manage settings. Every modal traps focus properly and returns you to where you were when you close it. Every action has a keyboard equivalent.
If you're a power user who lives on keyboard shortcuts, this benefits you too.
Screen Readers Tell the Full Story
When an agent earns XP, when a boss battle triggers, when a toast notification pops up — screen reader users used to miss all of it. The adventure was happening, and they couldn't hear it.
Now every dynamic update gets announced. Achievements, notifications, combat updates — it's all wired into live regions that screen readers pick up automatically. The gamification isn't just visual anymore. The adventure is for everyone.
The Widget Works for Your Customers Too
Here's the part that matters most: the customer-facing widget — the thing your actual end users interact with — is now fully accessible.
A customer using a screen reader can navigate message history, read who sent what and when, see typing indicators, and submit tickets without ever touching a mouse. That's not a nice-to-have for your business. That's 15% of the global population being able to use your support channel.
Icons Stopped Yelling
We use icons everywhere — over 900 of them across the app. Before this update, screen readers were trying to announce every single one. A decorative star next to "XP" would get read as "star image XP" — noise that makes the whole experience exhausting.
Now decorative icons stay silent. Meaningful ones (like a standalone settings gear) announce themselves clearly. Clean signal, zero noise.
Color Contrast Actually Passes
We audited every text and background combination across all four themes. Some of our lighter text colors were technically readable for most people but fell below WCAG standards for people with low vision.
Fixed. Documented. Future theme changes get checked against the same audit so we don't accidentally regress.
Why We Actually Did This
Here's the uncomfortable truth: accessibility in SaaS is often treated as a Tier 3 priority. Something you'll "get to eventually." Something that only matters when an enterprise prospect asks about it.
That thinking is broken.
But honestly? The legal and business arguments aren't why we did this. We did it because cStar is built on the belief that support agents are heroes. All of them. Including the ones who navigate with a keyboard, use magnification, or rely on screen readers.
If your gamification system only works for sighted mouse users, it's not really "for everyone." It's for most people, and you're hoping nobody notices the gap.
We noticed. We fixed it.
This Isn't a One-Time Thing
Accessibility isn't a destination — it's a practice. We've baked it into our development process so every new feature ships accessible from day one. We've got automated checks that catch regressions before they reach you, and a public accessibility statement that documents our standards and how to report issues.
We're not perfect. We're committed. And if you find something we missed, tell us — we'll fix it.