From MoodleDocs
Revision as of 21:06, 4 January 2024 by Rachel Preston (talk | contribs) (Added to clarify this plugin is not relevant to Moodle 4 as no relevant version has been released)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Moodle's goal is to be fully accessible and usable for all users regardless of ability.

This page describes the current state of accessibility in Moodle as well as our plans for the future.

Voluntary Product Accessibility Template (VPAT)

Digital accessibility is key to ensuring the Moodle platform is accessible and inclusive for all users. An overview of Moodle's conformance with the WCAG 2.1 guidelines can be found in our accessibility conformance report.

Established practices

Moodle core developers spend a lot of time making sure new developments are accessible. Part of the process when building new code in Moodle is to follow established best practices and part of the process for accepting new code into core is to test pages carefully and gather feedback from experts.

Conformance to standards

The Moodle platform is a complex system with many parts. Its code is always evolving. Modules can be enabled and disabled. The interface can be heavily customised using themes and thousands of settings. Actual content can be produced by any teacher or any student. As such it is impossible to say with 100% certainty whether Moodle or any site based on Moodle is absolutely accessible or not. Accessibility is not a state, it is a process of continuous improvement in response to our users and the wider technical environment.

WCAG 2.1

When deciding how Moodle should present its content for best Web accessibility, the WCAG 2.1 guidelines are followed.

ATAG 2.0

As Moodle is a place to construct content (as well as consume content), we also refer to the ATAG 2.0 guidelines. In Moodle 2.7 a new editor (Atto editor) was added that not only helps to improve how everyone can use the editor itself, but also helps to improve the accessibility of the content produced with it. In Moodle 4.1 a new powerful rich-text editor (TinyMCE editor) was added to allow users to create formatted content within a user-friendly interface.

ARIA 1.1

As many parts of the Moodle user interface are dynamic and interactive, we follow the ARIA recommendations to inform assistive technologies, such as screen-readers.

Section 508 (US)

As Moodle is used by US Government agencies, the US Section 508 amendment can be relevant to Moodle.

European Accessibility Act

As Moodle is used by government agencies and universities in the European Union, the European Accessibility Act is also relevant.


One of the main places accessibility work is being carried out is on the Moodle Accessibility Collaboration Group mailing list, see

There are also many discussion on issues in the Moodle Tracker.

Known bugs and issues

This is the main list of accessibility issues, organised by priority. This list is always changing.

See also

[[1]] [[2]]