Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

3 PASS 5 REVIEW 5 FIX

404 Error Page

Action

HTTP 404, bare page

FIX

HTTP 404, bare page

Correct 404 status code returned

Got: HTTP 404

Bare server default 404 page

The 404 page has no custom styling. Users hitting a broken link see a generic error with no way to navigate back. Add a custom 404 page with your site navigation and a search bar.

404 Page Quality Default 404 Page

Status Code HTTP 404 ✓Custom Styling ✗Navigation ✗Homepage Link ✗Search Form ✗

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 ✗

Navigation UX

Action

No navigation patterns

FIX

No navigation patterns

11 navigation landmark(s) detected

Hamburger menu detected (responsive design)

No breadcrumbs, search, or skip link detected

These navigation aids help users orient themselves and find content efficiently, especially on large sites.

Breadcrumbs

Skip Link

Labeled Navigation 11 <nav> element(s)

Hamburger Menu

Sticky Navigation Cannot reliably detect (CSS-based)

2 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.

Landmark Structure

17 landmarks

REVIEW

17 landmarks

<main> landmark present

11 <nav> landmark(s) found

2 of 11 <nav> elements are unlabeled

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

Skip navigation link is missing (WCAG 2.4.1)

Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.

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

Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.

Why this matters

Without a skip-nav link, keyboard users tab through every nav item before reaching content — every page, every visit.

Learn more ▾

WCAG 2.4.1 (Bypass Blocks) requires a mechanism to skip past repeated content. The standard implementation is a 'Skip to main content' link that's the first focusable element, visually hidden until focused. Three lines of HTML + four of CSS.

Source: WCAG 2.1 SC 2.4.1

Heading Hierarchy

25 headings

REVIEW

25 headings

Single H1 present

4 empty heading(s)

Empty headings appear in the document outline but provide no information.

H2 UWA Navigation
H2 Study
H2 Life at UWA
H2 Our research
H2 Partners and community
H2 About us
H2 How can we help you?
H2 WE SEEK WISDOM TO SEEK IMPACT
H2 IT ALL STARTS HERE
H2 GLOBAL TOP 100 UNIVERSITY
H2 CHALLENGERS, CHANGERS
H2 Step forward
H3 (empty)
H3 Study your way
H2 Courses you may like
H3 Find your people
H2 (empty)
H2 Be the difference
H2 (empty)
H3 Change the world
H3 Feel the connection to place
H2 Our community
H2 (empty)
H2 Partner with us
H1 The University of Western Australia

Empty headings appear in the document outline but provide no information.

Why this matters

Empty <hN> tags break the document outline — screen-reader users navigating by heading hit dead silence.

Source: WCAG 2.4.6

Alt Text Quality

20 of 27 images have issues

REVIEW

20 of 27 images have issues

20 image(s) with filename as alt text

7 image(s) with good alt text

27 images 7 good alt text 20 generic

Issue	Count
filename	20 image(s)

Favicon & Branding

11 icon(s) detected

REVIEW

11 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

Color Contrast (Screenshot)

Action

20 text elements analyzed, 18 fail WCAG AA

REVIEW

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

2 pass 18 fail WCAG AA

h2 WE SEEK WISDOM TO SEEK IMPACT

2.90:1

#000000

#0032FF

needs 3.0:1 (large text)

24px · bottom of viewport

h2 IT ALL STARTS HERE

2.90:1

#000000

#0032FF

needs 3.0:1 (large text)

24px · bottom of viewport

h2 GLOBAL TOP 100 UNIVERSITY

2.90:1

#000000

#0032FF

needs 3.0:1 (large text)

24px · bottom of viewport

h2 CHALLENGERS, CHANGERS

2.90:1

#000000

#0032FF

needs 3.0:1 (large text)

24px · bottom of viewport

h3 Study your way

2.90:1

#000000

#0032FF

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Find your people

2.90:1

#000000

#0032FF

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Change the world

2.90:1

#000000

#0032FF

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Feel the connection to place

2.90:1

#000000

#0032FF

needs 3.0:1 (large text)

19px · bottom of viewport

title Home | UWA

1.77:1

#000000

#003087

needs 4.5:1 (normal text)

16px · top of page (header area)

a UWA Navigation

1.77:1

#000000

#003087

needs 4.5:1 (normal text)

16px · top of page (header area)

button Study

3.92:1

#000000

#526B98

needs 4.5:1 (normal text)

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

button Partners and community

1.04:1

#000000

#0B0608

needs 4.5:1 (normal text)

16px · above the fold

button About us

1.29:1

#000000

#301B15

needs 4.5:1 (normal text)

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

button More

1.91:1

#000000

#5A3222

needs 4.5:1 (normal text)

16px · above the fold

button Close menu

1.24:1

#000000

#2C1712

needs 4.5:1 (normal text)

16px · above the fold

a Study

1.95:1

#000000

#583524

needs 4.5:1 (normal text)

16px · above the fold

a Explore courses

2.70:1

#000000

#3245BB

needs 4.5:1 (normal text)

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

button Show more

2.90:1

#000000

#0032FF

needs 4.5:1 (normal text)

16px · above the fold

3 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
h2 WE SEEK WISDOM TO SE…	2.90:1	3.0:1	#000000	#0032FF	Fail
h2 IT ALL STARTS HERE	2.90:1	3.0:1	#000000	#0032FF	Fail
h2 GLOBAL TOP 100 UNIVE…	2.90:1	3.0:1	#000000	#0032FF	Fail
h2 CHALLENGERS, CHANGER…	2.90:1	3.0:1	#000000	#0032FF	Fail
h3 Study your way	2.90:1	3.0:1	#000000	#0032FF	Fail
h3 Find your people	2.90:1	3.0:1	#000000	#0032FF	Fail
h3 Change the world	2.90:1	3.0:1	#000000	#0032FF	Fail
h3 Feel the connection …	2.90:1	3.0:1	#000000	#0032FF	Fail
title Home \| UWA	1.77:1	4.5:1	#000000	#003087	Fail
a UWA Navigation	1.77:1	4.5:1	#000000	#003087	Fail
button Study	3.92:1	4.5:1	#000000	#526B98	Fail
button Life at UWA	12.14:1	4.5:1	#000000	#CDC4B3	Pass
button Our research	9.45:1	4.5:1	#000000	#B9AC9D	Pass
button Partners and communi…	1.04:1	4.5:1	#000000	#0B0608	Fail
button About us	1.29:1	4.5:1	#000000	#301B15	Fail
button More	1.91:1	4.5:1	#000000	#5A3222	Fail
button Close menu	1.24:1	4.5:1	#000000	#2C1712	Fail
a Study	1.95:1	4.5:1	#000000	#583524	Fail
a Explore courses	2.70:1	4.5:1	#000000	#3245BB	Fail
button Show more	2.90:1	4.5:1	#000000	#0032FF	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+

Form Accessibility

No form controls

PASS

No form controls

No form controls on this page

No form controls found.

Link & Button Quality

1 issue(s) across 193 links and 57 buttons

PASS

1 issue(s) across 193 links and 57 buttons

1 link(s) with generic text

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

Got: https://www.uwa.edu.au/privacy ("Learn more")

2 link(s) open in new tab without warning

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

Got: https://www.uwa.edu.au/research; https://www.uwa.edu.au/about/our-history

190 link(s) with descriptive text

193 links

0 empty

1 generic text

2 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://www.uwa.edu.au/research	Our research	new tab	Add '(opens in new tab)' to text
https://www.uwa.edu.au/about/our-history	Our history	new tab	Add '(opens in new tab)' to text
https://www.uwa.edu.au/privacy	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Privacy

247 links and buttons have descriptive text

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

https://www.uwa.edu.au/privacy ("Learn 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

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

https://www.uwa.edu.au/research; https://www.uwa.edu.au/about/our-history

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+

Lighthouse Accessibility Audits

Score 96/100 — 1 failing, 28 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.

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
Australia `nav > details.uwa-footer__language > summary._flag-australia > a`

These items highlight common accessibility best practices.

○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

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

●Document has a main landmark.

●Deprecated ARIA roles were not used

●ARIA IDs are unique

●All heading elements contain content.

●Uses ARIA roles only on compatible elements

●Identical links have the same purpose.

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

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

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

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

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