Bupa resolves 50% accessibility issues in 3 months with BrowserStack | BrowserStack
Bupa resolves 50% accessibility issues in 3 months with BrowserStack
70%
Manual testing effort reduced
50%
Faster issue turnaround time
30%
Less developer remediation time
It’s not about detect and fix anymore — it’s about doing it right the first time. Accessibility-first is now part of how we design and build, and it’s much cheaper to fix issues early than late.
Shivaprakash Moolya
Head of Testing, Bupa
Industry
Hospitals and Health Care
Location
London, England
Products
[Accessibility](/content/accessibility "Accessibility"/index.html)
[Website Scanner](/content/website-scanner "Website Scanner"/index.html)
[Automate](/content/automate "Automate"/index.html)
Introduction
Bupa, a leading international healthcare provider, runs a digital estate spanning thousands of pages — built up over years of legacy development alongside a constant pipeline of new features. With releases shipping roughly every two weeks, the business needed to prove, continuously, that every page met accessibility standards who rely on its services.
Manual accessibility testing couldn’t keep pace. By adopting BrowserStack Accessibility, powered by the Spectra™ rule engine, Bupa’s testing, development, and design teams shifted accessibility left — cutting manual effort, accelerating fixes, and fixing 50% of all outstanding accessibility issues in just three months.
The challenge
Manual testing couldn’t scale with the speed of delivery
Bupa’s QA team had been running accessibility testing manually, across an estate of more than 3,000 pages, using a patchwork of disconnected tools. As release cycles accelerated, the gap between testing capacity and delivery speed widened into a real business risk.
- Slow, labour-intensive testing- Manual reviews of a digital estate this size were time-consuming and inconsistent, and defects often took longer than expected to triage, fix, and retest.
- Compliance uncertainty- As a healthcare provider, Bupa needed confidence that business-critical releases met accessibility standards — both as a regulatory obligation and as a commitment to serving all users.
- Inconsistent methods across teams- Reliance on non-standard testing approaches created inconsistency between teams, added day-to-day pressure, and raised the risk of errors slipping through.
- Legacy debt at scale- With years of existing pages to remediate alongside new development, Bupa needed a way to validate fixes confidently across a sprawling, constantly changing estate — not a one-off scan.
Shivaprakash Moolya
Head of Testing, Bupa
The solution
An all-in-one platform that fit straight into Bupa’s existing workflow
Bupa had already used BrowserStack for more than five years across Live, Automate, and Percy. As accessibility became a board-level priority, the team evaluated several dedicated accessibility tools before selecting BrowserStack Accessibility Testing.
- Fast, confident evaluation- The platform stood out for how quickly the team could run a scan and trust the result. Trend analysis and reporting features weren’t provided by other tools evaluated at the time, and because Bupa already had BrowserStack in its vendor ecosystem, procurement and data assessment moved far faster than a typical enterprise rollout.
- The Spectra™ rule engine- Bupa called out the accuracy of the underlying scan technology as a clear differentiator versus competing tools, giving the team confidence in results before standardizing on it company-wide.
- Actionable, developer-ready reporting- Each issue report mapped directly to the WCAG guideline breached, identified the specific element that caused it, and provided AI-powered remediation guidance.
- Easy, wide rollout- The tool’s ease of use let Bupa roll it out to a broad group of test engineers, developers, and designers in a short period, rather than restricting it to a small specialist team.
Shivaprakash Moolya
Head of Testing, Bupa
The impact
Faster fixes, fewer regressions, and accessibility built into the culture
Within months, BrowserStack Accessibility changed how Bupa’s teams worked, not just what they tested.
- 50% of issues fixed in 3 months- Through a rigorous, repeatable cycle, Bupa closed half of its outstanding accessibility backlog in a single quarter — without slowing down its broader growth and delivery commitments.
- Major reduction in manual effort- Scanning, triaging, and reporting that once took up to half a day per person across 3,000+ pages was significantly compressed, freeing test engineers to focus on releasing new features instead of doing repetitive manual checks in every two-week release cycle.
- Shift-left culture change- Developers and designers began using the toolkit early in the lifecycle, catching issues during build rather than after release.
- Quantified KPI improvements- Bupa tracked measurable gains across the delivery pipeline:
- ~70% reduction in manual testing effort (scanning, finding, and costing issues)
- ~30% reduction in developer remediation time, thanks to detailed, actionable reports
- ~50% improvement in overall turnaround time from detection to resolution
- Zero infrastructure overhead, since the platform is fully managed by BrowserStack
- Caught what manual testing missed- One critical issue, present across roughly 80% of the site’s pages, was identified by the Spectra™ engine after going undetected in manual human review — a single catch that protected the majority of Bupa’s digital estate from non-compliance.
- Renewed stakeholder confidence- Regular automated scans inside the two-week release cycle gave leadership ongoing assurance that new changes wouldn’t introduce regressions, replacing a stressful, risk-based approach with measurable proof of compliance.
Shivaprakash Moolya
Head of Testing, Bupa