Design Systems
Accessibility by Design: Building Compliance Into the System, Not the Checklist
Accessibility by Design: Building Compliance Into the System, Not the Checklist
Role
Director of UX → Vice President of UX
Context
A communications platform serving Deaf and hard-of-hearing users across FCC-regulated B2C services and enterprise B2B products, where accessibility failures carried legal, financial, and reputational risk.
Mandate
Move accessibility from reactive audits and late-stage fixes into a foundational, system-level capability that scaled across products and teams.
Scope
Led accessibility strategy across 25+ products and platforms
Integrated WCAG standards into a shared design system
Partnered with Product, Engineering, Legal, and Compliance
Operated within strict regulatory and delivery constraints
Outcomes
Zero new accessibility issues across products
Embedding WCAG-compliant components into the system eliminated recurring accessibility regressions and reduced legal and compliance risk.
Faster product delivery through consistent, accessible foundations
A unified, accessible design system reduced duplicative work and accelerated design-to-development handoffs.
Consistent design system adopted across 20+ products
Shared components improved user experience quality and reduced engineering rework from inconsistent interfaces.
WCAG AA compliance with AAA targets where feasible
Achieving compliance as a default decreased risk and improved usability for people with varied abilities.
Raised product maturity with accessibility embedded in workflows
Product and Engineering integrated accessibility checkpoints into delivery, improving confidence in releases.
The Business Problem
Accessibility was treated as something to check after features shipped.
Teams relied on audits and point-in-time fixes, which meant the same issues resurfaced release after release. Engineers rebuilt components differently across products. Designers solved the same problems repeatedly. Compliance reviews slowed delivery and increased risk.
In a regulated environment serving users who relied on accessibility to use the product at all, this approach wasn’t sustainable.
The business needed accessibility to be:
Reliable
Repeatable
Built into how products were designed and delivered
Not something teams scrambled to fix at the end.
Led UX strategy, built the accessibility-first design system, and aligned cross-functional teams on implementation.
Led UX strategy, built the accessibility-first design system, and aligned cross-functional teams on implementation.
Led UX strategy, built the accessibility-first design system, and aligned cross-functional teams on implementation.
Constraints and Realities
Accessibility failures created regulatory and legal exposure
Products spanned multiple platforms with inconsistent implementations
Engineering teams moved quickly but lacked shared standards
Accessibility expertise lived in pockets, not in the system
The challenge wasn’t convincing people accessibility mattered.
It was making it impossible to forget.
Built documentation, governance, and training so accessibility remained embedded in the product expanded across 25+ platforms.
Built documentation, governance, and training so accessibility remained embedded in the product expanded across 25+ platforms.
Built documentation, governance, and training so accessibility remained embedded in the product expanded across 25+ platforms.
Strategic Decisions
01.
Treat Accessibility as Infrastructure
Instead of addressing accessibility through audits and remediation cycles, I made the decision to embed it directly into the design system.
If the components were accessible by default, teams couldn’t accidentally ship inaccessible experiences.
This shifted accessibility from a review activity to a design constraint.
What this required
Wireframing and prototyping
User Interface design for web and mobile apps
Usability testing and user feedback analysis
Interaction design and micro-animations
What this required
Wireframing and prototyping
User Interface design for web and mobile apps
Usability testing and user feedback analysis
Interaction design and micro-animations
What this required
Wireframing and prototyping
User Interface design for web and mobile apps
Usability testing and user feedback analysis
Interaction design and micro-animations
02.
02.
Standardize Before Scaling
Teams were solving the same accessibility problems in different ways across products.
I prioritized consolidation over customization by:
Reducing component variation
Enforcing shared patterns for navigation, forms, and interaction states
Creating a single source of truth teams could rely on
Consistency reduced cognitive load for users and rework for teams.
System impact
Wireframing and prototyping
User Interface design for web and mobile apps
Usability testing and user feedback analysis
Interaction design and micro-animations
System impact
Wireframing and prototyping
User Interface design for web and mobile apps
Usability testing and user feedback analysis
Interaction design and micro-animations
System impact
Wireframing and prototyping
User Interface design for web and mobile apps
Usability testing and user feedback analysis
Interaction design and micro-animations
03.
03.
Integrate Accessibility Into Delivery Workflows
Accessibility couldn’t live only in design files.
I worked with Product and Engineering to integrate accessibility checks into planning, build, and review workflows so it became part of how work moved through the system.
Teams didn’t need reminders. The process handled it.
Workflow changes
Wireframing and prototyping
User Interface design for web and mobile apps
Usability testing and user feedback analysis
Interaction design and micro-animations
Workflow changes
Wireframing and prototyping
User Interface design for web and mobile apps
Usability testing and user feedback analysis
Interaction design and micro-animations
Workflow changes
Wireframing and prototyping
User Interface design for web and mobile apps
Usability testing and user feedback analysis
Interaction design and micro-animations
What Changed
Accessibility shifted from reactive fixes to proactive design
Teams stopped re-introducing known issues
Compliance reviews became predictable instead of disruptive
Users experienced consistent, usable interfaces across platforms
Accessibility stopped slowing teams down.
It made delivery safer.
Why This Matters
In regulated environments, accessibility that depends on vigilance eventually fails.
The only approach that scales is one where accessibility is built into the system itself.
This work ensured accessibility didn’t rely on individual effort, memory, or advocacy. It became part of how the company built products.
That’s the difference between compliance theater and durable design.
More Projects
Design Systems
Accessibility by Design: Building Compliance Into the System, Not the Checklist
Accessibility by Design: Building Compliance Into the System, Not the Checklist
Role
Director of UX → Vice President of UX
Context
A communications platform serving Deaf and hard-of-hearing users across FCC-regulated B2C services and enterprise B2B products, where accessibility failures carried legal, financial, and reputational risk.
Mandate
Move accessibility from reactive audits and late-stage fixes into a foundational, system-level capability that scaled across products and teams.
Scope
Led accessibility strategy across 25+ products and platforms
Integrated WCAG standards into a shared design system
Partnered with Product, Engineering, Legal, and Compliance
Operated within strict regulatory and delivery constraints
Outcomes
Zero new accessibility issues across products
Embedding WCAG-compliant components into the system eliminated recurring accessibility regressions and reduced legal and compliance risk.
Faster product delivery through consistent, accessible foundations
A unified, accessible design system reduced duplicative work and accelerated design-to-development handoffs.
Consistent design system adopted across 20+ products
Shared components improved user experience quality and reduced engineering rework from inconsistent interfaces.
WCAG AA compliance with AAA targets where feasible
Achieving compliance as a default decreased risk and improved usability for people with varied abilities.
Raised product maturity with accessibility embedded in workflows
Product and Engineering integrated accessibility checkpoints into delivery, improving confidence in releases.
The Business Problem
Accessibility was treated as something to check after features shipped.
Teams relied on audits and point-in-time fixes, which meant the same issues resurfaced release after release. Engineers rebuilt components differently across products. Designers solved the same problems repeatedly. Compliance reviews slowed delivery and increased risk.
In a regulated environment serving users who relied on accessibility to use the product at all, this approach wasn’t sustainable.
The business needed accessibility to be:
Reliable
Repeatable
Built into how products were designed and delivered
Not something teams scrambled to fix at the end.
Led UX strategy, built the accessibility-first design system, and aligned cross-functional teams on implementation.
Led UX strategy, built the accessibility-first design system, and aligned cross-functional teams on implementation.
Led UX strategy, built the accessibility-first design system, and aligned cross-functional teams on implementation.
Constraints and Realities
Accessibility failures created regulatory and legal exposure
Products spanned multiple platforms with inconsistent implementations
Engineering teams moved quickly but lacked shared standards
Accessibility expertise lived in pockets, not in the system
The challenge wasn’t convincing people accessibility mattered.
It was making it impossible to forget.
Built documentation, governance, and training so accessibility remained embedded in the product expanded across 25+ platforms.
Built documentation, governance, and training so accessibility remained embedded in the product expanded across 25+ platforms.
Built documentation, governance, and training so accessibility remained embedded in the product expanded across 25+ platforms.
Strategic Decisions
01.
Treat Accessibility as Infrastructure
Instead of addressing accessibility through audits and remediation cycles, I made the decision to embed it directly into the design system.
If the components were accessible by default, teams couldn’t accidentally ship inaccessible experiences.
This shifted accessibility from a review activity to a design constraint.
What this required
Wireframing and prototyping
User Interface design for web and mobile apps
Usability testing and user feedback analysis
Interaction design and micro-animations
What this required
Wireframing and prototyping
User Interface design for web and mobile apps
Usability testing and user feedback analysis
Interaction design and micro-animations
What this required
Wireframing and prototyping
User Interface design for web and mobile apps
Usability testing and user feedback analysis
Interaction design and micro-animations
02.
02.
Standardize Before Scaling
Teams were solving the same accessibility problems in different ways across products.
I prioritized consolidation over customization by:
Reducing component variation
Enforcing shared patterns for navigation, forms, and interaction states
Creating a single source of truth teams could rely on
Consistency reduced cognitive load for users and rework for teams.
System impact
Wireframing and prototyping
User Interface design for web and mobile apps
Usability testing and user feedback analysis
Interaction design and micro-animations
System impact
Wireframing and prototyping
User Interface design for web and mobile apps
Usability testing and user feedback analysis
Interaction design and micro-animations
System impact
Wireframing and prototyping
User Interface design for web and mobile apps
Usability testing and user feedback analysis
Interaction design and micro-animations
03.
03.
Integrate Accessibility Into Delivery Workflows
Accessibility couldn’t live only in design files.
I worked with Product and Engineering to integrate accessibility checks into planning, build, and review workflows so it became part of how work moved through the system.
Teams didn’t need reminders. The process handled it.
Workflow changes
Wireframing and prototyping
User Interface design for web and mobile apps
Usability testing and user feedback analysis
Interaction design and micro-animations
Workflow changes
Wireframing and prototyping
User Interface design for web and mobile apps
Usability testing and user feedback analysis
Interaction design and micro-animations
Workflow changes
Wireframing and prototyping
User Interface design for web and mobile apps
Usability testing and user feedback analysis
Interaction design and micro-animations
What Changed
Accessibility shifted from reactive fixes to proactive design
Teams stopped re-introducing known issues
Compliance reviews became predictable instead of disruptive
Users experienced consistent, usable interfaces across platforms
Accessibility stopped slowing teams down.
It made delivery safer.
Why This Matters
In regulated environments, accessibility that depends on vigilance eventually fails.
The only approach that scales is one where accessibility is built into the system itself.
This work ensured accessibility didn’t rely on individual effort, memory, or advocacy. It became part of how the company built products.
That’s the difference between compliance theater and durable design.
More Projects
Design Systems
Accessibility by Design: Building Compliance Into the System, Not the Checklist
Accessibility by Design: Building Compliance Into the System, Not the Checklist
Role
Director of UX → Vice President of UX
Context
A communications platform serving Deaf and hard-of-hearing users across FCC-regulated B2C services and enterprise B2B products, where accessibility failures carried legal, financial, and reputational risk.
Mandate
Move accessibility from reactive audits and late-stage fixes into a foundational, system-level capability that scaled across products and teams.
Scope
Led accessibility strategy across 25+ products and platforms
Integrated WCAG standards into a shared design system
Partnered with Product, Engineering, Legal, and Compliance
Operated within strict regulatory and delivery constraints
Outcomes
Zero new accessibility issues across products
Embedding WCAG-compliant components into the system eliminated recurring accessibility regressions and reduced legal and compliance risk.
Faster product delivery through consistent, accessible foundations
A unified, accessible design system reduced duplicative work and accelerated design-to-development handoffs.
Consistent design system adopted across 20+ products
Shared components improved user experience quality and reduced engineering rework from inconsistent interfaces.
WCAG AA compliance with AAA targets where feasible
Achieving compliance as a default decreased risk and improved usability for people with varied abilities.
Raised product maturity with accessibility embedded in workflows
Product and Engineering integrated accessibility checkpoints into delivery, improving confidence in releases.
The Business Problem
Accessibility was treated as something to check after features shipped.
Teams relied on audits and point-in-time fixes, which meant the same issues resurfaced release after release. Engineers rebuilt components differently across products. Designers solved the same problems repeatedly. Compliance reviews slowed delivery and increased risk.
In a regulated environment serving users who relied on accessibility to use the product at all, this approach wasn’t sustainable.
The business needed accessibility to be:
Reliable
Repeatable
Built into how products were designed and delivered
Not something teams scrambled to fix at the end.
Led UX strategy, built the accessibility-first design system, and aligned cross-functional teams on implementation.
Led UX strategy, built the accessibility-first design system, and aligned cross-functional teams on implementation.
Led UX strategy, built the accessibility-first design system, and aligned cross-functional teams on implementation.
Constraints and Realities
Accessibility failures created regulatory and legal exposure
Products spanned multiple platforms with inconsistent implementations
Engineering teams moved quickly but lacked shared standards
Accessibility expertise lived in pockets, not in the system
The challenge wasn’t convincing people accessibility mattered.
It was making it impossible to forget.
Built documentation, governance, and training so accessibility remained embedded in the product expanded across 25+ platforms.
Built documentation, governance, and training so accessibility remained embedded in the product expanded across 25+ platforms.
Built documentation, governance, and training so accessibility remained embedded in the product expanded across 25+ platforms.
Strategic Decisions
01.
Treat Accessibility as Infrastructure
Instead of addressing accessibility through audits and remediation cycles, I made the decision to embed it directly into the design system.
If the components were accessible by default, teams couldn’t accidentally ship inaccessible experiences.
This shifted accessibility from a review activity to a design constraint.
What this required
Wireframing and prototyping
User Interface design for web and mobile apps
Usability testing and user feedback analysis
Interaction design and micro-animations
What this required
Wireframing and prototyping
User Interface design for web and mobile apps
Usability testing and user feedback analysis
Interaction design and micro-animations
What this required
Wireframing and prototyping
User Interface design for web and mobile apps
Usability testing and user feedback analysis
Interaction design and micro-animations
02.
02.
Standardize Before Scaling
Teams were solving the same accessibility problems in different ways across products.
I prioritized consolidation over customization by:
Reducing component variation
Enforcing shared patterns for navigation, forms, and interaction states
Creating a single source of truth teams could rely on
Consistency reduced cognitive load for users and rework for teams.
System impact
Wireframing and prototyping
User Interface design for web and mobile apps
Usability testing and user feedback analysis
Interaction design and micro-animations
System impact
Wireframing and prototyping
User Interface design for web and mobile apps
Usability testing and user feedback analysis
Interaction design and micro-animations
System impact
Wireframing and prototyping
User Interface design for web and mobile apps
Usability testing and user feedback analysis
Interaction design and micro-animations
03.
03.
Integrate Accessibility Into Delivery Workflows
Accessibility couldn’t live only in design files.
I worked with Product and Engineering to integrate accessibility checks into planning, build, and review workflows so it became part of how work moved through the system.
Teams didn’t need reminders. The process handled it.
Workflow changes
Wireframing and prototyping
User Interface design for web and mobile apps
Usability testing and user feedback analysis
Interaction design and micro-animations
Workflow changes
Wireframing and prototyping
User Interface design for web and mobile apps
Usability testing and user feedback analysis
Interaction design and micro-animations
Workflow changes
Wireframing and prototyping
User Interface design for web and mobile apps
Usability testing and user feedback analysis
Interaction design and micro-animations
What Changed
Accessibility shifted from reactive fixes to proactive design
Teams stopped re-introducing known issues
Compliance reviews became predictable instead of disruptive
Users experienced consistent, usable interfaces across platforms
Accessibility stopped slowing teams down.
It made delivery safer.
Why This Matters
In regulated environments, accessibility that depends on vigilance eventually fails.
The only approach that scales is one where accessibility is built into the system itself.
This work ensured accessibility didn’t rely on individual effort, memory, or advocacy. It became part of how the company built products.
That’s the difference between compliance theater and durable design.