Accessibility usually arrives too late. The course is built, the interactions are polished, and then someone runs a checklist and discovers that the branching scenario — the part you spent the most on — doesn't work with a screen reader. Now you're either rebuilding it or quietly shipping something that excludes the people it was meant to serve.
The standard is the floor, not the goal
WCAG 2.1 AA is the standard, and it should be non-negotiable. But the mindset matters more than the line items. In practice it comes down to a handful of design commitments you make before you build:
- Colour is never the only thing carrying meaning.
- Every interaction is operable by keyboard, not just mouse.
- Timed and branching elements still work with a screen reader.
- Motion respects the learner's reduced-motion preference.
Hold those as constraints from the first storyboard and they shape the design instead of fighting it.
Accessible isn't a separate, lesser version. Designed well, it's just the version.
Constraints make the work better
Here's the part people miss: doing this upfront doesn't dull the design — it sharpens it. Designing for keyboard operation forces clearer interaction patterns. Designing for screen readers forces a sane content hierarchy. Designing without relying on colour forces stronger contrast and better visual structure. The discipline that makes a course accessible is the same discipline that makes it clearer for everyone.
Bolt it on at the end and you pay twice: once to retrofit, and again in the learners you quietly lose — often the ones who most needed the hardest parts of the course to actually work. Build it in from the start and accessibility stops being a tax. It becomes one of the constraints that makes the whole thing good.