Skip to content
https://auckland.ac.nz

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
66
GRADE
D
FIX
5
REVIEW
2
PASS
6
INFO
0
Checks
13
6 PASS 2 REVIEW 5 FIX
D
Favicon & Branding
Action
2 icon(s) detected
FIX
2 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
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'>.
Info::
SVG favicon detected — scales perfectly to any size
✓ favicon.ico Present
✓ PNG Icons Present
✗ Apple Touch Missing
✓ SVG Favicon Present
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
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::
2 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 2 <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
Lighthouse Accessibility Audits
Score 84/100 — 4 failing, 25 passed
REVIEW
84

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.

ARIA

ARIA roles must have valid values in order to perform their intended accessibility functions. Learn more about valid ARIA roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Waipapa Taumata RauUniversity of Auckland header.main-header > div.logo-area > div.container > a.logo
AskAuckland Your online help and support centre. Search our frequently asked q… div.row > div.col-xs-12 > div.askaucklandcomponent > div.ask-auckland
Waipapa Taumata RauUniversity of Auckland div.uoa-footer__container > div.uoa-footer__container > div.uoa-footer__section > a.footer-logo

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.

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
div.WxOChatApp__themeWrapper > div.WxOChatApp__root > div.wxo-float-container > button.chatButton div.WxOChatApp__themeWrapper > div.WxOChatApp__root > div.wxo-float-container > button.chatButton

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.

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
div.uoa-footer__container > div.social_mobile_view > div.uoa-footer__social > ul.footer__social-icon-list
About the University Our faculties and institutes About our research Our campus… div.uoa-footer__container > div.uoa-footer__container > div.uoa-footer__section > ul
Contact us AskAuckland Emergencies and safety on campus Donate to the Universit… div.uoa-footer__container > div.uoa-footer__container > div.uoa-footer__section > ul
Accessibility Copyright Privacy Disclaimer div.uoa-footer__container > div.uoa-footer__container > div.uoa-footer__legal > ul.sub

These are opportunities to improve the experience of reading tabular or list data using 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
Accessibility div.uoa-footer__legal > ul.sub > li > a
Disclaimer div.uoa-footer__legal > ul.sub > li > 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
●`[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.
●`button`, `link`, and `menuitem` elements have accessible names
●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
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●No element has a `[tabindex]` value greater than 0
●`[lang]` attributes have a valid value
●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
○`[accesskey]` values are unique
○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
○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.
○`<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.
A
Landmark Structure
6 landmarks
PASS
6 landmarks
Info::
<main> landmark present
Info::
2 <nav> landmark(s) found
Warning::
1 of 2 <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 MAIN 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+
Heading Hierarchy
36 headings
PASS
36 headings
Info::
Single H1 present
  • H3 Search
  • H2 Main Menu
  • H1 Waipapa Taumata Rau | University of Auckland
  • H2 International student stories
  • H2 Ako tahi ki a mātou | Study with us
  • H3 Mānawa Mai Info Evening - online
  • H3 Accommodation applications open
  • H3 Future international students
  • H2 Ngā taumata ako | Study levels
  • H3 Undergraduate study options
  • H3 Postgraduate study options
  • H3 International study options
  • H3 English language courses
  • H2 Tūhuratia | Discover
  • H3 Entry requirements
  • H3 Talk to a student
  • H3 Support for international students
  • H2 Ngā rauemi me te tautoko | Help and support
  • H3 AskAuckland
  • H4 Top questions
  • H3 Application help
  • H3 Foundation programmes
  • H3 No.1 ranked NZ University
  • H2 Rangahau me te auahatanga | Research and innovation
  • H3 Centre for Innovation and Entrepreneurship
  • H3 Sustainability
  • H3 Mātātaki | The Challenge
  • H2 Ngā kaupapa me ngā hui | News and events
  • H3 Multi-million-dollar gift adds to George Mason legacy at University
  • H3 Acoustic technology helps researchers hear kiwi in the dark
  • H3 How to make your imperfect job more rewarding
  • H3 University events
  • H2 Connect with us
  • H2 Explore
  • H2 Help and support
  • H2 Connect with us
A+
Alt Text Quality
All 22 images OK
PASS
All 22 images OK
Info::
2 decorative image(s) correctly marked
Info::
20 image(s) with good alt text
22 images 20 good alt text 2 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
#uoa-searchsearchSearch for courses, topics, events and everything else.aria-label
kwsearchnone
A
404 Error Page
HTTP 404, custom page
PASS
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::
Homepage link 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 – University of Auckland ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✓
A+
Color Contrast (Screenshot)
20 text elements analyzed, 0 fail WCAG AA
PASS

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

20 pass
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Waipapa Taumata Rau …21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Main Menu21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Connect with us21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Explore21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Help and support21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Connect with us21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Search21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Accommodation applic…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Future international…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Undergraduate study …21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Postgraduate study o…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 International study …21.00:13.0:1
#000000
#FFFFFF
Pass
h3 English language cou…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Entry requirements21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Talk to a student21.00:13.0:1
#000000
#FFFFFF
Pass
h3 AskAuckland21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Application help21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Foundation programme…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Centre for Innovatio…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Sustainability21.00:13.0: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.

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback