Ontario, Canada
AODA
The Integrated Accessibility Standards Regulation requires WCAG 2.0 AA for designated organizations' web content.
Accessible eLearning · WCAG 2.2 AA
Most organizations don't realize their training has to meet accessibility standards until a client, an auditor or an employee asks. We build custom eLearning that meets WCAG from the first storyboard, so your project is compliant before it ever reaches your LMS.
Ontario · AODA
WCAG 2.0 AA
US federal · Section 508
WCAG 2.0 AA
US public sector · ADA Title II
WCAG 2.1 AA
We build to
WCAG 2.2 AA
The requirement most teams miss
Accessibility has been part of eLearning for years. WCAG 2.0 was published in 2008, Ontario's AODA standards have been in force since 2011, and Section 508 was refreshed in 2017 to point directly at WCAG. Yet many courses still fail basic checks because accessibility gets treated as a final polish instead of a build requirement.
It also reaches further than people expect. Under the US Department of Justice's ADA Title II rule, password-protected content is not exempt, so courses inside an LMS are covered, and so are the vendors who build content for public organizations.
If your training reaches employees, customers or the public, assume it needs to be accessible, and plan for it from day one.
Which standard applies
Each version of WCAG builds on the one before it. Building to WCAG 2.2 Level AA satisfies the older versions your organization may be legally tied to.
Ontario, Canada
The Integrated Accessibility Standards Regulation requires WCAG 2.0 AA for designated organizations' web content.
US federal
Federal agencies and the organizations that supply them build to WCAG 2.0 AA.
US state & local government
The DOJ rule sets WCAG 2.1 AA for web content and apps, including content vendors provide.
SCORM Team standard
The current version. One build that meets all three, with headroom for whatever comes next.
Where DIY courses fail
Static pages are rarely the problem. These are the places custom eLearning most often breaks WCAG, and where we focus first.
Tabs, hotspots and click-to-reveal panels must work by keyboard and expose their state. Drag-and-drop needs a single-pointer alternative.
WCAG 2.1.1 · 4.1.2 · 2.5.7
When a new slide loads, focus moves to its heading, so screen reader users aren't stranded on a “Next” button. No focus traps in feedback layers.
WCAG 2.4.3 · 2.1.2
“Correct” and “Incorrect” can't rely on colour or an icon alone. Feedback is announced, fields are labelled and errors are described in text.
WCAG 1.4.1 · 3.3.1 · 4.1.3
Captions are required, and so is audio description at Level AA, the one most animated courses miss. We write narration that already describes what matters on screen.
WCAG 1.2.2 · 1.2.5
Timed quizzes and auto-advancing slides need a way to extend time. Long animations need a pause control, and nothing flashes.
WCAG 2.2.1 · 2.2.2 · 2.3.1
Content has to reflow at 400% zoom and survive increased text spacing. Locked aspect-ratio slide players often fail both.
WCAG 1.4.10 · 1.4.12
4.5:1 for text, 3:1 for controls and focus rings, click targets at least 24 px, and focus never hidden behind a sticky player bar.
WCAG 1.4.3 · 1.4.11 · 2.5.8 · 2.4.11
Each version declares its language, such as fr-CA for Québec French, so screen readers pronounce it correctly, including inline passages.
WCAG 3.1.1 · 3.1.2
An accessible SCORM package can still fail inside an inaccessible player: untitled frames, launch pop-ups, logins with CAPTCHAs. Learners experience it all as one.
WCAG 4.1.2 · 3.3.8
DIY or experts?
Authoring tools and AI can produce a course. Making that course genuinely accessible, and proving it, takes experience most teams don't have time to build.
Doing it yourself
SCORM Team
How we make your project compliant
01
We flag every interaction type up front and pick an accessible pattern for each one, before design starts.
02
Captions, descriptive narration, keyboard support, contrast and reflow go in as we build, not after.
03
Automated scans plus keyboard-only passes and screen reader testing on Windows, Mac and iOS.
04
A SCORM package checked inside your LMS, with the documentation you need when someone asks.
Already have courses? We can review and remediate them too.
Beyond the checklist
WCAG is light on cognitive accessibility, so we go further. Plain language, short chunks, consistent navigation and predictable quizzes help neurodivergent learners and people taking training in a second language.
Plain language
Short chunks
Consistent navigation
Predictable quizzes
FAQ
Often, yes. Depending on your jurisdiction and sector, rules like the AODA, Section 508 and ADA Title II can apply to training, and accommodation obligations apply to employees with disabilities regardless. Building accessibly from the start is far cheaper than fixing a complaint later.
No. The DOJ's ADA Title II rule confirms password-protected content is not one of its exceptions, so LMS-hosted courses for covered organizations are in scope.
WCAG 2.2 Level AA. It's the current version and includes everything in 2.0 and 2.1, so one build satisfies AODA, Section 508 and ADA Title II.
Yes. We review what you have, identify the failures and either remediate the course or rebuild the parts that can't be fixed in place.
[Confirm before publishing] Because we build to a documented checklist, we can provide the conformance information procurement teams ask for.
This page is general information, not legal advice. Confirm your specific obligations with your legal or compliance team.
Send us a course or tell us about a new project. We'll show you what it takes to make it accessible and compliant.