Moodle's goal is to be fully accessible and usable for all users regardless of ability.
This (DRAFT) page describes the current state of accessibility in Moodle as well as our plans for the future.
Established practices =
Moodle core developers spend a lot of time making sure new development 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 piece of machinery with many working parts. Code is always evolving. Modules can be enabled and disabled. The interface can be heavily customised using themes and thousands of settings. The 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.
- We hope to have document here soon discussing how well Moodle meets WCAG 2.0 requirements.
- In Moodle 2.7 a new editor Atto was added which is intended not only to improve how everyone can use the editor itself, but also to improve the accessibility of the content produced with it.
- A conformance report is planned.
Section 508 (US)
- Moodlerooms (a Moodle Partner) have a VPAT statement on their web site.
- No known SENDA report exists
One of the main places accessibility work is being carried out right now is on the Moodle Accessibility Collaboration Group mailing list, see http://collaborate.athenpro.org/group/moodle/
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.
Areas of major development
- Atto - a new text editor