Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

7 PASS 2 REVIEW 4 FIX

Web Manifest

Action

Not found

FIX

Not found

No web manifest found

No manifest at standard paths (/manifest.json, /site.webmanifest). A manifest is optional but enables PWA features like home screen installation and standalone display.

No web manifest found.

Dark Mode Support

Action

No dark mode signals

FIX

No dark mode signals

No dark mode signals detected

Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.

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.

Print Stylesheet

Action

No print styles

FIX

No print styles

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 ✗

404 Error Page

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

Navigation links present on 404 page

Homepage link present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title Page not found - Moodle ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗

Favicon & Branding

4 icon(s) detected

REVIEW

4 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

Multiple icon sizes detected

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✓ Multiple Sizes Present

Landmark Structure

11 landmarks

PASS

11 landmarks

<main> landmark present

4 <nav> landmark(s) found

2 of 4 <nav> elements are unlabeled

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

Skip navigation link present

Page Structure — as a screen reader sees it

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+

Heading Hierarchy

32 headings

PASS

32 headings

Single H1 present

H1 Online learning, delivered your way
H2 Why Moodle? – Moodle puts the power of eLearning in your hands
H3 Customise your learning experience
H3 Scale your platform to any size
H3 Safeguard your LMS data and systems
H3 Use anywhere, on any device
H3 Tap into specialist LMS support
H2 Our products – Choose your online learning platform
H3 Moodle LMS
H3 Moodle Workplace
H2 Success Stories – Building better learning experiences with Moodle
H3 Making virtual training more engaging: Lessons from real organisations
H3 Simon Community NI provides life-saving training with Moodle LMS
H3 Built together: A story of partnership and progress in Moodle Workplace
H2 Our customers – Who’s using Moodle?
H2 Testimonials – What our customers say
H3 PintRaj K, Web Developer, Source: G2
H3 Massy, Freelancer, Source: Capterra
H3 Adolphine, Lecturer, Source: Capterra
H3 Faycal, Instructor, Source: Capterra
H3 Jishma B., HR Manager, Source: G2
H3 Sylvester Zibusiso M., Source: Capterra
H3 Ahmad Farhad, VP Management Consulting, Source: Capterra
H3 Darina U, Source: Capterra
H3 Carlos A, Source: G2
H3 PintRaj K, Web Developer, Source: G2
H3 Massy, Freelancer, Source: Capterra
H2 Pioneers in education technology
H2 Find your partner – Here to help you succeed
H2 Ready to go?
H2 Need advice?
H2 See what’s new in Moodle – Explore our latest releases

A+

Alt Text Quality

All 51 images OK

PASS

All 51 images OK

2 image(s) with alt text over 125 characters

49 image(s) with good alt text

51 images 49 good alt text

Issue	Count
too long	2 image(s)

A+

Form Accessibility

All 7 controls labeled

PASS

All 7 controls labeled

7 control(s) properly labeled

7 controls

7 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
#q1-corp	radio	Workplace Learning	for/id
#q1-gen	radio	Education	for/id
#q3-yes	radio	Yes	for/id
#q3-no	radio	No	for/id
#q5-yes	radio	Yes	for/id
#q5-no	radio	No	for/id
s	text	Search input	aria-label

Link & Button Quality

170 links, 9 buttons — all OK

PASS

170 links, 9 buttons — all OK

2 link(s) open in new tab without warning

Add '(opens in new tab)' to link text or aria-label.

Got: https://services.moodle.com/designing-for-success-webinar?utm_source=moodleco…; https://www.bcorporation.net/en-us/find-a-b-corp/company/moodle-pty-ltd/

168 link(s) with descriptive text

170 links

0 empty

0 generic text

2 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://services.moodle.com/designing-fo…	Open link (external link, open…	new tab	Add '(opens in new tab)' to text
https://www.bcorporation.net/en-us/find-…	(external link, opens in a ne…	new tab	Add '(opens in new tab)' to text

177 links and buttons have descriptive text

Add '(opens in new tab)' to link text or aria-label.

https://services.moodle.com/designing-for-success-webinar?utm_source=moodleco…; https://www.bcorporation.net/en-us/find-a-b-corp/company/moodle-pty-ltd/

Why this matters

Links with target="_blank" without rel="noopener" leak the originating page's window context — security and UX issue.

Learn more ▾

Without rel="noopener", the new tab can navigate the original tab via window.opener (tab-nabbing attack). Modern browsers default to noopener for target=_blank but only since recent versions. Always set rel="noopener noreferrer" explicitly.

Source: MDN target / OWASP

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)

Element	Ratio	Required	FG	BG	Result
h1 Online learning, del…	5.24:1	3.0:1	#000000	#7F7F7F	Pass
h2 Moodle puts the powe…	5.24:1	3.0:1	#000000	#7F7F7F	Pass
h2 Choose your online l…	5.24:1	3.0:1	#000000	#7F7F7F	Pass
h2 Building better lear…	5.24:1	3.0:1	#000000	#7F7F7F	Pass
h2 Who’s using Moodle…	5.24:1	3.0:1	#000000	#7F7F7F	Pass
h2 What our customers s…	5.24:1	3.0:1	#000000	#7F7F7F	Pass
h2 Pioneers in educatio…	5.24:1	3.0:1	#000000	#7F7F7F	Pass
h2 Here to help you suc…	5.24:1	3.0:1	#000000	#7F7F7F	Pass
h2 Ready to go?	5.24:1	3.0:1	#000000	#7F7F7F	Pass
h2 Need advice?	5.24:1	3.0:1	#000000	#7F7F7F	Pass
h2 Explore our latest r…	5.24:1	3.0:1	#000000	#7F7F7F	Pass
h3 Customise your learn…	5.24:1	3.0:1	#000000	#7F7F7F	Pass
h3 Scale your platform …	5.24:1	3.0:1	#000000	#7F7F7F	Pass
h3 Safeguard your LMS d…	5.24:1	3.0:1	#000000	#7F7F7F	Pass
h3 Use anywhere, on any…	5.24:1	3.0:1	#000000	#7F7F7F	Pass
h3 Tap into specialist …	5.24:1	3.0:1	#000000	#7F7F7F	Pass
h3 Moodle LMS	5.24:1	3.0:1	#000000	#7F7F7F	Pass
h3 Moodle Workplace	5.24:1	3.0:1	#000000	#7F7F7F	Pass
h3 Making virtual train…	5.24:1	3.0:1	#000000	#7F7F7F	Pass
h3 Simon Community NI p…	5.24:1	3.0:1	#000000	#7F7F7F	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.

A+

Lighthouse Accessibility Audits

Score 95/100 — 1 failing, 26 passed

PASS

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.

ARIA

Each ARIA `role` supports a specific subset of `aria-*` attributes. Mismatching these invalidates the `aria-*` attributes. Learn how to match ARIA attributes to their roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Products Expand child menu for Products Services Expand child menu for Services… `div#page > header#masthead > div.site-header-wrapper > div#site-menu`

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

○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-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

●Image elements have `[alt]` attributes

●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.

●`button`, `link`, and `menuitem` elements have accessible names

●ARIA attributes are used as specified for the element's role

●`[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

●Links have a discernible name

●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

●No element has a `[tabindex]` value greater than 0

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●Skip links are focusable.

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Identical links have the same purpose.

○`[accesskey]` values are unique

○Elements with `role="dialog"` or `role="alertdialog"` 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

○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.

○Input buttons have discernible text.

○`<input type="image">` elements have `[alt]` text

○Form elements have associated labels

○Links are distinguishable without relying on color.

○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>`.

○All heading elements contain content.

○Uses ARIA roles only on compatible elements

○Image elements do not have `[alt]` attributes that are redundant text.

○Elements with visible text labels have matching accessible names.

○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.

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