Design Partnership
How Workback ran Coursera's accessibility audit in hours, not weeks.
In November 2025, Coursera ran a paid audit partnership with Workback across their learner experience. Our computer-use agents drove end-to-end sessions through their authenticated products: sign-in, enrollment, payments, assessments.
14 authenticated learner journeys. Full audit in hours.
About Coursera
Coursera is one of the largest online learning platforms in the world, serving more than 170 million registered learners and partnering with leading universities and companies across 100+ countries. Founded in 2012 and listed on the NYSE since 2021, Coursera operates at the scale where accessibility compliance is both a legal obligation and a daily engineering problem.
The scope
Real product. Real sessions. Real depth.
Coursera chose the exact user journeys their annual accessibility audit covers: the workflows that matter most to learners, and the ones their compliance program depends on getting right. Workback audited all of them.
Our computer-use agents signed in as real learners and drove end-to-end sessions across the product: discovery, enrollment, payments, course home, assessments, grading, AI-powered coaching, and enterprise learning paths. Fourteen journeys in total. The full sweep finished in hours.
The same flows Coursera's annual accessibility audit covers.
End-to-end across the product, not weeks of scheduling and sampling.
Multi-step flows with conditional UI, auth state, and dynamic content.
Beyond what scanners reach
Accessibility issues hide where scanners can't go.
Static scanners read markup. They don't sign in. They don't fill out forms and wait for validation errors. They don't click through a multi-step enrollment, trigger a payment modal, or navigate a course with a logged-in learner's state. That's where the accessibility issues that actually affect real users live.
Workback's agents interact with the product the way a learner would, and surface the class of issues that only appear once something is actually using the page. Coursera's team singled this out as the difference that mattered.
Static scanners
- Stop at the login wall
- Can't fill forms or trigger validation
- Miss state-dependent and dynamic UI
Workback
- Signs in, enrolls, pays, completes assessments
- Exercises multi-step flows and conditional UI
- Surfaces issues only visible mid-interaction
At scale
Coursera's scale shaped how Workback handles authenticated sessions, dynamic UIs, and the journeys every learner completes. The product runs on what we learned there.