Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

5 PASS 4 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 ✗

Form Accessibility

Action

3 of 5 controls have issues

REVIEW

3 of 5 controls have issues

3 control(s) without accessible label

Form controls need a <label>, aria-label, or aria-labelledby for screen readers.

Got: <input type="submit" name="op">; <input type="submit">; <input type="submit" id="edit-submit">

2 control(s) properly labeled

5 controls

2 labeled

0 placeholder only

3 unlabeled

Control	Type	Label	Method
#edit-q	text	Search term	for/id
#edit-search	search	Find your program	for/id
op	submit	(none)	none
input	submit	(none)	none
#edit-submit	submit	(none)	none

Form controls need a <label>, aria-label, or aria-labelledby for screen readers.

Why this matters

Form controls without labels — assistive tech announces 'edit text' with no context; users can't complete forms.

Source: WCAG 2.1 SC 3.3.2

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 - The University of Queensland - The University of Queensland ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗

Favicon & Branding

Action

3 icon(s) detected

REVIEW

3 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

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

title The University of Queensland

1.88:1

#000000

#51247A

needs 4.5:1 (normal text)

16px · top of page (header area)

a Skip to menu

1.88:1

#000000

#51247A

needs 4.5:1 (normal text)

16px · top of page (header area)

a Skip to content

1.59:1

#000000

#411D65

needs 4.5:1 (normal text)

16px · top of page (header area)

a Skip to footer

1.44:1

#000000

#371958

needs 4.5:1 (normal text)

16px · top of page (header area)

button Menu

1.49:1

#000000

#391C5C

needs 4.5:1 (normal text)

16px · above the fold

a Study

1.77:1

#000000

#472965

needs 4.5:1 (normal text)

16px · above the fold

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 MBA your way	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Find a program	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Looking for a UQ exp…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 One of the world's m…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Steps toward reconci…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 UQ teachers remain n…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Events	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 News	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Member of	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Media	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Working with us	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Current students	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Library	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Contact	21.00:1	3.0:1	#000000	#FFFFFF	Pass
title The University of Qu…	1.88:1	4.5:1	#000000	#51247A	Fail
a Skip to menu	1.88:1	4.5:1	#000000	#51247A	Fail
a Skip to content	1.59:1	4.5:1	#000000	#411D65	Fail
a Skip to footer	1.44:1	4.5:1	#000000	#371958	Fail
button Menu	1.49:1	4.5:1	#000000	#391C5C	Fail
a Study	1.77:1	4.5:1	#000000	#472965	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.

Landmark Structure

12 landmarks

PASS

12 landmarks

<main> landmark present

8 <nav> landmark(s) found

1 of 8 <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

25 headings

PASS

25 headings

Single H1 present

H1 MBA your way
H2 Study
H2 Research
H2 Partners and community
H2 About UQ
H2 Find a program
H2 Looking for a UQ expert?
H3 Our campuses
H3 Apply now
H3 Scholarships
H2 One of the world's most respected universities
H2 Steps toward reconciliation
H2 UQ teachers remain nation's most awarded
H2 Events
H3 UQ Ready
H2 News
H3 Older workers seen as less competent and trustworthy by their younger peers
H3 Closing the Gap at risk without urgent focus on urban Indigenous health
H3 Speaking Swahili: African language joins UQ course offerings
H2 Member of
H2 Media
H2 Working with us
H2 Current students
H2 Library
H2 Contact

A+

Alt Text Quality

All 17 images OK

PASS

All 17 images OK

1 image(s) with alt text over 125 characters

16 image(s) with good alt text

17 images 16 good alt text

Issue	Count
too long	1 image(s)

Link & Button Quality

1 issue(s) across 275 links and 11 buttons

PASS

1 issue(s) across 275 links and 11 buttons

1 link(s) with no accessible text

Links without text are announced as raw URLs by screen readers.

Got: a#main-content

274 link(s) with descriptive text

275 links

1 empty

0 generic text

0 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
	(empty)	empty	Add link text or aria-label

285 links and buttons have descriptive text

Links without text are announced as raw URLs by screen readers.

a#main-content

Why this matters

Links with no accessible text (empty <a></a>, image-only no alt, icon-only no aria-label) are unidentifiable to screen readers.

Source: WCAG 2.1 SC 2.4.4

Lighthouse Accessibility Audits

Score 91/100 — 2 failing, 21 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.

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
header.uq-header > div.uq-header__container > div.uq-header__search-toggle > button.nav-primary__toggle `header.uq-header > div.uq-header__container > div.uq-header__search-toggle > button.nav-primary__toggle`

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.

Contrast

Low-contrast text is difficult or impossible for many users to read. Link text that is discernible improves the experience for users with low vision. Learn how to make links distinguishable.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
00025B `nav.uq-footer__meta > ul.uq-footer__footer-list > li.uq-footer__footer-item > a.uq-footer__link`

These are opportunities to improve the legibility of your content.

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

●`[aria-*]` attributes have valid values

●`[aria-*]` attributes are valid and not misspelled

●Image elements have `[alt]` attributes

●Input buttons have discernible text.

●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

●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

●Document has a main landmark.

○`[accesskey]` values are unique

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

○Deprecated ARIA roles were not used

○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.

○`[aria-hidden="true"]` elements do not contain focusable descendents

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

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

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

○Uses ARIA roles only on compatible elements

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

○Identical links have the same purpose.

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