Accessible CMS for Australian Education Websites
Every mainstream CMS can be used to build an accessible website. Every mainstream CMS can also be used to build a genuinely inaccessible one, sometimes by the same agency, on the same platform, a year apart. That's the honest starting point for any Australian education provider weighing up platforms. The useful question was never "which CMS is accessible". It's "which CMS makes it easiest to stay accessible once we've handed the keys over".
Here's the legal position, the capabilities worth checking, and how to test a platform yourself.
Key Takeaways
- Australian education providers sit under the Disability Discrimination Act 1992 and the Disability Standards for Education 2005, with WCAG doing the measurable work.
- WCAG 2.2 Level AA is the current reference point. Plenty of older policy and existing contracts still say 2.1, so pin down which version you're being quoted against.
- No CMS ships "accessible" out of the box. Evaluate the authoring experience, not the marketing page.
- Worth checking for: required alt text, controlled heading structure, structured content types, constrained formatting, an admin interface that's itself accessible.
- Test the back end as well as the front end. Staff with disabilities publish too.
The Legal Backdrop
Two instruments do the heavy lifting. The Disability Discrimination Act 1992 makes it unlawful to discriminate in providing services, and that extends to anything digital. The Disability Standards for Education 2005, made under that Act, set out obligations specific to education providers around access and participation.
Neither names a technical specification, so the Web Content Accessibility Guidelines fill the gap, at Level AA. On version: WCAG 2.2 became a W3C Recommendation in October 2023 and is now the reference point for Australian Government digital services and Digital NSW, with the Commonwealth Digital Service Standard requiring the latest version rather than naming a number. Older policy and plenty of live contracts still specify 2.1. That gap is genuinely messy right now, because the policy moved and the paperwork hasn't caught up, so get it in writing which version your build is quoted against.
Public institutions have a second layer. If you're a TAFE, a public university or a government school system, check your own jurisdiction's digital standards first. Note too that since 1 July 2024 the Commonwealth Digital Service Standard covers new and replacement staff-facing services, so a new intranet is in scope.
The Platform Features Actually Worth Checking
Alt Text Isn't Optional, So Don't Let the CMS Treat It That Way
Missing alt text is one of the most common failures on education websites, and almost entirely preventable. A CMS that makes alt text required, with a genuine way to mark an image decorative on purpose, removes the problem at the source.
There are handy new AI tools which can generate alt text for assets on the fly - and even correct/improve existing code to confirm with new compliance. Speak to us to discuss what options are available.
Heading Structure Authors Can't Get Wrong
Screen reader users navigate by heading, constantly. Give authors free rein over heading levels, or let them use bold where a heading belongs, and that navigation breaks. Look for an editor offering only the heading levels valid in context.
Content Modelled as Data, Not Poured Into a Text Box
The single most effective accessibility measure available on an education site: stop authors building pages out of free-form text. Make a course a content type with defined fields, title, code, duration, delivery mode, fees, and render it through an accessible template. The author fills in fields. The markup's correct because there was never another way to produce it.
An Editor With Fewer Ways to Go Wrong
A full-featured rich text editor is a genuine risk, honestly. Pull out the font colour and size controls, block layout tables, strip pasted Word formatting. Sounds restrictive. Prevents a large share of the problems this article is about.
Check the Admin Screen, Not Just the Website
This one gets missed constantly: your own staff include people with disabilities. If the back end can't be operated with a keyboard or a screen reader, you've got an employment problem alongside the web one. Ask vendors for conformance documentation on the authoring interface, not only the public site.
It's fair to ask whether the agency builds staff-facing systems at all, since many web shops don't. Webcoda's SharePoint intranet for The Anglican Schools Corporation serves staff across 17 schools, with a directory carrying org structure and online status, a document hub and a live lesson-schedule feed. Systems staff use daily are a different discipline from a brochure site.
Testing a Platform Yourself, Rather Than Trusting the Demo
Run the same short test on every shortlisted platform, using the agency's own implementation rather than a demo polished for the pitch. Get them to create a page with a heading, an image, a link and a list. Could alt text be skipped? Could heading levels be applied wrong? Is the markup semantic, or does it just look right? Navigate the finished page with the keyboard alone, then try the same inside the admin screen.
Ask how the agency tests with people, too, not just tooling. Webcoda's Umbraco build for JMC Academy ran surveys, interviews, user testing, competitor analysis and user journey mapping before design started. That's the habit to look for, because automated checkers never tell you whether a page makes sense to the person using it.
Depth on More Than One Platform
Umbraco, Xperience by Kentico and HubSpot CMS all support this work well when implemented deliberately. None does it automatically, which is why the agency question outranks the platform one. Ask what an agency is certified in, and whether it can afford to recommend against its own preference. Webcoda is an Umbraco Gold Partner, a Gold partner for Xperience by Kentico and a HubSpot Solutions Partner, with education builds including JMC Academy on Umbraco, UTS College on HubSpot CMS and UNSW BusinessThink.
Frequently Asked Questions
None of them, not in any way that matters. Accessibility comes from implementation. Umbraco, Xperience by Kentico, HubSpot CMS and plenty of others can all deliver a genuinely accessible site. Judge the agency's approach and the authoring experience it builds, and ask which platforms it's actually certified in, so a recommendation isn't just the one thing it knows how to sell.
WCAG 2.2 Level AA is the current reference point for Australian Government digital services and Digital NSW, and it's the sensible default for anyone building new. Older policy documents and existing contracts still cite 2.1 Level AA, so the formal answer depends on your own jurisdiction and your contract. Whichever applies, write the version into the scope rather than leaving it implied.
An independent audit earns its cost before a major launch, or wherever you've got specific compliance exposure, and it's genuinely specialist work best bought from an accessibility specialist rather than your build agency. It complements building accessibly in the first place rather than replacing it. An audit run at the end of a project that ignored accessibility from day one tends to produce an expensive list of things to fix.
They're a common weak point. Student portals, application forms, payment systems, chat widgets and video players are frequently the least accessible parts of an education website, and you inherit whatever problems they bring. Ask vendors for accessibility documentation before you embed anything, not after.
No. Overlay tools that claim to fix accessibility automatically are widely criticised by accessibility practitioners and disability advocates alike. They don't touch the underlying markup or content, they just paper over it. Put that budget into the templates, the authoring experience and author training instead.
Talk to Webcoda
Webcoda is a Sydney-based, B Corp certified digital agency building websites and enterprise web applications since 2005. Our education clients include UTS College, JMC Academy and The Anglican Schools Corporation, and we build accessibility into design and development rather than treating it as a final check. We are an Umbraco Gold Partner, a Gold partner for Xperience by Kentico and a HubSpot Solutions Partner.
Get in touch to talk through your project, or browse our services and platforms.
