Services

I help product teams improve accessibility, frontend quality, design-system behavior, and practical AI-assisted delivery. The work is usually most valuable when accessibility is treated as part of the product system, not as a final pass before release.

How I can help

Accessible frontend systems

Review and improve interface patterns so they work across semantic HTML, keyboard interaction, focus behavior, assistive technology expectations, and real product states.

Possible support includes:

component behavior review
keyboard and focus-flow review
form and validation interaction review
accessible names, roles, states, and relationships
practical implementation guidance for React and modern frontend stacks

Design-system accessibility

Strengthen component libraries and design-system patterns so accessibility is built into reusable decisions instead of rediscovered screen by screen.

Possible support includes:

button, link, form, modal, disclosure, and navigation patterns
documentation for behavior, states, and usage rules
design-token and variant review from an accessibility perspective
component API guidance
test strategy for interaction behavior

Component and interaction reviews

Look closely at specific product flows or components where small interface decisions carry larger usability and accessibility consequences.

Possible support includes:

design review before implementation
pull-request or code review support
interaction-state review
disabled, loading, error, and success behavior
recommendations that designers and engineers can both act on

Design-to-code collaboration

Help teams close the gap between what design tools show and what working interfaces actually require.

Possible support includes:

handoff guidance
Figma component behavior notes
shared language for designers and engineers
design-system documentation improvements
identifying questions that should be answered before implementation

AI-assisted frontend workflow guidance

Help teams use AI-assisted development tools without letting generated code quietly weaken accessibility, maintainability, or product behavior.

Possible support includes:

review checklists for AI-generated UI code
prompts and guardrails for accessible component work
examples of useful and risky AI-assisted frontend patterns
team workflow guidance for review, testing, and documentation

This may be a good fit if your team is…

building or maintaining a design system
trying to improve accessibility without slowing delivery to a crawl
seeing repeated frontend quality issues across product surfaces
working through complex interaction, state, or validation patterns
using AI tools for frontend work and wanting stronger review guardrails
trying to improve collaboration between design, engineering, and product

Probably not the right fit if you need…

Some teams need a different kind of support. This should help make that clearer early.

a quick overlay or automated accessibility fix
a one-time compliance checklist with no product or engineering follow-through
visual design work only
a full agency team for brand, content, and production design
guaranteed legal compliance language

Want to talk through a product or system problem?

If your team is working through accessibility, design systems, frontend quality, or AI-assisted development, start with a short note about what you are building and where the work is getting difficult.

Start a conversation