Accessibility

F

Favicon & Branding

Action

2 icon(s) detected

FIX

2 icon(s) detected

No favicon.ico at site root

Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.

HTML icon links detected

Apple touch icon present

✗ favicon.ico Missing

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

D

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.

D

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.

D

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 ✗

F

Navigation UX

Action

1 navigation pattern(s)

FIX

1 navigation pattern(s)

Skip navigation link detected

5 navigation landmark(s) detected

Hamburger menu detected (responsive design)

Breadcrumbs

Search

Skip Link Skip link detected

Labeled Navigation 5 <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.

C

Landmark Structure

Action

7 landmarks

REVIEW

7 landmarks

No <main> landmark found

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

5 <nav> landmark(s) found

4 of 5 <nav> elements are unlabeled

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

No banner (header) landmark

Skip navigation link present

Page Structure — as a screen reader sees it

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

Why this matters

Without a <main> landmark, screen-reader users can't skip past the navigation to the page content — every page starts with re-reading the menu.

Learn more ▾

The <main> element marks the page's primary content area. Assistive tech offers a 'jump to main' shortcut — but only if <main> exists. Without it, every page navigation forces re-reading the header. Wrap your primary content in a single <main>.

Source: WAI-ARIA / WCAG 2.4.1

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

B

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 arrow icon ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗

C

Color Contrast (Screenshot)

Action

20 text elements analyzed, 6 fail WCAG AA

REVIEW

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

14 pass 6 fail WCAG AA 2 pass AA only

h1 RMIT University

2.65:1

#000000

on

#4F4E6E

needs 3.0:1 (large text)

32px · top of page (header area) · over background image/gradient

title RMIT University: A world leader in techn…

1.18:1

#000000

on

#070758

needs 4.5:1 (normal text)

16px · top of page (header area)

span RMIT Europe

1.30:1

#000000

on

#212120

needs 4.5:1 (normal text)

16px · above the fold

span RMIT Global

1.29:1

#000000

on

#22201F

needs 4.5:1 (normal text)

16px · above the fold

span RMIT Vietnam

2.22:1

#000000

on

#474642

needs 4.5:1 (normal text)

16px · above the fold · over background image/gradient

span RMIT UP

3.26:1

#000000

on

#5F5E61

needs 4.5:1 (normal text)

16px · above the fold

2 contrast failures on background images/gradients

These failures are invisible to CSS-based accessibility tools like Lighthouse. The text may be fine on a solid background, but fails when rendered over an image or gradient.

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 RMIT University	2.65:1	3.0:1	#000000	#4F4E6E	Fail
h2 Ready for what’s n…	20.47:1	3.0:1	#000000	#FCFCFC	Pass
h2 RMIT is an internati…	20.47:1	3.0:1	#000000	#FCFCFC	Pass
h2 In the news	20.47:1	3.0:1	#000000	#FCFCFC	Pass
h3 What would you like …	20.47:1	3.0:1	#000000	#FCFCFC	Pass
h3 3000+ scholarships	20.47:1	3.0:1	#000000	#FCFCFC	Pass
h3 24,245 placements	20.47:1	3.0:1	#000000	#FCFCFC	Pass
h3 Ranked #5 in the wor…	20.47:1	3.0:1	#000000	#FCFCFC	Pass
h3 You may be eligible …	20.47:1	3.0:1	#000000	#FCFCFC	Pass
h3 Transfer to RMIT	20.47:1	3.0:1	#000000	#FCFCFC	Pass
h3 Pathway options	20.47:1	3.0:1	#000000	#FCFCFC	Pass
h3 Local student applic…	20.47:1	3.0:1	#000000	#FCFCFC	Pass
h3 Supporting remote Fi…	20.47:1	3.0:1	#000000	#FCFCFC	Pass
title RMIT University: A w…	1.18:1	4.5:1	#000000	#070758	Fail
a SKIP TO CONTENT	5.24:1	4.5:1	#000000	#7F7F7E	Pass
span RMIT Australia	4.77:1	4.5:1	#000000	#7B7872	Pass
span RMIT Europe	1.30:1	4.5:1	#000000	#212120	Fail
span RMIT Global	1.29:1	4.5:1	#000000	#22201F	Fail
span RMIT Vietnam	2.22:1	4.5:1	#000000	#474642	Fail
span RMIT UP	3.26:1	4.5:1	#000000	#5F5E61	Fail

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+

Heading Hierarchy

14 headings

PASS

14 headings

Single H1 present

H1 RMIT University
H2 Ready for what’s next
H3 What would you like to study?
H2 RMIT is an international university of technology, design and enterprise
H3 3000+ scholarships
H3 24,245 placements
H3 Ranked #5 in the world
H3 You may be eligible for a Scholarship
H3 Transfer to RMIT
H3 Pathway options
H3 Local student applications
H2 In the news
H3 Supporting remote First Nations connectivity
H4 Acknowledgement of Country

A

Alt Text Quality

2 of 24 images have issues

PASS

2 of 24 images have issues

2 image(s) with filename as alt text

16 decorative image(s) correctly marked

6 image(s) with good alt text

24 images 6 good alt text 16 decorative 2 generic

Issue	Count
filename	2 image(s)

A+

Form Accessibility

All 3 controls labeled

PASS

All 3 controls labeled

3 control(s) properly labeled

3 controls

3 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
#topnav-search-value	text	Search field	for/id
#topnav-mobi-searchvalue	text	Search	for/id
#search-textfield	text	Search courses	for/id

A+

Link & Button Quality

1 issue(s) across 576 links and 9 buttons

PASS

1 issue(s) across 576 links and 9 buttons

1 link(s) with generic text

Generic link text like 'click here' doesn't describe the destination.

Got: /news/all-news/2026/mar/mapping-the-digital-gap ("Read more")

575 link(s) with descriptive text

576 links

0 empty

1 generic text

0 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
/about/reputation-and-rankings	More reputation and rankings	img no alt	Add alt attribute to the image
/news/all-news/2026/mar/mapping-the-digi…	Read more	generic text	Replace with descriptive text
Before: Read more Suggested: Mapping The Digital Gap
/about/our-values/respect-for-australian…	Learn more about our commitmen…	img no alt	Add alt attribute to the image

584 links and buttons have descriptive text

Generic link text like 'click here' doesn't describe the destination.

/news/all-news/2026/mar/mapping-the-digital-gap ("Read more")

Why this matters

Generic anchor text ('click here', 'read more', 'learn more') tells screen readers and search engines nothing about the destination.

Learn more ▾

Out-of-context lists of links read by AT (one navigation pattern) become useless when every link says 'click here'. Use the destination's title or topic as anchor text. Doubles as SEO win — Google passes anchor-text relevance to the destination.

Source: WCAG 2.4.4 / Google Search Central

A

Lighthouse Accessibility Audits

Score 90/100 — 4 failing, 25 passed

PASS

90

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

Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more about roles and required children elements.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Study with Us Life at RMIT Research Partner About `div.root > div.d-flex > div.col-12 > div.d-flex`

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.

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
News `div > ul.m-0 > li.mb-md-3 > a.shadow-none`

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html `html`

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
Get started `div.verticalcenterwrap > div.verticalcentercontent > div.btn_Wrap_Secondary_stdban > a`

○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

●Image elements have `[alt]` attributes

●Form elements have associated labels

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

●`[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 are distinguishable without relying on color.

●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

●Heading elements appear in a sequentially-descending order

●Deprecated ARIA roles were not used

●Uses ARIA roles only on compatible elements

○`[accesskey]` values are unique

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

○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

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

○The document does not use `<meta http-equiv="refresh">`

○`<object>` elements have alternate text

○Select elements have associated label elements.

○Skip links are focusable.

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

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