Most organizations treat accessibility like a final exam. Build the course, then run it through a checker, fix what’s flagged, and ship. The result is predictable: expensive retrofits, inconsistent compliance, and a team that sees accessibility as a burden rather than a design constraint.
When I inherited the accessibility initiative at Colibri — 45+ courses that needed to meet WCAG 2.1 AAA — I knew the audit-and-fix approach wouldn’t scale. The math didn’t work. Retrofitting one course took weeks. We needed a fundamentally different approach.
The shift was reframing accessibility from a compliance task to an architectural concern. Just like you don’t add the foundation to a building after the walls are up, you shouldn’t add accessibility after the course is built. It needs to be structural.
I designed a three-layer system. Layer one: a standards framework that translated WCAG criteria into actionable guidelines specific to our content types. Not ‘ensure sufficient contrast’ but ‘use these specific color pairings for these content elements.’ Specific, actionable, impossible to misinterpret.
Layer two: automated tooling integrated into the build pipeline. Before any course reached human review, it passed through automated checks that caught the mechanical violations — missing alt text, contrast failures, heading hierarchy issues. This freed up QA reviewers to focus on the judgment calls that machines can’t make.
Layer three: training that changed how the team thinks. Not ‘here are the rules’ but ‘here’s who your learners are and why this matters.’ When people understand the why, they start catching accessibility issues that no checklist covers.
The result: 45+ courses at AAA compliance with zero post-launch complaints. But more importantly, new courses are now built accessibly from the start. The framework eliminated the retrofit cycle entirely.
The lesson applies beyond accessibility. Any quality concern that gets treated as a bolt-on will always be expensive and inconsistent. The alternative is to make it architectural — embedded into templates, tools, training, and culture. When you do that, quality becomes effortless instead of exhausting.