Strategy & Innovation

Accessibility as a Competitive Edge

Accessibility in digital products is often treated like a box to check. Teams tweak a few colors, bump up the font size, and call it a day. But true accessibility is far more than that. It’s about designing experiences that adapt to a range of abilities, technologies, and contexts.

During my time working on products built specifically for users with disabilities, accessibility wasn’t just an afterthought. It was a requirement. Every interface had to work seamlessly with screen readers, respond to native operating system settings, and function consistently across multiple platforms. These aren’t “nice-to-have” features. They are the difference between whether someone can actually use the product or not.

Role

Director/VP of UX

Duration

Throughout 3 Years

Contribution

UX Strategy, Design Systems, Cross-Functional Alignment

Target Audience

Org facing compliance risks and usability challenges in an regulated environment

Unified design system

Consistent design system and practices were adopted across all 25+ products

WCAG Compliance

Core components WCAG AA-compliant, with AAA targets met where feasible

Streamlined delivery

Cutting our design-to-dev cycle time and reducing duplicative work with improved communication

Raised product maturity

Product and Engineering embracing a system-first development approach

PROBLEM

Uncovering the Stakes

The platform served a wide range of users but didn’t necessarily meet accessibility standards. This created risks: legal exposure, user frustration, and a brand that appeared out of touch. They needed more than quick fixes. We needed a design system that was accessible from the start and easy to maintain as the product evolved. The key issue was figuring out how to make all of this repeatable across multiple products without limiting functionality or drastically increasing development time.

Led UX strategy, built the accessibility-first design system, and aligned cross-functional teams on implementation.

APPROACH

How We Crafted a Systematic Solution

I started by reviewing commonly used design systems such as Material, Carbon, and Apple UI. I had built design systems in the past, which made it easier to know what I was looking for, but I was surprised to find there wasn’t a consistent approach that truly focused on people who needed accessibility features. In most cases, contrasts didn’t even meet AA standards, fonts were difficult to read, and there was little attention given to advanced needs such as screen reader compatibility.

Next, I dove deeper into WCAG guidelines, focusing on the differences between AA and AAA requirements. I challenged my designers to aim for AAA while still creating a consistent system that would scale over time. We began with an audit of our existing products, identifying every component we would need and building an icon library to maintain consistency across products. This proved more difficult than expected due to the varying ways each product had been developed.

01.

Set the Foundation

Set the Foundation

Set the Foundation

Established an accessibility-first design system that as 100% WCAG AA compliant into every component. Nearly 80% was AAA.

02.

Collaborated Across Teams

Collaborated Across Teams

Collaborated Across Teams

Worked with engineering and product management to integrate accessibility checkpoints into the development lifecycle.

03.

Validated with Research

Validated with Research

Validated with Research

Tested designs with users of varying abilities to identify issues early and ensure real-world usability.

04.

Operationalized for Scale

Operationalized for Scale

Operationalized for Scale

Delivered documentation, and governance to keep accessibility embedded in future product development.

Four of us designed the components, each testing contrast ratios and prototyping how they worked in real experiences. We held design reviews and daily check-ins to track progress, all while balancing our regular day-to-day duties. It was actually pretty impressive how quickly we were able to get it up and running.

With the foundation of the design system in place, we began using it in our prototypes and gathering user feedback. We also ran it through testing platforms and optimized it based on what we learned. Each component included documentation on its usage, functionality, and use cases. This ensured future designers and developers would have the information they needed to work efficiently.

OUTCOMES

NO ISSUES MEAN A SILENT SUCCESS

The results spoke for themselves. The platform achieved full WCAG compliance and reduced design-to-development handoff time by nearly 30%. Usability scores improved across all user groups, and accessibility became a standard part of how the team builds. Beyond compliance, the project shifted the company’s mindset, making accessibility part of its identity rather than just a box to check.

The only miss, though not for lack of trying, was that we weren’t able to build it out in a repository such as Storybook for all developers to use. By the time we considered it, many products were already too far along, and doing so would have slowed teams down and required significant rework. Instead, we made adjustments piece by piece as time allowed. Either way, this was a huge win for both the company and our users.

Built documentation, governance, and training so accessibility remained embedded in the product expanded across 25+ platforms.

WHY IT MATTERS

BEING INCLUSIVE FOR YOUR USERS IS NEVER A BAD THING

Accessibility is more than compliance. It is about designing products that include everyone and create a better experience for all users. This project proved that when accessibility is part of the process rather than an add-on at the end, it delivers value on multiple levels.

Every product began with the same inclusive foundation. Teams gained confidence because accessibility checks were built into their workflow. The business avoided legal risk and strengthened its brand reputation as an inclusive leader in its space.

By making accessibility a core design principle, the company did more than fix a problem. It created a long-term advantage that continues to drive both user satisfaction and business success.

Strategy & Innovation

Accessibility as a Competitive Edge

Accessibility in digital products is often treated like a box to check. Teams tweak a few colors, bump up the font size, and call it a day. But true accessibility is far more than that. It’s about designing experiences that adapt to a range of abilities, technologies, and contexts.

During my time working on products built specifically for users with disabilities, accessibility wasn’t just an afterthought. It was a requirement. Every interface had to work seamlessly with screen readers, respond to native operating system settings, and function consistently across multiple platforms. These aren’t “nice-to-have” features. They are the difference between whether someone can actually use the product or not.

Role

Director/VP of UX

Duration

Throughout 3 Years

Contribution

UX Strategy, Design Systems, Cross-Functional Alignment

Target Audience

Org facing compliance risks and usability challenges in an regulated environment

Unified design system

Consistent design system and practices were adopted across all 25+ products

WCAG Compliance

Core components WCAG AA-compliant, with AAA targets met where feasible

Streamlined delivery

Cutting our design-to-dev cycle time and reducing duplicative work with improved communication

Raised product maturity

Product and Engineering embracing a system-first development approach

PROBLEM

Uncovering the Stakes

The platform served a wide range of users but didn’t necessarily meet accessibility standards. This created risks: legal exposure, user frustration, and a brand that appeared out of touch. They needed more than quick fixes. We needed a design system that was accessible from the start and easy to maintain as the product evolved. The key issue was figuring out how to make all of this repeatable across multiple products without limiting functionality or drastically increasing development time.

Led UX strategy, built the accessibility-first design system, and aligned cross-functional teams on implementation.

APPROACH

How We Crafted a Systematic Solution

I started by reviewing commonly used design systems such as Material, Carbon, and Apple UI. I had built design systems in the past, which made it easier to know what I was looking for, but I was surprised to find there wasn’t a consistent approach that truly focused on people who needed accessibility features. In most cases, contrasts didn’t even meet AA standards, fonts were difficult to read, and there was little attention given to advanced needs such as screen reader compatibility.

Next, I dove deeper into WCAG guidelines, focusing on the differences between AA and AAA requirements. I challenged my designers to aim for AAA while still creating a consistent system that would scale over time. We began with an audit of our existing products, identifying every component we would need and building an icon library to maintain consistency across products. This proved more difficult than expected due to the varying ways each product had been developed.

01.

Set the Foundation

Set the Foundation

Set the Foundation

Established an accessibility-first design system that as 100% WCAG AA compliant into every component. Nearly 80% was AAA.

02.

Collaborated Across Teams

Collaborated Across Teams

Collaborated Across Teams

Worked with engineering and product management to integrate accessibility checkpoints into the development lifecycle.

03.

Validated with Research

Validated with Research

Validated with Research

Tested designs with users of varying abilities to identify issues early and ensure real-world usability.

04.

Operationalized for Scale

Operationalized for Scale

Operationalized for Scale

Delivered documentation, and governance to keep accessibility embedded in future product development.

Four of us designed the components, each testing contrast ratios and prototyping how they worked in real experiences. We held design reviews and daily check-ins to track progress, all while balancing our regular day-to-day duties. It was actually pretty impressive how quickly we were able to get it up and running.

With the foundation of the design system in place, we began using it in our prototypes and gathering user feedback. We also ran it through testing platforms and optimized it based on what we learned. Each component included documentation on its usage, functionality, and use cases. This ensured future designers and developers would have the information they needed to work efficiently.

OUTCOMES

NO ISSUES MEAN A SILENT SUCCESS

The results spoke for themselves. The platform achieved full WCAG compliance and reduced design-to-development handoff time by nearly 30%. Usability scores improved across all user groups, and accessibility became a standard part of how the team builds. Beyond compliance, the project shifted the company’s mindset, making accessibility part of its identity rather than just a box to check.

The only miss, though not for lack of trying, was that we weren’t able to build it out in a repository such as Storybook for all developers to use. By the time we considered it, many products were already too far along, and doing so would have slowed teams down and required significant rework. Instead, we made adjustments piece by piece as time allowed. Either way, this was a huge win for both the company and our users.

Built documentation, governance, and training so accessibility remained embedded in the product expanded across 25+ platforms.

WHY IT MATTERS

BEING INCLUSIVE FOR YOUR USERS IS NEVER A BAD THING

Accessibility is more than compliance. It is about designing products that include everyone and create a better experience for all users. This project proved that when accessibility is part of the process rather than an add-on at the end, it delivers value on multiple levels.

Every product began with the same inclusive foundation. Teams gained confidence because accessibility checks were built into their workflow. The business avoided legal risk and strengthened its brand reputation as an inclusive leader in its space.

By making accessibility a core design principle, the company did more than fix a problem. It created a long-term advantage that continues to drive both user satisfaction and business success.

Strategy & Innovation

Accessibility as a Competitive Edge

Accessibility in digital products is often treated like a box to check. Teams tweak a few colors, bump up the font size, and call it a day. But true accessibility is far more than that. It’s about designing experiences that adapt to a range of abilities, technologies, and contexts.

During my time working on products built specifically for users with disabilities, accessibility wasn’t just an afterthought. It was a requirement. Every interface had to work seamlessly with screen readers, respond to native operating system settings, and function consistently across multiple platforms. These aren’t “nice-to-have” features. They are the difference between whether someone can actually use the product or not.

Role

Director/VP of UX

Duration

Throughout 3 Years

Contribution

UX Strategy, Design Systems, Cross-Functional Alignment

Target Audience

Org facing compliance risks and usability challenges in an regulated environment

Unified design system

Consistent design system and practices were adopted across all 25+ products

WCAG Compliance

Core components WCAG AA-compliant, with AAA targets met where feasible

Streamlined delivery

Cutting our design-to-dev cycle time and reducing duplicative work with improved communication

Raised product maturity

Product and Engineering embracing a system-first development approach

PROBLEM

Uncovering the Stakes

The platform served a wide range of users but didn’t necessarily meet accessibility standards. This created risks: legal exposure, user frustration, and a brand that appeared out of touch. They needed more than quick fixes. We needed a design system that was accessible from the start and easy to maintain as the product evolved. The key issue was figuring out how to make all of this repeatable across multiple products without limiting functionality or drastically increasing development time.

Led UX strategy, built the accessibility-first design system, and aligned cross-functional teams on implementation.

APPROACH

How We Crafted a Systematic Solution

I started by reviewing commonly used design systems such as Material, Carbon, and Apple UI. I had built design systems in the past, which made it easier to know what I was looking for, but I was surprised to find there wasn’t a consistent approach that truly focused on people who needed accessibility features. In most cases, contrasts didn’t even meet AA standards, fonts were difficult to read, and there was little attention given to advanced needs such as screen reader compatibility.

Next, I dove deeper into WCAG guidelines, focusing on the differences between AA and AAA requirements. I challenged my designers to aim for AAA while still creating a consistent system that would scale over time. We began with an audit of our existing products, identifying every component we would need and building an icon library to maintain consistency across products. This proved more difficult than expected due to the varying ways each product had been developed.

01.

Set the Foundation

Set the Foundation

Set the Foundation

Established an accessibility-first design system that as 100% WCAG AA compliant into every component. Nearly 80% was AAA.

02.

Collaborated Across Teams

Collaborated Across Teams

Collaborated Across Teams

Worked with engineering and product management to integrate accessibility checkpoints into the development lifecycle.

03.

Validated with Research

Validated with Research

Validated with Research

Tested designs with users of varying abilities to identify issues early and ensure real-world usability.

04.

Operationalized for Scale

Operationalized for Scale

Operationalized for Scale

Delivered documentation, and governance to keep accessibility embedded in future product development.

Four of us designed the components, each testing contrast ratios and prototyping how they worked in real experiences. We held design reviews and daily check-ins to track progress, all while balancing our regular day-to-day duties. It was actually pretty impressive how quickly we were able to get it up and running.

With the foundation of the design system in place, we began using it in our prototypes and gathering user feedback. We also ran it through testing platforms and optimized it based on what we learned. Each component included documentation on its usage, functionality, and use cases. This ensured future designers and developers would have the information they needed to work efficiently.

OUTCOMES

NO ISSUES MEAN A SILENT SUCCESS

The results spoke for themselves. The platform achieved full WCAG compliance and reduced design-to-development handoff time by nearly 30%. Usability scores improved across all user groups, and accessibility became a standard part of how the team builds. Beyond compliance, the project shifted the company’s mindset, making accessibility part of its identity rather than just a box to check.

The only miss, though not for lack of trying, was that we weren’t able to build it out in a repository such as Storybook for all developers to use. By the time we considered it, many products were already too far along, and doing so would have slowed teams down and required significant rework. Instead, we made adjustments piece by piece as time allowed. Either way, this was a huge win for both the company and our users.

Built documentation, governance, and training so accessibility remained embedded in the product expanded across 25+ platforms.

WHY IT MATTERS

BEING INCLUSIVE FOR YOUR USERS IS NEVER A BAD THING

Accessibility is more than compliance. It is about designing products that include everyone and create a better experience for all users. This project proved that when accessibility is part of the process rather than an add-on at the end, it delivers value on multiple levels.

Every product began with the same inclusive foundation. Teams gained confidence because accessibility checks were built into their workflow. The business avoided legal risk and strengthened its brand reputation as an inclusive leader in its space.

By making accessibility a core design principle, the company did more than fix a problem. It created a long-term advantage that continues to drive both user satisfaction and business success.