What a WCAG 2.2 AA accessibility audit covers
Further reading: How to Make eLearning Accessible: Applying WCAG Standards.
What you receive
Especially relevant for government and public institutions with accessibility obligations, and for everyone else, simply the right way to build. Building new content instead? We build to AA as standard.
Common questions
What does an accessibility audit cover?
Your courses, LMS theme and documents, tested against WCAG 2.2 AA: keyboard navigation, screen reader behaviour, colour contrast, captions, headings and structure, forms and focus order.
What do we receive at the end?
A prioritised findings report in plain language: each issue with evidence, its severity, who it affects and how to fix it, so your team can act on it rather than file it.
Do you fix the issues too, or just report them?
Both. An audit can stand alone, or flow straight into remediation by the same team, and because we build to WCAG 2.2 AA as our default, the fixes come from people who do this daily.
Why WCAG 2.2 AA specifically?
It is the current version of the international standard, and AA is the level Australian government and education organisations commonly require for digital learning. It is also our default build standard, not a premium add-on.
Can you audit courses you did not build?
Yes. We audit existing SCORM and H5P content, LMS themes and platforms regardless of who built them, and give you an honest picture of where they stand.