Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

4 PASS 4 REVIEW 5 FIX

Favicon & Branding

Action

2 icon(s) detected

FIX

2 icon(s) detected

No favicon.ico at site root

Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.

HTML icon links detected

Apple touch icon present

✗ favicon.ico Missing

✓ PNG Icons Present

✓ Apple Touch Present

✗ 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

Theme color only

FIX

Theme color only

Theme-color present but no dark variant

A theme-color is set but no dark-specific variant was found. The browser toolbar may not adapt for dark mode users.

Got: #fafafa

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 ModePartial Dark Mode

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 9 controls have issues

REVIEW

3 of 9 controls have issues

2 control(s) without accessible label

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

Got: <textarea name="g-recaptcha-response" id="g-recaptcha-response">; <input type="submit" name="form_email_240614_submit" id="form_email_240614_submit">

1 control(s) rely on placeholder only

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

Got: <input name="query" id="autoComplete2">

6 control(s) properly labeled

9 controls

6 labeled

1 placeholder only

2 unlabeled

Control	Type	Label	Method
#autoComplete	input	Search input	aria-label
#q240616_q2_0	radio	Yes	for/id
#q240616_q2_1	radio	No	for/id
#q240633_q1	textarea	What did you come here to do?	for/id
#q240633_q2	textarea	How can we improve this information?	for/id
#languages	select	Language	for/id
#autoComplete2	input	(Search...)	placeholder only
#form_email_240614_submit	submit	(none)	none
#g-recaptcha-response	textarea	(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

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

Link & Button Quality

3 issue(s) across 105 links and 17 buttons

REVIEW

3 issue(s) across 105 links and 17 buttons

3 button(s) with no accessible text

Icon-only buttons need an aria-label so screen readers can announce them.

Got: button.mobile-menu (#94 on page); button#clear-text-btn; button (#252 on page)

105 link(s) with descriptive text

105 links

0 empty

0 generic text

0 new tab

3 empty buttons

Element	Text	Issue	Suggested Fix
https://www.oaic.gov.au/privacy/privacy-…	Make a privacy complaint	img no alt	Add alt attribute to the image
https://www.oaic.gov.au/privacy/notifiab…	Report a data breach	img no alt	Add alt attribute to the image
https://www.oaic.gov.au/freedom-of-infor…	Apply for an Information Commi…	img no alt	Add alt attribute to the image
https://www.oaic.gov.au/rss	Subscribe via RSS	img no alt	Add alt attribute to the image
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label

119 links and buttons have descriptive text

Icon-only buttons need an aria-label so screen readers can announce them.

button.mobile-menu (#94 on page); button#clear-text-btn; button (#252 on page)

Why this matters

Buttons with no accessible text (icon-only, no aria-label) can't be activated by voice control or understood by screen readers.

Source: WCAG 2.1 SC 4.1.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

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title Page Not Found | OAIC ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✗

Color Contrast (Screenshot)

Action

20 text elements analyzed, 12 fail WCAG AA

REVIEW

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

8 pass 12 fail WCAG AA

h2 We use cookies on this site

1.39:1

#000000

#002A3A

needs 3.0:1 (large text)

24px · top of page (header area)

title OAIC

1.39:1

#000000

#002A3A

needs 4.5:1 (normal text)

16px · top of page (header area)

p We use cookies to analyse traffic and to…

1.39:1

#000000

#002A3A

needs 4.5:1 (normal text)

16px · top of page (header area)

a privacy policy

1.39:1

#000000

#002A3A

needs 4.5:1 (normal text)

16px · top of page (header area)

button Close

1.39:1

#000000

#002A3A

needs 4.5:1 (normal text)

16px · above the fold

a Skip to main content

1.52:1

#000000

#023141

needs 4.5:1 (normal text)

16px · above the fold

a News

1.73:1

#000000

#1D3947

needs 4.5:1 (normal text)

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

a Join our team

1.54:1

#000000

#033243

needs 4.5:1 (normal text)

16px · above the fold

a Contact us

1.54:1

#000000

#033243

needs 4.5:1 (normal text)

16px · above the fold

a Home

1.39:1

#000000

#002A3A

needs 4.5:1 (normal text)

16px · above the fold

button Privacy

1.48:1

#000000

#012F41

needs 4.5:1 (normal text)

16px · above the fold

a Privacy

1.67:1

#000000

#0B3846

needs 4.5:1 (normal text)

16px · above the fold

1 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 We’re the independ…	19.25:1	3.0:1	#000000	#ECF7FA	Pass
h2 We use cookies on th…	1.39:1	3.0:1	#000000	#002A3A	Fail
h2 Make a privacy compl…	19.25:1	3.0:1	#000000	#ECF7FA	Pass
h2 Report a data breach	19.25:1	3.0:1	#000000	#ECF7FA	Pass
h2 Apply for an Informa…	19.25:1	3.0:1	#000000	#ECF7FA	Pass
h2 Children’s Online …	19.25:1	3.0:1	#000000	#ECF7FA	Pass
h2 Learn about ...	19.25:1	3.0:1	#000000	#ECF7FA	Pass
h3 Latest news	19.25:1	3.0:1	#000000	#ECF7FA	Pass
h3 Latest blogs	19.25:1	3.0:1	#000000	#ECF7FA	Pass
title OAIC	1.39:1	4.5:1	#000000	#002A3A	Fail
p We use cookies to an…	1.39:1	4.5:1	#000000	#002A3A	Fail
a privacy policy	1.39:1	4.5:1	#000000	#002A3A	Fail
button Close	1.39:1	4.5:1	#000000	#002A3A	Fail
a Skip to main content	1.52:1	4.5:1	#000000	#023141	Fail
a News	1.73:1	4.5:1	#000000	#1D3947	Fail
a Join our team	1.54:1	4.5:1	#000000	#033243	Fail
a Contact us	1.54:1	4.5:1	#000000	#033243	Fail
a Home	1.39:1	4.5:1	#000000	#002A3A	Fail
button Privacy	1.48:1	4.5:1	#000000	#012F41	Fail
a Privacy	1.67:1	4.5:1	#000000	#0B3846	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+

Landmark Structure

4 landmarks

PASS

4 landmarks

<main> landmark present

1 <nav> landmark(s) found

No contentinfo (footer) landmark

Skip navigation link present

Page Structure — as a screen reader sees it

A+

Heading Hierarchy

15 headings

PASS

15 headings

Single H1 present

H2 We use cookies on this site
H1 We’re the independent national regulator for privacy and freedom of information.
H2 Make a privacy complaint
H2 Report a data breach
H2 Apply for an Information Commissioner review
H2 Children’s Online Privacy Code
H2 Learn about ...
H3 Latest news
H4 eSafety and OAIC working together to protect privacy and…
H4 RentTech platforms must stop unfair and excessive personal…
H4 OAIC releases Exposure Draft of the Children’s Online…
H3 Latest blogs
H4 My first six months as FOI commissioner: Building trust and…
H4 Handling privacy complaints – a new approach for a new era
H4 Safer Internet Day: Assuring age while ensuring privacy

A+

Alt Text Quality

All 86 images OK

PASS

All 86 images OK

48 decorative image(s) correctly marked

38 image(s) with good alt text

86 images 38 good alt text 48 decorative

All images have appropriate alt text.

A+

Lighthouse Accessibility Audits

Score 100/100 — 0 failing, 29 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.

●Select elements have associated label elements.

●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

●Touch targets have sufficient size and spacing.

●`[lang]` attributes have a valid value

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

●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

○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

○Skip links are focusable.

○No element has a `[tabindex]` value greater than 0

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

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