The Challenge
Colibri had 45+ course products that needed to meet WCAG 2.1 AAA accessibility standards. There was no existing systematic approach — accessibility was treated as a checklist item at the end of development, which meant issues were caught late, fixes were expensive, and compliance was inconsistent across products. The scale of the problem made a course-by-course retrofit impractical.
The Approach
I reframed accessibility from a compliance task to an architectural concern. Instead of auditing courses after they were built, I designed a framework that embedded accessibility into every phase of development. This included creating a comprehensive checklist system mapped to WCAG 2.1 AAA criteria, building automated pre-checks into our development pipeline, and developing training materials so every team member understood accessibility principles — not just the rules.
The Solution
The solution had three layers. First, a standards framework that translated WCAG criteria into actionable development guidelines specific to our content types. Second, automated tooling integrated into the build pipeline that caught accessibility violations before human review. Third, a training program that shifted the team's mindset from 'check the box' to 'design for inclusion.' Accessibility became structural, woven into how courses were conceived and built — not bolted on at the end.
Three-Layer Accessibility Architecture
Standards Framework
WCAG AAA criteria translated into content-specific development guidelines
Automated Tooling
Pipeline-integrated checks catching violations before human review
Team Training
Mindset shift from compliance checkbox to inclusive design culture
The Results
45+
Courses Compliant
AAA
WCAG 2.1 Level
Zero
Post-Launch Complaints
All 45+ courses achieved WCAG 2.1 AAA compliance. Post-implementation, accessibility complaints dropped to zero. The framework continues to ensure new courses are built accessibly from the start, eliminating costly retrofits. The team now views accessibility as a design constraint rather than a compliance burden.
Reflection
Accessibility is architecture, not cosmetics. When you treat it as something you add at the end, you'll always be catching up. When you build it into the foundation — into the templates, the tools, the training, the culture — it becomes effortless. The most impactful part wasn't the checklist; it was changing how the team thinks about who their learners are.