Designing for Inclusion: Embedding Accessibility into ASSA ABLOY’s Digital Product Ecosystem

Designing for Inclusion: Embedding Accessibility into ASSA ABLOY’s Digital Product Ecosystem

This project documents how I led the effort to embed accessibility into ASSA ABLOY's digital teams. Accessibility was often misunderstood, inconsistently applied, and lacked ownership, leaving both product teams and users vulnerable. The initiative focused on aligning teams, building internal capabilities, and embedding accessibility into every stage of the product lifecycle.

Role

Accessibility Advocate, ASSA ABLOY

Scope

Organization-wide Accessibility Strategy

Certification

CPACC (IAAP)

My Role

As a CPACC-certified Accessibility Advocate, in an organization with dozens of products, geographically dispersed teams, and different levels of accessibility maturity, I had to meet people where they were and guide them forward…

Step by step!

My work spanned strategy, education, culture-building, and hands-on execution:

  • Designing our accessibility strategy and roadmap

  • Creating centralized resources and support systems

  • Equipping teams with tools, training, and workflows

  • Leading assessments and offering strategic recommendations

Assessment

Understanding the Current Landscape

Before proposing any solution, I had to understand the real state of accessibility within the organization, not just what the documents or leaders said, but how people across disciplines experienced it on the ground.

The Survey

We designed and distributed a comprehensive survey to stakeholders across the organization, from designers and developers to product managers, QA, and leadership. The survey aimed to capture insights on:

  • The products different divisions were working on.

  • The level of familiarity with accessibility and relevant guidelines.

  • Who was responsible for accessibility in each division.

  • Current steps, if any, taken to ensure deliverables meet accessibility standards.

  • The priority placed on accessibility across divisions.

  • Challenges faced in integrating accessibility.

  • Specific resources and support needed from the organization to better integrate accessibility into workflows.

People were curious. They wanted to talk about accessibility. They just hadn’t been asked before!

Key Insights

There was no clear ownership of accessibility in most teams.

Teams had uneven levels of knowledge, some were unaware of basic standards.

Interest was high, but so was confusion and overwhelm.

Accessibility was often reactive: only considered when issues were reported externally.

People didn’t feel confident in how to start, or how to advocate for accessibility

The first thing we needed wasn’t just a checklist. We needed connection, clarity, and confidence.

Network

Creating the Digital Accessibility Network

Out of this need for connection came our first system:
The Digital Accessibility Network, a dedicated space for all things accessibility.

This wasn’t just a Slack channel. It was a cross-functional community hub:

  • A central library of best practices, templates, and learning tools

  • A Q&A and peer support space

  • A place to celebrate wins, ask hard questions, and share blockers

Building a Culture of Champions

We also, identified accessibility experts from the survey participants and invited them to become A11y champions within the network. These champions played a crucial role in supporting others, offering guidance, and fostering a culture of accessibility across divisions.

Training

Foundational Resources and Practical Support

We focused on providing foundational resources and practical support for everyone, regardless of their level of expertise in accessibility.

Learning Module

We created a recorded learning module that teams could take on their own schedule.

It included:

  1. Introduction to Accessibility

  1. Why Should We Care About Digital Accessibility? The business, ethical, and legal reasons behind accessibility.

  1. POUR Principles

  1. Overview of Accessibility Standards and Legislation: An introduction to standards like Section 508, ADA, EAA, and others.

  1. How to Be Accessible: A step-by-step guide with resources and tools for each step, and defining the responsibilities of different team members at each step.

Simplifying WCAG 2.2 Success Criteria

To give teams a practical starting point, We simplified the WCAG 2.2 success criteria for Level A and Level AA and categorized them based on the POUR principles

Tools

Training People to Use the Tools

Once teams were equipped with knowledge, we gave them the means to put it into action:

  • Step-by-step guides to install and use Chrome accessibility extensions

  • Introduction to screen readers like NVDA and VoiceOver

  • How to test products using only a keyboard

  • Color contrast analysis

  • Focus order and tab logic

Audits

Conducting Accessibility Assessments

In addition to equipping teams with tools and training, I played a hands-on role in helping them improve their products through accessibility assessments.

For each product assessed, I created a detailed report that outlined accessibility issues, explained their impact, and offered practical solutions aligned with WCAG 2.2 standards.

But I didn’t just hand over the reports and walk away. I held working sessions with each team to walk through the findings, answer questions, and guide them through remediation. We reviewed issue severity, discussed feasible fixes within their technical and design constraints, and often paired the changes with ongoing sprint work to ensure accessibility was integrated, not bolted on.

Reflections & Takeaways

What I Took Away!

Accessibility Is a Continuous Commitment

Building accessibility into an organization isn’t something you do once and mark as complete. It’s a continuous process of raising awareness, shifting mindsets, and making inclusion part of everyday decision-making. Awareness isn’t a milestone; it’s a muscle that needs regular strengthening.

People Just Need to Know Where to Start

Throughout this journey, one of the biggest lessons I learned is that most people want to do the right thing, they just need clarity on how to start. Abstract standards and technical checklists aren’t enough. What really helps is providing real-world examples, showing teams how accessibility applies to their work in context, and giving them a concrete first step.

Confidence Grows When Progress Is Visible

I saw how powerful it can be to celebrate small wins. Recognizing progress, even if it's just adding alt text or fixing a focus state, builds confidence and reinforces that accessibility isn’t about perfection; it’s about progress.

Let's Collaborate

Let's talk about a project,
collaboration or an idea you may have

Let's Collaborate

Let's talk about a project,
collaboration or an idea you may have

Let's Collaborate

Let's talk about a project,
collaboration or an idea you may have

Let's Collaborate

Let's talk about a project,
collaboration or an idea you may have