Skip to content
https://curtin.edu.au

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
67
GRADE
D
FIX
4
REVIEW
5
PASS
4
INFO
0
Checks
13
4 PASS 5 REVIEW 4 FIX
D
Web Manifest
Action
Not found
FIX
Not found
Info::
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
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::
12 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 12 <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
51 headings, 1 skip(s)
REVIEW
51 headings, 1 skip(s)
Warning::
Multiple H1 headings (3 found)
A page should have only one H1. Multiple H1s dilute the document outline.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H2 Explore Curtin University
  • H3 Go to ...
  • H1 Curtin Open Day 2026
  • H1 Respect at Curtin duplicate H1
  • H1 Year 12 Application Support Webinar duplicate H1
  • H2 Find your course
  • H4 Explore our study areas skipped
  • H2 Get the Curtin edge
  • H3 #1 for undergraduate employment
  • H3 A leader in research and innovation
  • H3 #4 in the world for Mineral and Mining Engineering
  • H2 This is the start of something big
  • H2 How we’re making a difference
  • H3 Fostering inclusion and positivity
  • H3 Protecting our planet
  • H3 Working together
  • H2 Explore our locations
  • H2 What’s happening at Curtin
  • H3 Schools must do more than box-ticking to support Indigenous kids: report
  • H3 Nationally defined framework to recognise Culturally Significant Entities
  • H3 Curtin appoints Cisco leader to foster future tech talent
  • H3 Study looks to Africa to best support Aussies living with chronic conditions
  • H3 Schools must do more than box-ticking to support Indigenous kids: report
  • H3 Nationally defined framework to recognise Culturally Significant Entities
  • H3 Curtin appoints Cisco leader to foster future tech talent
  • H3 Study looks to Africa to best support Aussies living with chronic conditions
  • H3 Schools must do more than box-ticking to support Indigenous kids: report
  • H3 Nationally defined framework to recognise Culturally Significant Entities
  • H3 Creatures on Campus
  • H3 Free bike checks and repairs on campus
  • H3 CurtinLife & Carnaby’s Step Challenge
  • H3 Chronically Crafty Drop-In Craft Sessions
  • H3 Creatures on Campus
  • H3 Free bike checks and repairs on campus
  • H3 CurtinLife & Carnaby’s Step Challenge
  • H3 Chronically Crafty Drop-In Craft Sessions
  • H3 Creatures on Campus
  • H3 Free bike checks and repairs on campus
  • H3 Climate Anxiety: agency, community and action
  • H3 Four-day Work Week: flexibility, productivity and adoption
  • H3 Plastic: circular economy, zero waste and the global plastic crisis
  • H3 Energy: green tech, critical minerals and net zero
  • H3 Climate Anxiety: agency, community and action
  • H3 Four-day Work Week: flexibility, productivity and adoption
  • H3 Plastic: circular economy, zero waste and the global plastic crisis
  • H3 Energy: green tech, critical minerals and net zero
  • H3 Climate Anxiety: agency, community and action
  • H3 Four-day Work Week: flexibility, productivity and adoption
  • H2 Aboriginal and Torres Strait Islander commitment
  • H2 Campuses
  • H2 Teaching areas

A page should have only one H1. Multiple H1s dilute the document outline.

Why this matters

Multiple H1s blur the page's primary topic — screen-reader users and Google both prefer one H1.

Learn more ▾

HTML5's outline algorithm technically allows multiple H1s within sectioning content, but no browser implements it. In practice: one H1 per page. Use H2-H6 for subsections.

Source: WCAG 2.4.6 / Google Search Central

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

B
404 Error Page
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
Info::
Navigation links present on 404 page
Info::
Search form present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Page not found - Curtin University, Perth, Australia ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✓
B
Favicon & Branding
10 icon(s) detected
REVIEW
10 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 Missing
✓ Multiple Sizes Present
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 2 fail WCAG AA
REVIEW

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

18 pass 2 fail WCAG AA
h2 Explore Curtin University
1.19:1
#000000
on
#261508
needs 3.0:1 (large text)
24px · above the fold
h3 Go to ...
1.85:1
#000000
on
#3C3A33
needs 3.0:1 (large text)
19px · mid-page
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Respect at Curtin21.00:13.0:1
#000000
#FFFFFF
Pass
h1 Year 12 Application …21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Explore Curtin Unive…1.19:13.0:1
#000000
#261508
Fail
h2 Find your course21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Get the Curtin edge21.00:13.0:1
#000000
#FFFFFF
Pass
h2 This is the start of…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 How we’re making a…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Explore our location…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 What’s happening a…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Aboriginal and Torre…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Campuses21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Teaching areas21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Go to ...1.85:13.0:1
#000000
#3C3A33
Fail
h3 #1 for undergraduate…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 A leader in research…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 #4 in the world for …21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Fostering inclusion …21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Protecting our plane…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Working together21.00:13.0:1
#000000
#FFFFFF
Pass
title Curtin University | …21.00:14.5:1
#000000
#FFFFFF
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
Landmark Structure
22 landmarks
PASS
22 landmarks
Info::
<main> landmark present
Info::
12 <nav> landmark(s) found
Warning::
8 of 12 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
Info::
Skip navigation link present
Page Structure — as a screen reader sees it
BANNER header NAV "Skip links" MAIN ASIDE "Search bar" 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+
Alt Text Quality
All 57 images OK
PASS
All 57 images OK
Info::
1 decorative image(s) correctly marked
Info::
56 image(s) with good alt text
57 images 56 good alt text 1 decorative
All images have appropriate alt text.
A+
Form Accessibility
All 2 controls labeled
PASS
All 2 controls labeled
Info::
2 control(s) properly labeled
2 controls
2 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
#curtin-global-searchsearchFind courses, people, events, news ...aria-label
#search-form-inputsearchSearch coursesaria-label
A
Lighthouse Accessibility Audits
Score 90/100 — 4 failing, 28 passed
PASS
90

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

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
mimas-block > form.search-form > fieldset.search-bar > button.search-clear mimas-block > form.search-form > fieldset.search-bar > button.search-clear

Including a skip link can help users skip to the main content to save time. Learn more about skip links.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Skip to the content body.home > nav.skip-links > a.skip-to-content
Skip to search body.home > nav.skip-links > a
Skip to secondary navigation body.home > nav.skip-links > 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.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Explore our study areas article.mimas-grid > mimas-block > section.study-areas > h4

These are opportunities to improve keyboard navigation in your application.

Tables and lists

Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Study Study Study at Curtin Find a course Explore course types Browse study are… div.mm-ocd > div.mm-ocd__content > nav.header__mobile-nav > ul.first-level
Study Study at Curtin Find a course Explore course types Browse study areas Ent… nav.header__mobile-nav > ul.first-level > li > ul#sub-menu-1
Life at Curtin Life at Curtin Regional study Living in Perth Learning and study… nav.header__mobile-nav > ul.first-level > li > ul#sub-menu-2
Engage Engage For industry For education providers, teachers and advisors For a… nav.header__mobile-nav > ul.first-level > li > ul#sub-menu-3
About About Curtin Respect at Curtin Rankings and reputation Learning and teach… nav.header__mobile-nav > ul.first-level > li > ul#sub-menu-4
Research Research at Curtin Research areas Higher degrees by research Our resea… nav.header__mobile-nav > ul.first-level > li > ul#sub-menu-5
News & events News Events Media Centre nav.header__mobile-nav > ul.first-level > li > ul#sub-menu-6

These are opportunities to improve the experience of reading tabular or list data using 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-*]` attributes match their roles
●`[aria-hidden="true"]` is not present on the document `<body>`
●`[role]`s have all required `[aria-*]` attributes
●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
●`[role]` values are valid
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●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
●`<frame>` or `<iframe>` elements have a title
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●Links have a discernible name
●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.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●ARIA IDs are unique
●Image elements do not have `[alt]` attributes that are redundant text.
●Elements with visible text labels have matching accessible names.
○`[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
○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
○No form fields have multiple labels
○`<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
○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
○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.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback