Skip to content
https://moodle.org

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
53
GRADE
F
FIX
6
REVIEW
4
PASS
3
INFO
0
Checks
13
3 PASS 4 REVIEW 6 FIX
F
Alt Text Quality
Action
13 of 52 images have issues
FIX
13 of 52 images have issues
Critical::
11 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Critical::
10 image-in-link without alt text
An image inside a link with no alt creates an empty link.
Warning::
2 image(s) with generic alt text
Info::
1 image(s) with alt text over 125 characters
Info::
8 decorative image(s) correctly marked
Info::
30 image(s) with good alt text
52 images 30 good alt text 8 decorative 2 generic 11 missing
IssueCount
missing11 image(s)
generic2 image(s)
too long1 image(s)

Images without alt text are invisible to screen readers.

Why this matters

Each image without alt text is a WCAG 1.1.1 failure — invisible to screen-reader users, lost from Google Image Search.

Learn more ▾

WCAG 2.1 Level A requires text alternatives for non-decorative images. Empty alt='' is fine for decorative; meaningful images need descriptive text. Common fixes: CMS audit + bulk add, build-time linter (alt-text-required ESLint rule), CI gate on Lighthouse a11y score.

Source: WCAG 2.1 SC 1.1.1 / WebAIM Million Report

An image inside a link with no alt creates an empty link.

Why this matters

Image-only links with no alt create empty links — screen-reader users hear 'link' with no destination context.

Learn more ▾

An <a><img></a> with no img alt is the worst-case for accessibility: AT announces the link but can't describe where it goes. Either add alt to the image OR add aria-label to the link.

Source: WCAG 2.1 SC 2.4.4

F
Web Manifest
Action
Valid manifest
FIX
Valid manifest
Info::
Name present: Moodle.org
Warning::
No 192x192 icon
A 192px icon is required for PWA installation.
PWA Install Criteria Not Installable
Name Moodle.org ✓192×192 icon ✗512×512 icon ✗Start URL ✗Display Mode ✗
Icons 1 icon(s)
D
Dark Mode Support
Action
No dark mode signals
FIX
No dark mode signals
Info::
No dark mode signals detected
Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.
Info::
Detection limited to meta tags and inline styles
External CSS files may contain prefers-color-scheme rules not visible to this scan.
Dark ModeNo Dark Mode Detected
color-scheme meta Not set ✗Dark theme-color Not set ✗CSS indicators Not detected ✗

Detection limited to meta tags and inline styles.

D
Print Stylesheet
Action
No print styles
FIX
No print styles
Info::
No print-specific styles detected
When users print this page, they get the screen layout including navigation and non-essential elements. Add @media print rules to hide navigation and optimize layout for paper.
Print Stylesheet No Print Styles
Print stylesheet Not found ✗Inline @media print Not detected ✗
F
Navigation UX
Action
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Skip navigation link detected
Info::
2 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 2 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
3 of 6 testable patterns navigation patterns detected. Strong navigation UX with multiple discovery paths.
B
Heading Hierarchy
53 headings, 2 skip(s)
REVIEW
53 headings, 2 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H1 → H3 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H3 → H5 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H2 Blocks
  • H2 Need guidance on the best learning solution for you?
  • H3 Community hub
  • H1 Welcome to the Moodle community
  • H3 Stats registry skipped
  • H3 Community update
  • H2 Community update
  • H3 Better learning with Moodle LMS 5.2
  • H3 Current research projects
  • H2 Help shape our future
  • H3 Get involved
  • H4 Join the Moodle Experience Lab
  • H4 Translate Moodle Academy
  • H4 The new Moodle Marketplace
  • H3 Need help
  • H2 Need help with your Moodle site?
  • H3 Product vision
  • H2 Our product vision
  • H3 Discover how we build Moodle
  • H3 Community announcements heading
  • H2 Keep up to date
  • H3 Community announcements
  • H3 Announcements footer - mobile
  • H3 News and announcements
  • H4 Announcing Moodle LMS 5.2: Clearer course design, stronger assessment, and a foundation for the future
  • H4 Announcing Moodle LMS 5.2: Clearer course design, stronger assessment, and a foundation for the future
  • H4 Opportunity to list paid plugins on Moodle Marketplace
  • H4 Opportunity to list paid plugins on Moodle Marketplace
  • H4 Multi-Factor Authentication (MFA) Coming to Our Moodle Community Site
  • H4 Multi-Factor Authentication (MFA) Coming to Our Moodle Community Site
  • H3 HQ News Heading
  • H3 Moodle HQ news
  • H3 HQ News
  • H4 Field Notes: When AI agents show up to class
  • H4 Moodle Mentor: April 2026
  • H4 Moodle Premium Certified Partner Accipio expands to New Zealand
  • H3 Hq news footer - mobile
  • H5 Empowering educators to improve our world skipped
  • H5 Moodle
  • H5 Support
  • H5 Get Involved
  • H5 Contributions
  • H5 Downloads
  • H5 Tracker
  • H5 Development
  • H5 Empowering educators to improve our world
  • H2 Privacy Preference Center
  • H3 Manage Consent Preferences
  • H4 Performance Cookies
  • H4 Targeting Cookies
  • H4 Strictly Necessary Cookies
  • H4 Functional Cookies
  • H3 Vendors List

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

C
404 Error Page
Action
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title 404 Not Found ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗
B
Favicon & Branding
6 icon(s) detected
REVIEW
6 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
Multiple icon sizes detected
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✓ Manifest Icons Present
✓ Multiple Sizes Present
B
Lighthouse Accessibility Audits
Score 83/100 — 5 failing, 23 passed
REVIEW
83

Accessibility

These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.

Names and labels

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div#page-wrapper > nav.navbar > a > img.d-lg-none div#page-wrapper > nav.navbar > a > img.d-lg-none
div.card-deck > div.social-icons-block > a.facebook > img div.card-deck > div.social-icons-block > a.facebook > img
div.card-deck > div.social-icons-block > a.linkedin > img div.card-deck > div.social-icons-block > a.linkedin > img
div.card-deck > div.social-icons-block > a.twitter > img div.card-deck > div.social-icons-block > a.twitter > img
div.card-deck > div.social-icons-block > a.youtube > img div.card-deck > div.social-icons-block > a.youtube > img

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
body#page-site-index > div#page-wrapper > nav.navbar > a body#page-site-index > div#page-wrapper > nav.navbar > a

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Contrast

Low-contrast text is difficult or impossible for many users to read. Link text that is discernible improves the experience for users with low vision. Learn how to make links distinguishable.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Log in div.footer-content-popover > div.footer-section > div.logininfo > a
Moodle div.footer-content-popover > div.footer-section > div > a

These are opportunities to improve the legibility of your content.

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Policies div.footer-content-popover > div.footer-section > div.policiesfooter > a
Get the mobile app div.footer-content-popover > div.footer-section > div > a.mobilelink
Switch to the standard theme div.footer-content-popover > div.footer-section > div#theme_switch_link > a

These items highlight common accessibility best practices.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Cookies policy div#onetrust-group-container > div#onetrust-policy > div#onetrust-policy-text > a.ot-cookie-policy-link
○Interactive controls are keyboard focusable
○Interactive elements indicate their purpose and state
○The page has a logical tab order
○Visual order on the page follows DOM order
○User focus is not accidentally trapped in a region
○The user's focus is directed to new content added to the page
○HTML5 landmark elements are used to improve navigation
○Offscreen content is hidden from assistive technology
○Custom controls have associated labels
○Custom controls have ARIA roles
●`[aria-*]` attributes match their roles
●`[aria-hidden="true"]` is not present on the document `<body>`
●`[role]`s have all required `[aria-*]` attributes
●`[role]` values are valid
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●Buttons have an accessible name
●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
●ARIA attributes are used as specified for the element's role
●Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
●`[aria-hidden="true"]` elements do not contain focusable descendents
●Elements use only permitted ARIA attributes
●Background and foreground colors have a sufficient contrast ratio
●Document has a `<title>` element
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●No element has a `[tabindex]` value greater than 0
●Heading elements appear in a sequentially-descending order
●`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
●Skip links are focusable.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●All heading elements contain content.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○ARIA input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
○`[role]`s are contained by their required parent element
○Elements with the `role=text` attribute do not have focusable descendents.
○ARIA toggle fields have accessible names
○ARIA `tooltip` elements have accessible names
○ARIA `treeitem` elements have accessible names
○The page contains a heading, skip link, or landmark region
○`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
○Definition list items are wrapped in `<dl>` elements
○ARIA IDs are unique
○No form fields have multiple labels
○`<frame>` or `<iframe>` elements have a title
○Input buttons have discernible text.
○`<input type="image">` elements have `[alt]` text
○Form elements have associated labels
○Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
○List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
○`[lang]` attributes have a valid value
○`<video>` elements contain a `<track>` element with `[kind="captions"]`
○Tables have different content in the summary attribute and `<caption>`.
○Uses ARIA roles only on compatible elements
○Image elements do not have `[alt]` attributes that are redundant text.
○Identical links have the same purpose.
○Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
○`<td>` elements in a large `<table>` have one or more table headers.
A
Landmark Structure
21 landmarks
PASS
21 landmarks
Info::
<main> landmark present
Info::
2 <nav> landmark(s) found
Warning::
1 of 2 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
Info::
No banner (header) landmark
Info::
Skip navigation link present
Page Structure — as a screen reader sees it
BANNER (missing!) NAV MAIN ASIDE "main-block-region-heading" CONTENTINFO footer

Multiple navigations need aria-label to distinguish them for screen readers.

Why this matters

Some <nav> elements lack aria-label — screen-reader users hear 'navigation' multiple times with no way to distinguish them.

Learn more ▾

When a page has multiple <nav> regions (primary, footer, breadcrumb), each needs aria-label or aria-labelledby. AT users navigate by landmark; identical 'navigation' announcements force them to enter each one to discover purpose.

Source: WAI-ARIA Authoring Practices

A+
Form Accessibility
All 9 controls labeled
PASS
All 9 controls labeled
Info::
9 control(s) properly labeled
9 controls
9 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
#searchinput-69e7c87158dfe69e7c87150bb23textSearcharia-label
#ot-group-id-C0002checkboxPerformance Cookiesfor/id
#ot-group-id-C0004checkboxTargeting Cookiesfor/id
#ot-group-id-C0003checkboxFunctional Cookiesfor/id
#vendor-search-handlertextVendor list searcharia-label
#chkbox-idcheckboxcheckbox labelfor/id
#select-all-hosts-groups-handlercheckboxcheckbox labelfor/id
#select-all-vendor-groups-handlercheckboxcheckbox labelfor/id
#select-all-vendor-leg-handlercheckboxcheckbox labelfor/id
A+
Color Contrast (Screenshot)
20 text elements analyzed, 0 fail WCAG AA
PASS

Analyzes text contrast against the actual rendered page, including background images, gradients, and overlays that CSS-based tools cannot detect.

20 pass
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Welcome to the Moodl…4.89:13.0:1
#000000
#7A7A7A
Pass
h2 Blocks4.89:13.0:1
#000000
#7A7A7A
Pass
h2 Need guidance on the…4.89:13.0:1
#000000
#7A7A7A
Pass
h2 Community update4.89:13.0:1
#000000
#7A7A7A
Pass
h2 Help shape our futur…4.89:13.0:1
#000000
#7A7A7A
Pass
h2 Need help with your …4.89:13.0:1
#000000
#7A7A7A
Pass
h2 Our product vision4.89:13.0:1
#000000
#7A7A7A
Pass
h2 Keep up to date4.89:13.0:1
#000000
#7A7A7A
Pass
h2 Privacy Preference C…4.89:13.0:1
#000000
#7A7A7A
Pass
h3 Community hub4.89:13.0:1
#000000
#7A7A7A
Pass
h3 Stats registry4.89:13.0:1
#000000
#7A7A7A
Pass
h3 Community update4.89:13.0:1
#000000
#7A7A7A
Pass
h3 Better learning with…4.89:13.0:1
#000000
#7A7A7A
Pass
h3 Current research pro…4.89:13.0:1
#000000
#7A7A7A
Pass
h3 Get involved4.89:13.0:1
#000000
#7A7A7A
Pass
h3 Need help4.89:13.0:1
#000000
#7A7A7A
Pass
h3 Product vision4.89:13.0:1
#000000
#7A7A7A
Pass
h3 Discover how we buil…4.89:13.0:1
#000000
#7A7A7A
Pass
h3 Community announceme…4.89:13.0:1
#000000
#7A7A7A
Pass
h3 Community announceme…4.89:13.0:1
#000000
#7A7A7A
Pass

Methodology: The top 20 text elements by font size were checked. Background color was sampled from the desktop screenshot using a 5-point pattern. WCAG 2.1 AA requires 4.5:1 for normal text and 3:1 for large text.

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback