Skip to content

Accessibility statement based on moodle.org statement #1364

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Jun 10, 2025
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
37 changes: 33 additions & 4 deletions general/documentation/accessibility.md
Original file line number Diff line number Diff line change
@@ -1,10 +1,39 @@
---
title: Accessibility
description: This page discusses the accessibility of the developer documentation site, including any policies and certifications that are adhered to.
description: A statement about the accessibility of the Moodle Developer Resources site.
tags:
- Accessibility
- Compliance
- Certification
---

The Moodle Developer resources are designed to provide equal functionality and access to information for all people. There should be no barrier for people regardless of any disabilities, or assistive technologies that are used, different screen sizes, and different input devices (for example mouse, keyboard and touchscreen).
At Moodle, we are committed to ensuring that the Moodle Developer Resource, powered by Docusaurus, is accessible to all users, including those with disabilities. While the Docusaurus framework does not specify a particular level of Web Content Accessibility Guidelines (WCAG) conformance, our goal is to meet WCAG 2.2 Level AA standards across the site.

The Moodle Developer Resource is built and maintained through community contributions, reflecting the collective expertise and dedication of Moodle developers worldwide.

As part of this effort, we strive to:

- Provide clear, structured, and easy-to-navigate content.
- Encourage contributors to follow accessibility best practices when submitting documentation.
- Ensure compatibility with assistive technologies, including screen readers and keyboard navigation.
- Use accessible colour, typography, and media elements.
- Continuously review and improve the site's accessibility based on feedback and best practices.

You should be able to:

- Enlarge text by zooming in.
- Read the text and view images that have a high contrast to their background.
- Change the background and text colour and fonts using browser plugins.
- Navigate the website using only a keyboard.
- Navigate using a screen-reader and speech-recognition software.
- Listen to texts and image descriptions using a screen-reader (such as [NVDA](https://www.nvaccess.org/download/)).

## Alter this website to suit your own needs

[My Computer My Way](https://mcmw.abilitynet.org.uk/) is a website by AbilityNet that helps you to set up your computer to suit your own needs.

## Problems, questions, comments or suggestions

If you have problems accessing any part of the website, or require it in a different format, or have any questions, comments or suggestions for improving the accessibility of the website, please raise an issue in our [Github devdocs repository](https://github.com/moodle/devdocs/issues) or send a message via the [Moodle Community Sites contact form](https://moodle.com/contact/support/?selection=community#form).

## Learn about accessibility

Moodle Academy offers a number of [free short courses about accessibility](https://moodle.academy/tag/index.php?tc=2&tag=Accessibility&from=2) for the general public, teachers and programmers. Get started with the 1 hour [Introduction to Accessibility](https://moodle.academy/course/view.php?id=58) course to learn how you can communicate in a more accessible way to benefit everyone.