About
This work sits at the intersection of design, frontend engineering, accessibility, design systems, and practical AI-assisted development.
The goal is not to make accessibility a separate checklist or to treat frontend quality as a purely technical concern. The goal is to help teams make better product decisions that hold up in real interfaces.
A cross-functional perspective
My approach is shaped by work across design, frontend engineering, accessibility, and design systems. That combination matters because many product problems do not live cleanly in one discipline.
A button, form, modal, or navigation pattern may look like a design detail, a code detail, an accessibility detail, or a process detail depending on who is looking at it. In practice, it is often all of those things at once.
What I pay attention to
- semantic structure and native behavior
- keyboard interaction and focus management
- accessible names, states, and relationships
- component APIs and reusable interaction patterns
- design-system documentation that explains behavior, not only appearance
- design-to-code collaboration
- AI-assisted frontend workflows that still require human judgment
How I work
I try to make the next decision clearer. That may mean reviewing a component, mapping an interaction state, improving a design-system pattern, asking better implementation questions, or helping a team create guardrails for AI-generated frontend code.
The work is practical, plain-spoken, and grounded in how teams actually design, build, test, and maintain product interfaces.
The throughline
Accessible product engineering is not only about finding issues. It is about building systems that make better decisions easier the next time.
When teams improve the underlying patterns, they do more than fix one screen. They improve the way future work gets designed, implemented, reviewed, and maintained.
Looking for this kind of perspective?
If your team is working through accessibility, design systems, frontend quality, or AI-assisted delivery, the Services page explains the kinds of problems this work can support.