Design Systems & Accessibility Architecture

I design and scale token-driven systems that turn design decisions into reusable, measurable product infrastructure.

wA11y is a token-driven, accessibility-first system designed to make inclusive design the default, not the exception.

Explore the system →

Operating Model: Federated

I design systems to scale across federated product teams — enabling autonomy while maintaining consistency.

Core System Team

Product team contribution model

Decision framework

Governance: Clear Ownership, Lightweight Process

My governance model focuses on:

Explicit ownership

Contribution pathways

Readiness checklists

Changelog & deprecation policy

The goal is to ensure the system evolves intentionally instead of reactively.

Accessibility: Built Into the System

I embed accessibility directly into:

  • Design tokens (color contrast, motion, spacing)

  • Component behavior (focus management, keyboard support, ARIA patterns)

  • Documentation (clear guidance on correct and incorrect usage)

Every component ships with:

  • Accessibility requirements and known limitations

  • Usage guidance for edge cases

  • Alignment with WCAG standards from the start

This approach reduces downstream remediation work and ensures teams don’t need to be accessibility experts to build inclusive products.

Adoption: Designed, Measured, and Earned

Adoption is not assumed—it is designed for.

Documentation

Clear documentation that supports real workflows, not ideal ones

Libraries

Figma libraries and coded components that stay in sync

Updates & Communication

Regular system updates and communication with product teams

Devs Partnerships

Direct partnerships with engineering to reduce friction at implementation

I measure impact through:

Component usage and duplication metrics

Reduction in custom UI and design debt

Decreased accessibility bugs

Feedback loops with designers and engineers

When teams choose the system because it makes their work easier, adoption becomes sustainable.

What I Optimize For

Consistency without rigidity

Speed without fragmentation

Accessibility without extra effort

Governance without bureaucracy

A successful system is invisible when it’s working—and painfully obvious when it’s missing. My role is to make sure teams never feel that absence.