Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

6 PASS 2 REVIEW 5 FIX

Favicon & Branding

Action

2 icon(s) detected

FIX

2 icon(s) detected

favicon.ico present at site root

HTML icon links detected

No apple-touch-icon detected

iOS devices use this when users add your site to their home screen. Add <link rel='apple-touch-icon' sizes='180x180' href='/apple-touch-icon.png'>.

✓ favicon.ico Present

✓ PNG Icons Present

✗ Apple Touch Missing

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

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 404 - Page not found ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗

Color Contrast (Screenshot)

Action

20 text elements analyzed, 3 fail WCAG AA

REVIEW

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

17 pass 3 fail WCAG AA

h3 Home

1.40:1

#000000

#1F2A14

needs 3.0:1 (large text)

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

h3 For students

1.24:1

#000000

#161F13

needs 3.0:1 (large text)

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

h3 Research

2.01:1

#000000

#4D3D26

needs 3.0:1 (large text)

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

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
h1 Home	17.62:1	3.0:1	#000000	#EBEBEB	Pass
h2 Explore the Universi…	17.62:1	3.0:1	#000000	#EBEBEB	Pass
h2 Popular Links	17.62:1	3.0:1	#000000	#EBEBEB	Pass
h2 Why UTS?	17.62:1	3.0:1	#000000	#EBEBEB	Pass
h2 #1 young university	17.62:1	3.0:1	#000000	#EBEBEB	Pass
h2 Top 100 worldwide	17.62:1	3.0:1	#000000	#EBEBEB	Pass
h2 93.3% employed	17.62:1	3.0:1	#000000	#EBEBEB	Pass
h2 Acknowledgement of C…	17.62:1	3.0:1	#000000	#EBEBEB	Pass
h2 We use cookies and s…	17.62:1	3.0:1	#000000	#EBEBEB	Pass
h3 Home	1.40:1	3.0:1	#000000	#1F2A14	Fail
h3 For students	1.24:1	3.0:1	#000000	#161F13	Fail
h3 For industry	7.45:1	3.0:1	#000000	#AF9583	Pass
h3 Research	2.01:1	3.0:1	#000000	#4D3D26	Fail
h3 Explore	17.62:1	3.0:1	#000000	#EBEBEB	Pass
h3 For you	17.62:1	3.0:1	#000000	#EBEBEB	Pass
h3 Study at UTS	17.62:1	3.0:1	#000000	#EBEBEB	Pass
h3 Student information	17.62:1	3.0:1	#000000	#EBEBEB	Pass
h3 Admissions	17.62:1	3.0:1	#000000	#EBEBEB	Pass
h3 For you	17.62:1	3.0:1	#000000	#EBEBEB	Pass
h3 POPULAR LINKS	17.62:1	3.0:1	#000000	#EBEBEB	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

37 landmarks

PASS

37 landmarks

<main> landmark present

10 <nav> landmark(s) found

All <nav> elements are properly labeled

Skip navigation link present

Page Structure — as a screen reader sees it

A+

Heading Hierarchy

45 headings

PASS

45 headings

Single H1 present

H3 Home
H3 For students
H3 For industry
H3 Research
H3 Explore
H3 For you
H3 Study at UTS
H3 Student information
H3 Admissions
H3 For you
H3 POPULAR LINKS
H3 Featured industries
H3 Explore
H3 For you
H3 POPULAR LINKS
H3 Explore
H3 For you
H3 POPULAR LINKS
H1 Home
H2 Explore the University of Technology Sydney
H2 Popular Links
H3 Sustainability in action
H3 How research students are helping to drive reef recovery
H3 5 easy ways to take climate action
H3 6 careers that will be crucial for addressing climate change
H3 In a heatwave, a cool library or shopping centre is a lifeline. Do we need more climate shelters?
H3 Looking beyond extraction for renewables
H3 6 careers that will be crucial for addressing climate change
H3 How research students are helping to drive reef recovery
H3 In a heatwave, a cool library or shopping centre is a lifeline. Do we need more climate shelters?
H3 5 easy ways to take climate action
H3 Looking beyond extraction for renewables
H3 Clean green machine
H2 Why UTS?
H2 #1 young university
H2 Top 100 worldwide
H2 93.3% employed
H2 Acknowledgement of Country
H3 Follow us
H3 A member of
H3 Study
H3 Engage
H3 About
H3 Staff and students
H2 We use cookies and similar technologies to provide a better experience

A+

Alt Text Quality

All 28 images OK

PASS

All 28 images OK

15 decorative image(s) correctly marked

13 image(s) with good alt text

28 images 13 good alt text 15 decorative

All images have appropriate alt text.

Form Accessibility

1 of 2 controls have issues

PASS

1 of 2 controls have issues

1 control(s) rely on placeholder only

Placeholder text disappears on focus and is not a reliable label.

Got: <input type="text">

1 control(s) properly labeled

2 controls

1 labeled

1 placeholder only

0 unlabeled

Control	Type	Label	Method
#global-search	text	Search:	for/id
input	text	(Search courses, people, research or something else)	placeholder only

Placeholder text disappears on focus and is not a reliable label.

Why this matters

Placeholder-only labels disappear when the user starts typing — they must remember what the field was for.

Learn more ▾

Placeholders are NOT labels. They vanish on input, fail color contrast checks (most are gray), and don't satisfy WCAG SC 3.3.2. Always use a real <label> alongside (or aria-labelledby).

Source: WCAG 2.1 SC 3.3.2 / Nielsen Norman

A+

Link & Button Quality

154 links, 30 buttons — all OK

PASS

154 links, 30 buttons — all OK

154 link(s) with descriptive text

154 links

0 empty

0 generic text

0 new tab

0 empty buttons

All links and buttons have descriptive accessible text.

184 links and buttons have descriptive text

A+

Lighthouse Accessibility Audits

Score 100/100 — 0 failing, 32 passed

PASS

100

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.

○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

●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

●ARIA IDs are unique

●`<video>` elements contain a `<track>` element with `[kind="captions"]`

●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

○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

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

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