Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

10 PASS 7 REVIEW 7 FIX

Landmark Structure

Action

38 landmarks

FIX

38 landmarks

No <main> landmark found

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

11 <nav> landmark(s) found

11 of 11 <nav> elements are unlabeled

Multiple navigations need aria-label to distinguish them for screen readers.

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

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

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

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

Form Accessibility

Action

28 of 28 controls have issues

FIX

28 of 28 controls have issues

27 control(s) without accessible label

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

Got: <input type="text" id="input-suburb-or-postcode-fa5ce78a-ebc0-4a63-a78c-db3eb4d52541">; <input type="tel">; <input type="tel">; <input type="tel">; <input type="tel">; <input type="tel">; <input type="tel">; <input type="tel">; <input type="tel">; <input type="tel"> (+17 more)

1 control(s) rely on placeholder only

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

Got: <input type="text" id="product-search-autocomplete-f2fa8b0b-20a9-4465-9fea-a78647c247eb">

28 controls

0 labeled

1 placeholder only

27 unlabeled

Control	Type	Label	Method
#product-search-autocomplete-f2fa8b0b-20a9-4465-9fea-a78647c247eb	text	(Product Search)	placeholder only
#input-suburb-or-postcode-fa5ce78a-ebc0-4a63-a78c-db3eb4d52541	text	(none)	none
input	tel	(none)	none
input	tel	(none)	none
input	tel	(none)	none
input	tel	(none)	none
input	tel	(none)	none
input	tel	(none)	none
input	tel	(none)	none
input	tel	(none)	none
input	tel	(none)	none
input	tel	(none)	none
input	tel	(none)	none
input	tel	(none)	none
input	tel	(none)	none
input	tel	(none)	none
input	tel	(none)	none
input	tel	(none)	none
input	tel	(none)	none
input	tel	(none)	none
input	tel	(none)	none
input	tel	(none)	none
input	tel	(none)	none
input	tel	(none)	none
input	tel	(none)	none
input	tel	(none)	none
input	tel	(none)	none
input	tel	(none)	none

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

<input type="text" id="input-suburb-or-postcode-fa5ce78a-ebc0-4a63-a78c-db3eb4d52541">; <input type="tel">; <input type="tel">; <input type="tel">; <input type="tel">; <input type="tel">; <input type="tel">; <input type="tel">; <input type="tel">; <input type="tel"> (+17 more)

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

Mobile Keyboard & Autofill

Action

52/52 eligible field(s) missing autocomplete or inputmode

FIX

52/52 eligible field(s) missing autocomplete or inputmode

26 field(s) missing recommended autocomplete attribute

WCAG 1.3.5 (Level AA): inputs whose purpose maps to a Common Input Purpose value should declare it via `autocomplete=`. Required for password managers, browser autofill, and assistive tech that customizes inputs (e.g., simplified keyboards). Mobile autofill in particular cuts form-completion time by 30-50% when these are present. Affected purposes: tel.

Got: <input type="tel">, <input type="tel">, <input type="tel">, <input type="tel">, <input type="tel">

26 field(s) would benefit from inputmode attribute

Mobile browsers pick the on-screen keyboard layout from `inputmode=` when present (numeric pad, tel dialpad, email keyboard). Without it, users see the default text keyboard and must mode-switch -- 2-3 extra taps per phone-number or numeric-ID field. Type-based defaults exist (`type=tel` shows the tel keyboard on most browsers) but `inputmode` is the explicit, cross-browser way to control this. Affected types: tel.

Got: <input type="tel">, <input type="tel">, <input type="tel">, <input type="tel">, <input type="tel">

Mobile-Readable Font Sizes

Action

66% of visible text renders at >= 12 CSS px (1 below threshold)

FIX

66% of visible text renders at >= 12 CSS px (1 below threshold)

1 text node(s) render below 12 CSS pixels on mobile

Mobile browsers default the root font-size to 16 px; text below ~ 12 px (75% of root) is hard to read without zooming. WCAG 1.4.4 (Resize Text) requires the page to support 200% zoom without loss of functionality -- which most layouts handle, but small base text still costs readability and conversion. Audit which selectors set sizes below 12 px (often footers, fine print, table cells) and bump them to 14-16 px or use rem units that scale with user preferences. Examples: <span> 10.0px ("menu").

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.

Navigation UX

Action

No navigation patterns

FIX

No navigation patterns

11 navigation landmark(s) detected

No breadcrumbs, search, or skip link detected

These navigation aids help users orient themselves and find content efficiently, especially on large sites.

Breadcrumbs

Skip Link

Labeled Navigation 11 <nav> element(s)

Hamburger Menu

Sticky Navigation Cannot reliably detect (CSS-based)

1 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.

Alt Text Quality

Action

5 of 107 images have issues

REVIEW

5 of 107 images have issues

3 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

2 image(s) with generic alt text

102 image(s) with good alt text

107 images 102 good alt text 2 generic 3 missing

Issue	Count
missing	3 image(s)
generic	2 image(s)

Images without alt text are invisible to screen readers.

Why this matters

Each image without alt text is a WCAG 1.1.1 failure — invisible to screen-reader users, lost from Google Image Search.

Learn more ▾

WCAG 2.1 Level A requires text alternatives for non-decorative images. Empty alt='' is fine for decorative; meaningful images need descriptive text. Common fixes: CMS audit + bulk add, build-time linter (alt-text-required ESLint rule), CI gate on Lighthouse a11y score.

Source: WCAG 2.1 SC 1.1.1 / WebAIM Million Report

Link & Button Quality

1 issue(s) across 559 links and 31 buttons

REVIEW

1 issue(s) across 559 links and 31 buttons

4 link(s) open in new tab without warning

Add '(opens in new tab)' to link text or aria-label.

Got: https://www.facebook.com/rseasafety/; https://www.instagram.com/rseasafety; https://www.linkedin.com/company/2554255/admin/feed/posts/; https://rseaoutlet.com.au/

1 button(s) with no accessible text

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

Got: button.btn (#359 on page)

555 link(s) with descriptive text

559 links

0 empty

0 generic text

4 new tab

1 empty buttons

Element	Text	Issue	Suggested Fix
https://www.facebook.com/rseasafety/	Facebook	new tab	Add '(opens in new tab)' to text
https://www.instagram.com/rseasafety	Instagram	new tab	Add '(opens in new tab)' to text
https://www.linkedin.com/company/2554255…	LinkedIn	new tab	Add '(opens in new tab)' to text
https://rseaoutlet.com.au/	Shop Outlet	new tab	Add '(opens in new tab)' to text
<button>	(empty)	empty	Add button text or aria-label

585 links and buttons have descriptive text

Add '(opens in new tab)' to link text or aria-label.

https://www.facebook.com/rseasafety/; https://www.instagram.com/rseasafety; https://www.linkedin.com/company/2554255/admin/feed/posts/; https://rseaoutlet.com.au/

Why this matters

Links with target="_blank" without rel="noopener" leak the originating page's window context — security and UX issue.

Learn more ▾

Without rel="noopener", the new tab can navigate the original tab via window.opener (tab-nabbing attack). Modern browsers default to noopener for target=_blank but only since recent versions. Always set rel="noopener noreferrer" explicitly.

Source: MDN target / OWASP

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

button.btn (#359 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

Iframe Accessibility

2/5 iframe(s) missing title; 0 placeholder(s)

REVIEW

2/5 iframe(s) missing title; 0 placeholder(s)

WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.

WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.

404 Error Page

Action

HTTP 301, custom page

REVIEW

HTTP 301, custom page

Unexpected status code: HTTP 301

Expected HTTP 404 but received 301. This may confuse search engine crawlers.

Got: HTTP 301

Custom styled 404 page

Navigation links present on 404 page

Homepage link present on 404 page

Search form present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 301 ✗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, 7 fail WCAG AA

REVIEW

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

13 pass 7 fail WCAG AA 1 pass AA only

title RSEA Safety – Australia's Workwear and…

1.00:1

#000000

needs 4.5:1 (normal text)

16px · top of page (header area)

button Close

1.00:1

#000000

needs 4.5:1 (normal text)

16px · top of page (header area)

span Contact Us

1.00:1

#000000

needs 4.5:1 (normal text)

16px · top of page (header area)

span About Us

1.00:1

#000000

needs 4.5:1 (normal text)

16px · top of page (header area)

span Career

1.09:1

#000000

#091107

needs 4.5:1 (normal text)

16px · above the fold

span RSEA Rewards

1.40:1

#000000

#102D09

needs 4.5:1 (normal text)

16px · above the fold

span Safety Catalogues

2.61:1

#000000

#175D08

needs 4.5:1 (normal text)

16px · above the fold

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 TRUSTED SAFETY BRAND…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 BEST SELLERS	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Safety Resources	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Latest News	21.00:1	3.0:1	#000000	#FFFFFF	Pass
title RSEA Safety – Aust…	1.00:1	4.5:1	#000000	#000000	Fail
button Close	1.00:1	4.5:1	#000000	#000000	Fail
span Contact Us	1.00:1	4.5:1	#000000	#000000	Fail
span About Us	1.00:1	4.5:1	#000000	#000000	Fail
span About RSEA Safety	7.37:1	4.5:1	#000000	#999999	Pass
span Career	1.09:1	4.5:1	#000000	#091107	Fail
span RSEA Rewards	1.40:1	4.5:1	#000000	#102D09	Fail
span Safety Catalogues	2.61:1	4.5:1	#000000	#175D08	Fail
span Business Services	5.03:1	4.5:1	#000000	#189001	Pass
span New Business and Ten…	12.47:1	4.5:1	#000000	#7ADE66	Pass
span 30-Day Trade Account…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Direct Online Paymen…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Work Uniform Solutio…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Commercial Safety So…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Onsite & Vending Ser…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Digital Ordering	21.00:1	4.5: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.

Lighthouse Accessibility Audits

Action

Score 77/100 — 6 failing, 20 passed

REVIEW

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
fieldset#widget-product-search-742f04b0-3c5e-46e0-b0de-4849c5301093 > div#search-container > div > button.btn `fieldset#widget-product-search-742f04b0-3c5e-46e0-b0de-4849c5301093 > div#search-container > div > button.btn`

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.widget-html-snippet > div.widget-html-snippet > div.topbar-generic-item > a `div.widget-html-snippet > div.widget-html-snippet > div.topbar-generic-item > a`
div.grid-row > div.col-1-2 > div.widget-login-logout > a.main-menu-link `div.grid-row > div.col-1-2 > div.widget-login-logout > a.main-menu-link`
Tenders `div.owl-stage > div.owl-item > div.gallery-slide > a.gallery-slide-link`
Hire quote online `div.owl-stage > div.owl-item > div.gallery-slide > a.gallery-slide-link`
Steel Blue Competion 2026 `div.owl-stage > div.owl-item > div.gallery-slide > a.gallery-slide-link`
Tenders `div.owl-stage > div.owl-item > div.gallery-slide > a.gallery-slide-link`
Hire quote online `div.owl-stage > div.owl-item > div.gallery-slide > a.gallery-slide-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.

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
E1300ST_ `div > div.cv-zone-product-2 > div.cv-zone-product-4 > span.widget-productlist-code`
HF1605__ `div > div.cv-zone-product-2 > div.cv-zone-product-4 > span.widget-productlist-code`
Now: $35.00 `div > div.cv-zone-product-2 > div.cv-zone-product-5 > span.widget-productlist-sale-price`
318598__ `div > div.cv-zone-product-2 > div.cv-zone-product-4 > span.widget-productlist-code`
P727057_ `div > div.cv-zone-product-2 > div.cv-zone-product-4 > span.widget-productlist-code`

These are opportunities to improve the legibility of your content.

Tables and lists

Screen readers require list items (`<li>`) to be contained within a parent `<ul>`, `<ol>` or `<menu>` to be announced properly. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
SHOP OUTLET `div#mobilemenupublic-dadb7e60-02b7-4e95-b8ee-11eeef7979b9 > div#mobile-menu > nav.top-level > li.top-li`
SHOP BY BRAND `div#mobilemenupublic-dadb7e60-02b7-4e95-b8ee-11eeef7979b9 > div#mobile-menu > nav.top-level > li.top-li`
NEW `div#mobilemenupublic-dadb7e60-02b7-4e95-b8ee-11eeef7979b9 > div#mobile-menu > nav.top-level > li.top-li`
WORKWEAR `div#mobilemenupublic-dadb7e60-02b7-4e95-b8ee-11eeef7979b9 > div#mobile-menu > nav.top-level > li.top-li`
WORK BOOTS `div#mobilemenupublic-dadb7e60-02b7-4e95-b8ee-11eeef7979b9 > div#mobile-menu > nav.top-level > li.top-li`
PPE `div#mobilemenupublic-dadb7e60-02b7-4e95-b8ee-11eeef7979b9 > div#mobile-menu > nav.top-level > li.top-li`
WORKPLACE SAFETY `div#mobilemenupublic-dadb7e60-02b7-4e95-b8ee-11eeef7979b9 > div#mobile-menu > nav.top-level > li.top-li`
ROAD SAFETY `div#mobilemenupublic-dadb7e60-02b7-4e95-b8ee-11eeef7979b9 > div#mobile-menu > nav.top-level > li.top-li`
HARDWARE `div#mobilemenupublic-dadb7e60-02b7-4e95-b8ee-11eeef7979b9 > div#mobile-menu > nav.top-level > li.top-li`
HIRE `div#mobilemenupublic-dadb7e60-02b7-4e95-b8ee-11eeef7979b9 > div#mobile-menu > nav.top-level > li.top-li`
BULKY ITEM `div#mobilemenupublic-dadb7e60-02b7-4e95-b8ee-11eeef7979b9 > div#mobile-menu > nav.top-level > li.top-li`
BEST SELLERS `div#mobilemenupublic-dadb7e60-02b7-4e95-b8ee-11eeef7979b9 > div#mobile-menu > nav.top-level > li.top-li`
HELP `div#mobilemenupublic-dadb7e60-02b7-4e95-b8ee-11eeef7979b9 > div#mobile-menu > nav.top-level > li.top-li`
CONTACT US `div#mobilemenupublic-dadb7e60-02b7-4e95-b8ee-11eeef7979b9 > div#mobile-menu > nav.top-level > li.top-li`

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Best practices

Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
head > meta `head > meta`

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html.k-webkit `html.k-webkit`

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

●`[role]` values are valid

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

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

●Image elements have `[alt]` attributes

●Form elements have associated labels

●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

●Document has a `<title>` element

●`<html>` element has a `[lang]` attribute

●`<html>` element has a valid value for its `[lang]` attribute

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

●Touch targets have sufficient size and spacing.

●Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.

●Heading elements appear in a sequentially-descending order

●Deprecated ARIA roles were not used

●Identical links have the same purpose.

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

○Links are distinguishable without relying on color.

○Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

○The document does not use `<meta http-equiv="refresh">`

○`<object>` elements have alternate text

○Select elements have associated label elements.

○Skip links are focusable.

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

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

Heading Hierarchy

11 headings

PASS

11 headings

Single H1 present

H2 BEST SELLERS
H1 TRUSTED SAFETY BRANDS
H2 Safety Resources
H2 Plastic vs Concrete vs Steel? How to choose the right barrier for your next project?
H2 Which safety signs do you need in your workplace?
H2 Understanding the NEW EN388 Mechanical Standards
H2 Latest News
H2 RSEA Safety Albion Park Now Open
H2 RSEA Chirnside Park Now Open
H2 RSEA Forrestdale Now Open
H2 Follow Us

A+

Heading Text Quality

1 heading-text-quality issue(s) detected

PASS

1 heading-text-quality issue(s) detected

2 heading(s) are all-uppercase (excluding short acronyms)

Headings rendered in all-uppercase are a styling choice that should be done via CSS (`text-transform: uppercase`), not by typing the text in caps. Capitalized text is read letter-by-letter by some screen readers (e.g., "H-E-L-L-O W-O-R-L-D" instead of "hello world"). It's also a soft signal of CMS-migration artifacts where the original lowercase intent was lost.

Got: 2 all-caps heading(s)

A+

Form Input Types

1 input(s) using type=text where a specific type would help

PASS

1 input(s) using type=text where a specific type would help

Input "product-search-autocomplete-f2fa8b0b-20a9-4465-9fea-a78647c247eb" should use type="search" (currently type="text")

Field name "product-search-autocomplete-f2fa8b0b-20a9-4465-9fea-a78647c247eb" suggests type="search". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="search">.

A+

Form Input Quality

28 form control(s) checked, no input-semantic issues

PASS

28 form control(s) checked, no input-semantic issues

All form input semantics look correct

A+

Document Language

Lang attribute set to "en"

PASS

Lang attribute set to "en"

<html lang="en"> is set and valid

Got: en

A+

Tabindex Anti-Patterns

32 explicit tabindex attribute(s) checked, no anti-patterns

PASS

32 explicit tabindex attribute(s) checked, no anti-patterns

No tabindex anti-patterns detected

A+

Tap Target Adequacy

All tap targets meet WCAG 2.5.5/2.5.8 sizing

PASS

All tap targets meet WCAG 2.5.5/2.5.8 sizing

All tap targets meet WCAG 2.5.5 (44x44px) sizing

A+

PWA Depth

No PWA depth issues detected

PASS

No PWA depth issues detected

A+

Print Stylesheet

Print styles detected

PASS

Print styles detected

External print stylesheet detected

Got: /Themes/BPDTHEME01/Min/css/theme-print.min.css?v=2023-06-29-B-291094037

Print Stylesheet ✓ Print Optimized

Print stylesheet /Themes/BPDTHEME01/Min/css/theme-print.min.css?v=2023-06-29-B-291094037 ✓Inline @media print Not detected ✗

A+

Mobile UX Depth

2 mobile-depth signal(s) detected

PASS

2 mobile-depth signal(s) detected

No `<meta name="theme-color">` -- browser chrome falls back to default

Without `theme-color`, Android Chrome's status bar and iOS Safari's toolbar fall back to a generic gray. Adding a single hex color in `<meta name="theme-color" content="#0066cc">` tints them to your brand color across all mobile browsers.

iOS auto-link for phone numbers disabled (`format-detection: telephone=no`)

The page sets `<meta name="format-detection" content="telephone=no">`, which prevents iOS Safari from auto-converting phone-number-shaped strings into clickable `tel:` links. Common reason: the auto-detection rewrites mid-paragraph DOM and breaks CSS selectors / JS that depended on the specific text. If you want clickable phone numbers, declare them with explicit `<a href="tel:+1234567890">` and keep auto-detection disabled.

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