Accessibility and WCAG for online courses in Australia

A student who cannot hear the lecture, see the contrast, or reach the “next lesson” button without a mouse is not a special case you will meet later. They are already in the cohort. They are the bookkeeper with low vision in Townsville, the team leader watching with the sound off in a ward, the apprentice who is Deaf, the public servant who cannot use a mouse after an injury, the person who just has a terrible laptop and a late shift. If your course only works for a well-lit, well-hearing, well-moused version of yourself, you did not build a course. You built a clip.

This is a practical briefing for people who sell training, filed from the same sceptical desk that tests platforms on price and refunds. It sits in the creators hub. It is not legal advice. The Disability Discrimination Act 1992 is a real statute with real complaints. WCAG is a technical standard that keeps moving. A journal article cannot certify you. It can stop you shipping the hostage video with no captions and calling that “done”.

How we treat claims and corrections lives in the editorial standards. The same rule applies to accessibility claims on a sales page: if you have not tested it, do not boast it.

The DDA is the law. WCAG is the yardstick people will pick up

The Disability Discrimination Act 1992 makes it unlawful, in broad terms, to discriminate on the ground of disability in education and in the provision of goods and services. Online courses sit awkwardly across those ideas: you are selling a service, you are teaching, you are sometimes both. The Australian Human Rights Commission publishes guidance. State and territory laws sit alongside. None of them are summarised, for your facts, by a blog.

What a small training business should take from that, without pretending to be a barrister: if a person with disability cannot use the thing you sold, and you have not made reasonable adjustments, you may have a problem that a refund policy cannot decorate away. “It was only a $197 digital product” is not a defence anyone should be proud of.

WCAG — the Web Content Accessibility Guidelines — is the shared language for what “usable” looks like in a browser. Version 2.2 is the current one this desk will name in 2026. Many Australian government digital standards still talk in 2.1 AA because procurement documents move slower than working groups. If you aim at 2.2 AA, you are covering the 2.1 AA bar and the extra 2.2 items (including some that help people with motor and cognitive disabilities use pointers, targets and help). AAA is a higher, often impractical ceiling for a sole trader’s first course. AA is the working target.

WCAG is organised as perceivable, operable, understandable, robust. In a course that means: they can see or hear the lesson, they can work the player and the quiz, they can understand the instructions, and the page does not fall over in an assistive stack. You do not need to memorise the principle names. You need to watch your own lesson with the sound off, then with a keyboard only, then on a phone in bright sun.

A badge that says “WCAG compliant” without a date, a level and a URL you tested is marketing. We would cut it in review.

Captions, transcripts and the lesson that still works when video dies

If you sell video, you sell captions. Not later. Not “if someone asks”. The asking is how a student spends their first paid hour, and how a government buyer decides you are not serious.

Auto-captions from YouTube, Zoom or the LMS are a first pass. They fail on Australian acronyms, names, and the moment you talk over a spreadsheet. Sit through the lesson once as if you could not hear it. Fix the numbers. Fix the names of legislation. Fix the jokes that became other jokes. Then export a caption file the platform can actually use. Burned-in captions help some players and punish everyone who needs to turn them off or translate. Prefer a track.

Transcripts are the searchable version. They help the student who learns by reading, the student on a terrible connection, and you, when you cannot remember which clip mentioned the Fair Work Commission. A transcript is also a kindness to the person building notes from video courses. If the only way to find a fact is to scrub a waveform, you have hidden the curriculum.

Audio descriptions — a second narration of what is happening on screen — matter when the picture carries meaning the words do not. A talking head does not need a poet describing your shirt. A software lesson might need you to say the button, not just circle it in red. That habit also helps the student who is looking at a different version of the app.

The production choices that make captions easier are the same ones that make lectures less hostage-like. Speak in a microphone. Do not talk over music. Do not put the only instruction in a tiny red circle. The companion on recording lectures that look professional is the camera-and-NBN version of this paragraph.

Offer a non-video path for the same artefact: a checklist, a template, a short reading. Australian internet is patchy. Disability is not the only reason a video fails. Design as if Broome and a hospital car park are normal classrooms. They are.

The boring controls: contrast, keyboard, player, language

Most accessibility failures in small courses are not exotic. They are a pale grey button on a pale grey theme, a quiz you cannot reach without a mouse, a video player that traps focus, and a PDF exported from a slide deck that is just a photograph of words.

Contrast. WCAG AA has ratio numbers. Your eyes have a cheaper test: stand in the garden in Brisbane glare and try to read the lesson title on your phone. If the brass-on-stone palette looks elegant in the office and disappears outside, it is not elegant. Links must look like links. Error messages must not be only red.

Keyboard. Unplug the mouse. Can you play, pause, skip, submit, and escape a modal? Can you see where you are? A custom-styled player from a cheap theme is a common villain. The native player is less pretty and more honest.

Structure. Headings in order. One h1. Lists that are lists. A page that still makes sense if the CSS does not load. Screen readers travel by structure. So do tired people.

Images. Alt text that says what the student needs, or an empty alt if the image is noise. A screenshot of Xero needs a sentence about the field, not “image1.png”. Charts need the numbers in text. Memes need a pass or a bin.

PDFs. A tagged PDF, or better, a web page. A scanned workbook is a brick. If you only have the brick, say so and offer another format when asked — and then do it in a time that does not make the request decorative.

Language and cognitive load. Plain Australian English helps more students than a dyslexia plugin you never tested. Short lessons. Instructions before the video, not hidden in lesson 14. Time estimates that are true. Autoplaying sound is a hostility.

Live sessions. Captions on the Zoom. A recording that is not the only access. Chat that is not the only place a vital URL appears. A way to ask a question without speaking on the recording. If you use breakout rooms, have a written task for the person who cannot hear the huddle.

None of this requires a Melbourne agency on a six-month retainer. It requires a Tuesday afternoon and the willingness to be embarrassed by your own theme.

Government and procurement will ask, and they will mean it

If you want invoices from departments, councils, universities, hospitals or large corporates that borrow government language, accessibility is not a vibe you mention in the last slide of a pitch.

Tenders commonly ask for WCAG 2.1 AA or, increasingly, 2.2. They ask whether content is captioned. They ask whether you can make adjustments. They sometimes ask for a VPAT-style statement or a link to an accessibility page that is not “we care”. If your only environment is an American course platform with a theme you have never tested, do that testing before you bid. “We use Thinkific” is not a WCAG claim. Themes and your files are the claim.

Some buyers will require Australian hosting, or a Moodle they already know, because their IT and their disability-support people live there. That is a platform decision as much as a production one. A beautiful Kajabi funnel that a keyboard user cannot complete is a funnel you cannot sell to a department.

Adjustments are part of the sale. Extra time. A transcript early. An alternative assessment that still measures the job. A copy of the slides before the live session. Write down what you can do so the first request is not a panic. You do not have to invent a new course for every student. You do have to not treat the request as an attack on your aesthetic.

Schools and universities have their own procurement and their own disability-support units. If you sell into those, ask what their students already use. An LMS they know, with your videos captioned inside it, will beat a separate login that fails a screen reader on day one.

Private consumer sales are not a holiday from this. The DDA does not apply only when a purchase order number exists. The difference is that government buyers will ask up front, and a consumer may ask after they have paid and failed to play lesson one. The second email is worse.

A working sequence for a sole trader

You will not WCAG-certify a first course on a Sunday. You can stop shipping the worst failures.

1. Write the outline so the job is doable without cinema. Planning is accessibility. A twelve-hour waffle is hostile to everyone, including people with cognitive disabilities and people with a life.
2. Record with a microphone, name the buttons you click, and keep the lesson short. See the recording guide.
3. Caption and read the captions. Export a transcript.
4. Test the student path on a phone, then with a keyboard, then with the OS screen reader for twenty minutes. You will not become an expert. You will find the broken menu.
5. Fix contrast and link text on the sales page and the checkout. A pretty page that cannot be bought is not a page.
6. Write an accessibility note that is true: what you have done, how to ask for an adjustment, how fast you will answer. Put a human email on it.
7. When a platform update wrecks the player, test again. Accessibility is maintenance, like GST settings and a software lesson that still matches the menu.

If you can pay one specialist for anything, pay them to review the student journey, not to write a policy paragraph. A policy paragraph that lies is worse than a quiet page.

Do not use disabled people as a marketing texture. Do not put a stock photograph of a wheelchair next to a course you have never tested. Do not claim you are “fully accessible” because you bought an overlay widget. Those widgets have a reputation. Test the real thing.

Students already know how to work around hostile video — they pause, they take notes, they ask a colleague. Your job is to need fewer workarounds.

A short working checklist

Before you tell a buyer the course is usable:

• Captions you have read, plus a transcript for anything longer than a clip.
• Spoken buttons and on-screen text that is not the only place the meaning lives.
• Contrast that survives a phone in daylight.
• A keyboard-only pass through play, quiz and checkout.
• Alt text, real headings, and no scanned-only workbook without another format.
• An accessibility note with a human contact and a time you will answer.
• A government-ready sentence about WCAG level and date only if you tested it.
• No overlay badge, no “fully compliant” slogan, no fake Australian case study.

If you ship the checklist, you will still miss something. That is why the inbox exists. Missing something and fixing it is teaching. Shipping a course only one body can use, then arguing about the Disability Discrimination Act in a review thread, is a different product. Aim at WCAG 2.2 AA like a grown-up. Get legal advice for the facts of your business. Then go and watch your own lesson with the sound off. That is the review that matters.