I don’t focus on whether something passes accessibility checks.
I focus on what happens after.
Where I usually get involved
A product passes an audit—but users still struggle to complete tasks.
A flow works technically—but feels confusing in practice.
Something is “accessible”—but no one is sure what just happened.
That’s where I step in.
What this looks like in practice
I’ve worked across physical spaces, digital systems, and emerging experiences.
- reviewing systems that pass audits but fail in real use
- testing with screen readers, keyboards, and actual workflows
- identifying where interaction breaks—not just where code is missing
- working with teams to turn unclear behavior into usable experiences
This includes work on:
- accessible self-checkout systems in retail environments
- physical space accessibility where real-world constraints matter
- 3D and immersive experiences where traditional patterns don’t apply
- NVDA add-ons that solve gaps in everyday workflows
How I work with teams
I usually work closely with designers, developers, and researchers.
Not just pointing out issues—but helping teams understand:
- what the user is actually experiencing
- why something feels unclear
- what needs to change to make it usable
Sometimes that means slowing things down.
Because clarity matters more than speed.
If this sounds familiar
If your product passes accessibility checks—but still feels unclear, inconsistent, or hard to use—
that’s usually where I can help.
You can reach me through the contact page.