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

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
59
GRADE
D
FIX
6
REVIEW
1
PASS
6
INFO
0
Checks
13
6 PASS 1 REVIEW 6 FIX
D
Landmark Structure
Action
2 landmarks
FIX
2 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Warning::
No <nav> landmark found
Warning::
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
BANNER header MAIN (missing!) CONTENTINFO footer

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

Why this matters

Without a <main> landmark, screen-reader users can't skip past the navigation to the page content — every page starts with re-reading the menu.

Learn more ▾

The <main> element marks the page's primary content area. Assistive tech offers a 'jump to main' shortcut — but only if <main> exists. Without it, every page navigation forces re-reading the header. Wrap your primary content in a single <main>.

Source: WAI-ARIA / WCAG 2.4.1

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

D
Favicon & Branding
Action
4 icon(s) detected
FIX
4 icon(s) detected
Warning::
No favicon.ico at site root
Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.
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::
Multiple icon sizes detected
✗ favicon.ico Missing
✓ PNG Icons Present
✗ Apple Touch Missing
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✓ Multiple Sizes Present
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
No navigation patterns
FIX
No navigation patterns
Info::
No breadcrumbs, search, or skip link detected
These navigation aids help users orient themselves and find content efficiently, especially on large sites.
Breadcrumbs
Search
Skip Link
Labeled Navigation
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
0 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
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
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Error (404) - The University of Sydney ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✗
A
Heading Hierarchy
33 headings
PASS
33 headings
Warning::
Multiple H1 headings (2 found)
A page should have only one H1. Multiple H1s dilute the document outline.
Warning::
1 empty heading(s)
Empty headings appear in the document outline but provide no information.
  • H2 Leadership for good starts here
  • H1 (empty)
  • H1 Find a course duplicate H1
  • H2 Find a course
  • H2 Study
  • H2 Study levels
  • H2 About
  • H2 1st in Australia, 25th globally
  • H2 15th for sustainability
  • H2 Our research
  • H3 Research areas
  • H2 Research areas
  • H3 Research centres
  • H2 Research centres
  • H3 Find a researcher
  • H2 Find a researcher
  • H2 Alumni
  • H2 Partner
  • H2 News and opinion
  • H3 Google backs digital frontiers research at University of Sydney
  • H2 Google backs digital frontiers research at University of Sydney
  • H3 University of Sydney ranks 10 disciplines in global top 25
  • H2 University of Sydney ranks 10 disciplines in global top 25
  • H3 Snow Fellowship awarded to University of Sydney researcher
  • H2 Snow Fellowship awarded to University of Sydney researcher
  • H2 Contact us
  • H2 Contact us online
  • H2 Call us
  • H2 Other
  • H2 Media
  • H2 Student links
  • H2 About us
  • H2 Connect

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

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

A+
Alt Text Quality
All 17 images OK
PASS
All 17 images OK
Info::
11 decorative image(s) correctly marked
Info::
6 image(s) with good alt text
17 images 6 good alt text 11 decorative
All images have appropriate alt text.
A+
Form Accessibility
All 1 controls labeled
PASS
All 1 controls labeled
Info::
1 control(s) properly labeled
1 controls
1 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
#m-content-hub__searchbar__inputtextType keywordsfor/id
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 Find a course9.25:13.0:1
#000000
#A6ADB3
Pass
h2 Leadership for good …15.47:13.0:1
#000000
#C8E1EF
Pass
h2 Find a course5.27:13.0:1
#000000
#E64626
Pass
h2 Study18.90:13.0:1
#000000
#F2F3F4
Pass
h2 Study levels18.90:13.0:1
#000000
#F2F3F4
Pass
h2 About18.90:13.0:1
#000000
#F2F3F4
Pass
h2 1st in Australia, 25…18.90:13.0:1
#000000
#F2F3F4
Pass
h2 15th for sustainabil…18.90:13.0:1
#000000
#F2F3F4
Pass
h2 Our research18.90:13.0:1
#000000
#F2F3F4
Pass
h2 Research areas18.90:13.0:1
#000000
#F2F3F4
Pass
h2 Research centres18.90:13.0:1
#000000
#F2F3F4
Pass
h2 Find a researcher18.90:13.0:1
#000000
#F2F3F4
Pass
h2 Alumni18.90:13.0:1
#000000
#F2F3F4
Pass
h2 Partner18.90:13.0:1
#000000
#F2F3F4
Pass
h2 News and opinion18.90:13.0:1
#000000
#F2F3F4
Pass
h2 Google backs digital…18.90:13.0:1
#000000
#F2F3F4
Pass
h2 University of Sydney…18.90:13.0:1
#000000
#F2F3F4
Pass
h2 Snow Fellowship awar…18.90:13.0:1
#000000
#F2F3F4
Pass
h2 Contact us18.90:13.0:1
#000000
#F2F3F4
Pass
h2 Contact us online18.90:13.0:1
#000000
#F2F3F4
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
Lighthouse Accessibility Audits
Score 93/100 — 3 failing, 27 passed
PASS
93

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.

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
About us div.cmp-teaser-content__cta-holder > div.cmp-teaser-content__cta > a.cmp-button > span.cmp-button__text

These are opportunities to improve the legibility of your content.

Names and labels

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.m-global-footer__bottom-top-section > div.m-global-footer-social-medias > div.m-global-footer-social-medias__icon-links-container > a.m-link div.m-global-footer__bottom-top-section > div.m-global-footer-social-medias > div.m-global-footer-social-medias__icon-links-container > a.m-link

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.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Research areas Our breadth of expertise across our faculties and schools is su… div#bespoke-container-f00c8e21c5 > div.m-wrapper-js-card > div.m-card > div.m-card__link
Research centres With more than 150 research centres and networks, we are one … div#bespoke-container-f00c8e21c5 > div.m-wrapper-js-card > div.m-card > div.m-card__link
Find a researcher Our academics are leaders in their fields, publishing thousa… div#bespoke-container-f00c8e21c5 > div.m-wrapper-js-card > div.m-card > div.m-card__link
Google backs digital frontiers research at University of Sydney Six University … div#bespoke-container-9773b6dc19 > div.m-wrapper-js-card > div.m-card > div.m-card__link
University of Sydney ranks 10 disciplines in global top 25 With 10 subjects ran… div#bespoke-container-9773b6dc19 > div.m-wrapper-js-card > div.m-card > div.m-card__link
Snow Fellowship awarded to University of Sydney researcher A University of Sydn… div#bespoke-container-9773b6dc19 > div.m-wrapper-js-card > div.m-card > div.m-card__link
○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.
●`button`, `link`, and `menuitem` elements have accessible names
●ARIA attributes are used as specified for the element's role
●Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
●`[aria-hidden="true"]` elements do not contain focusable descendents
●Elements use only permitted ARIA attributes
●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.
●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.
●Deprecated ARIA roles were not used
●Identical links have the same purpose.
○`[accesskey]` values are unique
○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
○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 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.
○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.
○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