Introduction
Guardian Life is a leading insurance and wealth management provider with a workforce of over 7,000 employees, including more than 2,000 developers. Guardian is deeply committed to digital inclusion, operating at an advanced level on the Digital Accessibility Maturity Model (Level 4, compared to an industry average of Level 2). To maintain and scale this high standard, Guardian Life sought to modernize its approach to web and mobile accessibility.
Breaking the bottlenecks of manual accessibility checks
Despite having a highly mature digital accessibility program, Guardian Life wanted to move away from individual “heroics” and reliance on specialized knowledge. Their goal was to build a structured, automated process that integrated accessibility into the earliest stages of the Software Development Life Cycle (SDLC)—a true “shift-left” approach.
Before BrowserStack, they faced several key limitations:
- Design bottlenecks: Designers were manually creating accessibility annotations. This process was slow and heavily dependent on each designer’s understanding of accessibility guidelines.
- Lack of developer tooling: Developers lacked robust, automated checks while writing React or Angular code. The team needed a reliable linter that went beyond basic open-source capabilities to catch complex ARIA attribute errors and integrate with CI/CD pipelines before code check-in.
- The remote device impediment: Guardian Life’s developers work remotely. When a bug required testing a screen reader on a specific device (like an iPhone), it could only be assigned to a developer who physically owned that device. This created massive logistical bottlenecks.



