From my experience, accessibility at large orgs doesn't fail because people don't care. It fails because the people who care are speaking different languages.
Virgin Pulse was already pushing for better WCAG compliance when I joined, but the effort was stalling. Engineering leadership was struggling to normalize internal best practices, and the product team had little familiarity with responsive UI or resizable text. I came in to bridge that gap, taking a federated approach and building buy-in across both orgs rather than pushing mandates from the center. Then I gave both sides tools and a language they could share.
For 350+ engineers, I focused on the fundamental concepts behind Resize and Reflow, and the CSS modules that enable them. The training reoriented how they thought about layout: not just screen sizes, but the core goal of keeping content perceivable, understandable, and robust.
For 50+ designers and PMs, I focused on shared language, writing accessibility acceptance criteria, and annotation. That's where the disconnect usually lives. I built an annotation library for communicating testable, specific a11y AC that engineers could implement without guessing.
Together the two curricula reached 400+ people and became the foundation of Virgin Pulse's WCAG AA compliance strategy, a contractual Section 508 requirement the org had been struggling to fulfill before I joined.
As the team had needs, during this period, I also took on UX design work across multiple streams, including our pattern library team, gamification/rewards team, and platform team, which was working on a Partner Platform API documentation page.
My ability to communicate effectively with my technical colleagues helped me incorporate their technical guidance into our UX design process so that in the end, we delivered artifacts that not only met our UX goals, but also exceeded our accessibility, performance, and usability standards up to that point.