Moodle is designed to provide equal functionality and information to all people. This means that there should be no barriers for people regardless of disabilities, assistive technologies that are used, different screen sizes and different input devices (for example mouse, keyboard and touchscreen).
This checklist helps reviewers perform an accessibility review of a patch. It is designed to be used alongside the Accessibility coding guidelines and the Accessibility testing documentation.
A statement about the accessibility of the Moodle Developer Resources site.
You should perform accessibility testing when introducing features or bug fixes involving user interface (UI) changes. Combining automated and manual accessibility testing is essential to ensure accessibility of code contributions to Moodle.
Screen readers
All features in Moodle must be accessible to all users regardless of their abilities. Therefore, accessibility must be built in from the planning and design stage through to development and testing, to ensure we release features that are accessible by default.
What does accessibility mean?