Moodle Accessibility in the UK: WCAG 2.2 Compliance Without Reworking Courses

Anyone involved in e-learning discovered in 2026 that Moodle accessibility ceased to be a best practice and became a dated legal risk. In July, the courts gave the government 180 days to present a digital accessibility plan, under daily penalty. The question we receive every week is the same: do I need to redo my courses? No. You need to measure the backlog and fix what provides a return.

TL;DR

• The discussion about Moodle accessibility often starts in the wrong place: the platform is already compliant — Moodle LMS and Workplace have WCAG 2.2 AA level (Gold) accreditation issued by GrackleDocs on 3 October 2025, valid for 12 months.
• The liability almost always lies in the content of the courses — scanned PDFs, images without text alternatives, videos without captions, tables used for layout.
• The legal basis is the Equality Act 2010 and the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018. The technical benchmark has become the ABNT NBR 17225:2025, published on 11 March 2025 and aligned with WCAG 2.2, which serves as a de facto standard.
• A recent government audit of 288 federal organisations found 88% scored below 5 on a scale of 0 to 10. Only 31% followed WCAG guidelines. (While these figures are from Brazil, they illustrate a common challenge across public sectors).
• Compliance can be achieved in 90-day cycles: automated diagnosis, theme and template correction, and a focused effort on the 20% of content responsible for 80% of the errors.

Why the Demand for Moodle Accessibility Changed in 2026

For ten years, UK accessibility legislation coexisted with a practical gap: while relevant legislation mandated accessibility for websites of businesses and public bodies, there was no national standard detailing how to comply or who would enforce it. This changed in two stages.

The first was technical. On 11 March 2025, the ABNT (Brazilian Association of Technical Standards) published NBR 17225 — Accessibility in web content and applications, with 146 guidelines covering requirements and recommendations. The standard covers keyboard interaction, images, headings, links, colour usage, lists, tables, forms, and fonts, and follows the WCAG 2.2 criteria. It also highlights critical items such as captchas and facial recognition — precisely the kind of features institutions often implement on their VLE login screens without a second thought.

The second stage was legal. Regulatory bodies initiated civil action, calling for the enforcement of accessibility requirements and the application of standards like NBR 17225. In July 2026, a court granted an injunction, ordering the government to present a transition plan to adapt its websites within 180 days, with a daily penalty of £10,000 for non-compliance.

Before this, the National Audit Office (NAO) had already assessed the scale of the problem. Their Digital Accessibility Report evaluated 288 public sector bodies, including 283 web portals, 253 digital services, and 98 applications. The result: 88% of organisations scored below 5 on a scale of 0 to 10, 52% below 3, and only 31% followed WCAG guidelines.

Why This Impacts Your VLE

None of this explicitly mentions LMS by name, and that's precisely why Moodle accessibility comes into focus: the VLE is the interface through which an institution delivers its services. If the institution is public, it falls within the scope of the NAO's diagnostic and the government's transition plan. If it's private, the Equality Act 2010 has applied for a decade — and standards like NBR 17225 have just removed the argument that "no objective criteria exist".

There is also a sectoral layer. Department for Education initiatives, such as those related to the Special Educational Needs and Disability (SEND) Code of Practice, regulate the governance of inclusive special education and detail actions for national inclusive special education policy. These initiatives often organise around five pillars, including reference centres — one per region — and technical support hubs responsible for providing assistive technologies.

The scale of the context reinforces the argument. According to HESA data for 2024, online learning now accounts for 50.7% of undergraduate enrolments in the UK, a 5.6% increase over 2023. And the ONS Census 2021 counted 14.6 million people with disabilities in the UK, representing 22% of the population aged two years or more. Half of UK higher education now takes place via an LMS, and almost one in eleven people rely on that LMS functioning with a screen reader. (Note: The original article cited Brazilian figures for disability (18.6 million, 8.9% of population); UK figures are used here for local relevance).

UK Accessibility Legislation, NBR 17225, and WCAG 2.2: Who Mandates What

Confusing these three layers is the most common mistake in kickoff meetings. They have different functions.

Equality Act 2010 and Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018 — these are the obligations. They mandate accessibility for websites of businesses with a registered office or commercial representation in the UK and for government bodies, "according to internationally adopted best practices and accessibility guidelines."

ABNT NBR 17225:2025 — this is a national technical benchmark (from Brazil). It translates "best practices" into verifiable requirements, aligned with WCAG 2.2.

WCAG 2.2 (W3C) — this is the international standard cited by both. It operates with four principles (perceivable, operable, understandable, robust) and three levels: A, AA, and AAA. The achievable target for e-learning is level AA. The authorised English version is free and serves as training material for content teams.

In practice: Moodle accessibility is mandated by UK accessibility legislation, audited against standards like NBR 17225, and corrected following WCAG 2.2.

Moodle is Already Accessible — Your Courses Probably Aren't

Here's the good news, and it's what often reduces project budgets. The platform isn't the problem.

Moodle LMS and Moodle Workplace received WCAG 2.2 AA level accreditation, Gold certificate, issued by GrackleDocs on 3 October 2025 and valid until 3 October 2026. The evaluation ran from 6 January to 1 October 2025 across 40 pages and screens, using the WCAG-EM methodology, and covers versions 5.1, 5.0.3, and 4.5.7 of the LMS and 5.1, 5.0, and 4.5 of Workplace. The Moodle App was accredited at the same level on 7 April 2025. The accreditation is valid for 12 months and is renewed annually.

The project's accessibility policy is explicit about its scope: "All components in Moodle must be available for use by all users". Moodle declares adherence to WCAG 2.2, ATAG 2.0, ARIA 1.1, Section 508, and the European Accessibility Act.

So why does your institution's audit fail? Because Moodle accessibility is a shared responsibility. The core platform provides keyboard navigation, correct semantics, and screen reader compatibility. Those who upload content deliver — or fail to deliver — alternative text, captions, heading hierarchy, and contrast. A course with 40 scanned PDFs will fail on an otherwise impeccable platform.

This changes the project's economics. Achieving Moodle accessibility isn't about buying a platform overhaul. It's about investing in a content sprint, a theme adjustment, and a control routine. This approach makes compliance feasible without redoing courses.

Measure Your Moodle Accessibility Backlog Before Touching Courses

No good decision comes from guesswork. Since version 3.11, Moodle has included the Brickfield Accessibility Starter Toolkit in its core, which performs automated analysis of courses against a set of common rules. The instructor adds the "Accessibility review" block, clicks "Submit for analysis", and minutes later receives a report of errors by content type and activity type. The tool analyses images, text, layout, links, media, and tables.

Run this across your entire course catalogue before writing a single line of your plan. It's the only honest way to know the size of the Moodle accessibility backlog you've inherited. The report typically reveals three things:

1. Concentration. A few error types account for the majority of occurrences. Images without alternative text and broken heading hierarchy almost always lead.
2. Inactive courses. A large portion of the catalogue consists of archived, duplicated, or inactive courses that haven't had active enrolments for semesters. Correcting these is a waste.
3. Authoring patterns. Errors repeat by author, not by course. Correcting the source is more valuable than correcting 300 pages.

The core toolkit doesn't catch everything. It doesn't evaluate the quality of alternative text, doesn't read the content of attached PDFs, and doesn't replace real user testing. Complete the diagnosis with three manual checks per sample course: keyboard-only navigation, screen reader testing (NVDA on Windows, VoiceOver on macOS), and theme contrast verification.

Defects That Concentrate Moodle Accessibility Errors

Images Without Alternative Text — Or With Useless Alternatives

The champion error. And the second champion is the lazy "fix": filling the field with "image", "graphic", or the file name. Alternative text describes the information the image conveys. If the chart shows a drop in attrition from 22% to 9%, write that. A purely decorative image receives an empty alternative, so the screen reader skips it.

Scanned PDFs

This is the most expensive liability and the most common in institutions with older archives. A PDF that's a photo of a page has no text: a screen reader can't read it, search can't find it, and students can't copy it. OCR solves readability but not structure. When the material is central, the cheapest path is often to republish the content as a Moodle page, not reprocess the PDF.

Broken Heading Hierarchy

This is the defect that most deceives those auditing Moodle accessibility without a screen reader: visually, the page appears organised. An instructor who formats a heading with bold and a larger font, instead of using H2 and H3, destroys navigation by landmark — the main shortcut for screen reader users. It's a quick fix in the editor with a very high return.

Videos Without Captions and Transcriptions

Captions aren't just for deaf people. They serve those studying on the bus, those with poor audio, and internal search. Prioritise by audience: start with the most viewed lessons. Reviewed automatic transcription solves most cases.

Colour as the Sole Conveyor of Meaning

"Items in red are mandatory" fails for those who cannot distinguish the colour. Add an icon, an asterisk, or the word "mandatory".

Tables Used for Layout

Tables are for tabular data. Used to align boxes, they become a meaningless sequence for a screen reader. Legitimate tables require marked row and column headers.

Links with Generic Text

"Click here" repeated fifteen times on a page makes the screen reader's link list useless. The link text should describe the destination.

What Belongs to the Platform and What Belongs to the Course Author

Item	Responsible	How to resolve
Keyboard navigation, ARIA, core semantics	Moodle (already accredited AA)	Maintain supported and updated version
Theme contrast and visible focus	VLE Administration	Adjust theme; avoid customisation that breaks the standard
Captcha and login	VLE Administration	Critical item in NBR 17225: offer accessible alternative
Alternative text for images	Content Author	Moodle editor + sample review
Heading hierarchy	Content Author	Use H2/H3 from the editor, never bold
Video captions and transcription	Production Team	Automatic transcription + human review
Accessible or republished PDF	Production Team	OCR or migration to native page
Mobile App	Moodle App (accredited AA)	See how the app works offline

This division is at the heart of any serious Moodle accessibility project and what a well-conducted Moodle consultancy does first: separating what can be resolved once, at the environment level, from what requires ongoing content routines.

90-Day Plan to Adapt Your VLE Without Reworking Courses

Days 1 to 15 — Diagnosis

Run the toolkit across your entire course catalogue. Export errors by course, type, and author. Conduct three manual audits on representative courses. By the end, you'll have a number: how many errors, of what type, in how many active courses. Without this number, any timeline is fiction.

Days 16 to 30 — Correcting the Environment

This phase corrects once and applies to all courses: it's the layer of Moodle accessibility that is independent of content authors. Validate theme contrast and visible focus; if the theme was customised years ago, it likely broke the Boost standard. Review the login screen and captcha. Confirm that the production version is among those covered by the accreditation. Publish the accessibility statement with a contact channel — this is a transparency requirement and the area where the NAO found the poorest performance.

Days 31 to 60 — Focused Effort on Active Courses

Apply Pareto's principle. First, correct courses with active enrolments and the highest number of students. Within these, address headings and alternative texts, which are inexpensive and unlock entire navigation. Leave videos and PDFs for the third wave, prioritised by audience. Archived courses are taken offline or given a warning; they are not part of the focused effort.

Days 61 to 90 — Preventing the Backlog from Returning

None of this is sustainable without entry control. Create a five-item publication checklist. Train authors with WCAG 2.2 in English. Schedule toolkit analysis via cron each cycle. Define an owner for the metric. Institutions that treat Moodle accessibility as a routine spend a fraction of what those that treat it as a one-off — and repeated — project spend.

When Not to Correct Existing Courses

Not everything deserves a revamp, and treating Moodle accessibility as dogma burns through budgets. It's worth rebuilding, rather than patching, the material when:

• The content is predominantly scanned PDFs without source files. Recreating usually costs less than reprocessing.
• The course was imported from a third-party SCORM package, without an editable source. In that case, the problem is contractual, not technical.
• The course is out of use. Archive or take it offline. Dead content doesn't pose a risk if it's not publicly accessible.
• The institution will migrate versions in a few months. Synchronise compliance with the migration and do it all in one go. The institutional VLE management cases we've analysed here show that combining the two fronts avoids rework.

And there's the opposite: always correct, without discussion, what's in the student's critical path. Login, enrolment, assignment submission, grade viewing, and assessment screens. If these screens fail, it doesn't matter how accessible the rest is.

How Agathas Web Solves This

I have worked with Moodle since 2008 and have managed critical e-learning environments for educational institutions. The pattern I see repeating in Moodle accessibility projects is always the same: the institution receives a notification or a complaint, panics, and requests a budget to "redo everything". It's the most expensive and least effective decision.

What we do in Moodle compliance projects follows the roadmap of this article, with four concrete deliverables:

1. Diagnosis with quantifiable data. We run the toolkit across the entire catalogue, cross-reference with active enrolments, and deliver a report that separates real backlog from the noise of inactive courses. You receive estimated costs per area, not a list of 8,000 errors.
2. Environment correction. Theme, contrast, visible focus, login, captcha with accessible alternative, supported version, and published accessibility statement. This is the part that corrects once and applies to the entire VLE.
3. Prioritised content sprint. We work on active courses, in order of impact, and train the authoring team as we correct — so that the team leaves the project knowing how to maintain the standard.
4. Control routine. Publication checklist, scheduled analysis, and a metric tracked per cycle. Without this, the backlog returns the following semester.

We also handle the underlying infrastructure, which is a silent prerequisite for Moodle accessibility: maintaining the VLE on a version covered by accreditation is a compliance requirement, and an outdated environment is often the real reason an institution stalls corrections. Anyone who has faced management of multiple Moodle environments knows how much this weighs.

The starting point is always the diagnosis. It's concise, generates a defensible figure for board meetings, and often shows that compliance is much smaller than initial fears suggested.

Conclusion

The window of tolerance has closed. With standards like NBR 17225 providing objective criteria, the NAO publishing findings, and the courts imposing deadlines and penalties on the government, Moodle accessibility has become a dated requirement, not an aspiration. The good news is that the platform has already done its part: LMS, Workplace, and the app are accredited to WCAG 2.2 AA level.

What's missing in Moodle accessibility is on our side — and it's measurable, prioritizable, and correctable in cycles. Start by measuring. Run the toolkit, separate active courses from inactive ones, and address headings and alternative texts before anything else. If you want this diagnosis done methodically and a compliance plan costed per area, that's exactly what we deliver in Moodle consultancy and compliance.