Estimated reading time: ( words)
Summary: Auditing a Moodle site needs to be done manually. Below are resources to help you build accessibility into your site from the beginning and to test your work as you go.
On this page:
Two types of issues may arise in site accessibility audits: those that the instructor or instructional designer has control over, and those that we do not.
The web accessibility assessment software we have at the U of M, Compliance Sheriff, is not helpful for Moodle sites because the software will identify violations that are not possible for you to fix, such as:
- Moodle code
- Grade book
- Course structure
Likewise for other free audit tools like FANGS and WAVE. Therefore, you will need to manually audit your site.
External tools that will automatically evaluate (audit) your Moodle are not currently available at the U of M, but they do exist. If you would like a tool that can audit Moodle sites automatically, we encourage you to indicate your interest by sending an email to firstname.lastname@example.org.
Make sure that:
- Individual documents linked to the site are accessible. Guidelines for Word, Excel, PowerPoint, PDF
- Hyperlinks are discrete and descriptive
- Color is not used alone to identify important information
- All text manually entered into Moodle (in quiz questions, Pages, Book, Lesson, Label, and etc.) are structured using HTML headings
- Heading rows in tables are identified, and tables are only used to display data rather than as means of page layout
- Images have descriptive text, preferably as part of a caption that all users can view, or as alternative text
- Videos are captioned and transcripts are available
- Quizzes don’t use the drag-and-drop question types
Other third-party activities, such as Flipgrid and Yellowdig, may have additional accessibility concerns. For these scenarios, consider developing an assignment alternative following the principles of universal design for learning.
Two additional features of the text editor may also help you ensure accessible content in your Moodle site when you use them at the point of creation: the accessibility checker and the screen-reader helper.
You can find the accessibility checker as an icon in the WYSIWYG text editor:
This tool checks for some common errors, such as:
- Images with missing or empty alt text (unless they have the presentation role)
- Color contrast between text and background
- Long blocks of text are structured with headings
- Tables include captions
- Table cells aren’t merged
- Tables contain row or column headers
The accessibility checker can be useful on a per-text-area basis. That is, it doesn’t check a whole site or a whole section, but just the content in the text box.
Screen reader helper
You can find the screenreader helper in the WYSIWYG text editor, next to the accessibility checker:
The screen reader helper provides additional information to the screen reader user.
Screen reader softwares usually identify editable content regions as text boxes. You encounter editable content regions everywhere you add content in Moodle. Students encounter them in places like the online text Assignment and Forum tools. Here is an example of the mini “report” that the screen reader helper returns to a user:
It is useful to know that the screen reader helper tool is available when you are creating content in your Moodle site, as it provides another quick check of accessibility best practices as you go along.