What it is
Accessibility is a design-system problem as much as a per-page one. If focus rings, contrast and interactive states are decided once, in tokens and components, every screen that uses them inherits the right behavior for free.
How I approach it
I audit components and flows against WCAG 2.2 AA, then fix the causes rather than the symptoms: focus and state styling promoted into tokens, contrast checked at the palette level, keyboard and screen-reader behavior verified on real assistive technology. Findings are written so a designer and a developer can each see their part of the fix.
I’ve practiced inclusive design since the early 2000s, back when it mostly meant semantic HTML and keyboard order — the foundations haven’t changed, the tooling has gotten much better.
Common problems I solve
- Focus styling that’s removed for looks and never replaced.
- Color palettes that fail contrast before a single component is built.
- Components that work with a mouse but trap or confuse keyboard and screen-reader users.
- Accessibility treated as a last-minute audit instead of a property of the system.
On a multi-brand e-commerce program I led the push to get several storefronts to WCAG AA — and kept them there by moving the rules into shared components.