I Don't Just Test
for Accessibility.
I Live It.

My expertise isn't academic.
It's lived.

JAWS — Job Access With Speech — is the world's leading screen reader for blind and low-vision users. For most people, it's a tool they use in testing scenarios or demos. For me, it's how I navigate the entire digital world. Every browser, every app, every form, every checkout flow — I experience it through a screen reader, every day, without exception.

That kind of daily lived experience creates a depth of understanding that no amount of academic study or certification coursework can fully replicate. I know where screen readers break — not because I've read the WCAG documentation, but because I've encountered those failures in my own daily life. I feel the friction of a missing aria-label. I know what it's like to have a dropdown trap focus and go nowhere. I understand what a disorganized heading structure does to your ability to navigate a page.

But lived experience isn't abstract. It's a broken ARIA role that turns a button into silence — no name, no context, just nothing. It's an unlabeled button that gives a screen reader nothing to announce, so you press it, or you don't, because you have no way of knowing what it does. It's a page where state changes happen visually — a menu opens, a panel expands, a notification appears — and none of it is ever announced. You sit there, not knowing something changed, wondering whether your action did anything at all.

And then there's the form. A required field has failed validation — shown to sighted users as a red underline beneath the input. The submit button is dimmed. Nothing is announced. No alert, no error, no indication of where the problem is. So you read back through the entire form, field by field, trying to find the issue yourself. That process doesn't take minutes — it takes hours. And at the end of it, you don't feel like a user who hit a bug. You feel like less of a person. That's before you even get to CAPTCHAs, or the dashboards and portals that simply lock you out with no workaround and no alternative path forward.

This is exactly what I test for. Because I know what it costs when it's broken.

"I don't test for compliance. I test for the person who spent three hours on a form they couldn't submit — and walked away feeling like less."

This is what separates QA11Y Labs from every other accessibility consultancy: I am the user they're testing for. I don't guess how blind and low-vision users will experience your product — I know. And I bring that knowledge directly to your team, in clear, actionable findings that prioritize real-world impact over theoretical compliance.

When a company like Vivint rebuilds their entire smart home app based on my findings, or when Mountain America Credit Union keeps reaching back out for new feature testing — that's not because I ran a great automated scan. That's because I gave them a perspective they couldn't get anywhere else.