An accessible learning platform that works for every student

The challenge

What was going wrong

1. 1

   Audit against WCAG

   We tested the main journeys by hand with keyboards and screen readers, and with automated tools, then measured each issue against WCAG 2.2.

2. 2

   Prioritize by student impact

   We ranked the findings by how much they blocked learning, so the team fixed lesson access and quizzes before smaller cosmetic problems.

3. 3

   Guide the fixes

   We wrote clear instructions for designers and developers, reviewed their changes and retested with assistive technology after every round.

4. 4

   Build the habit

   We trained the team and added accessibility checks to design reviews and releases, so new features start accessible instead of needing repair.

• Full accessibility audit report

  Each issue explained in plain words, with severity and a suggested fix.

• Keyboard and screen reader fixes

  Menus, lessons and quizzes can be used without a mouse.

• Captions and clear contrast

  Video captions, readable colors and visible focus indicators.

• Team checklist and training

  A short checklist used in every design and release review.

• Core lessons usable with assistive tools

  Students using screen readers and keyboards can now complete lessons and quizzes.

• Stronger position with schools

  The provider can answer accessibility questions in tenders with evidence from the audit.

• Accessibility is part of the routine

  New features are checked during design and review, so old problems do not return.

• Figma Design tool for dashboard wireframes and layouts approved before build.
• HTML5 Standard markup for banners and email builds.
• CSS Styles layouts responsively across phones, tablets and desktops.
• JavaScript The language of interactive web pages.
• Lighthouse Audits page speed, accessibility and search readiness.