I am a front-end architect and UX/accessibility engineer who works in the translation layer between product intent, implementation reality, and AI-assisted delivery.
I help teams build complex systems that are not just functional, but usable, accessible, maintainable, and grounded in judgment.
## Why translation matters In complex product environments, the risk is rarely just whether a screen can be built. The harder problem is whether requirements, design intent, accessibility expectations, backend constraints, and implementation details still mean the same thing by the time they reach users. ## From code to experience I began my web career as a full-stack Java developer after earning a Computer Science degree. Early in my career, I worked on a technically useful application that struggled to gain adoption. That gap bothered me: the system worked, the functionality mattered, but people were not using it. Trying to understand why led me to user experience. It also led me to Section 508 accessibility, at a time when formal training and structured learning paths were limited. I taught myself accessibility through available standards, guidance, and implementation practice, then deepened that direction through a Master’s degree in Human-Computer Interaction. ## The work became translation That experience changed the direction of my career. I moved deliberately from general full-stack development into front-end architecture, UX, and accessibility because I wanted to work where implementation decisions directly affect whether systems are understandable, usable, and responsible. Over time, I became the person who could translate across disciplines: between backend constraints and front-end behavior, between visual design and usable interfaces, between accessibility requirements and practical QA validation, and between product intent and the code that actually reaches users.