Accessibility

F

Heading Hierarchy

Action

19 headings, 4 skip(s)

FIX

19 headings, 4 skip(s)

Single H1 present

Heading level skipped: H2 → H4 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H2 → H5 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H2 → H5 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H2 → H6 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

1 empty heading(s)

Empty headings appear in the document outline but provide no information.

H1 We Strategize, You Thrive
H2 Ultimate Solution for Your Construction Needs
H4 Asbestos Remediation Services skipped
H2 Industrial Representation
H2 Our Portfolio
H5 Goodwood Station, Civil and Power Works, Wilcannia skipped
H6 View Project
H5 Auburn Park Extension, Asbestos Remediation Works, Auburn
H6 View Project
H5 Drainage and Pavement Works, Brand St Artarmon- Sydney Metro City & Southwest Line-Wide Works
H6 View Project
H2 Assured Quality
H2 Our ISO Certifications
H5 contact@wbsnsw.com.au skipped
H5 T: (02) 8074 1172
H5 (empty)
H2 Company
H6 Australia skipped
H2 Info

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

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

F

404 Error Page

Action

HTTP 503, bare page

FIX

HTTP 503, bare page

Unexpected status code: HTTP 503

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

Got: HTTP 503

Bare server default 404 page

The 404 page has no custom styling. Users hitting a broken link see a generic error with no way to navigate back. Add a custom 404 page with your site navigation and a search bar.

404 Page Quality Default 404 Page

Status Code HTTP 503 ✗Custom Styling ✗Navigation ✗Homepage Link ✗Search Form ✗

D

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.

D

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.

D

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 ✗

F

Navigation UX

Action

1 navigation pattern(s)

FIX

1 navigation pattern(s)

Skip navigation link detected

3 navigation landmark(s) detected

Hamburger menu detected (responsive design)

Breadcrumbs

Search

Skip Link Skip link detected

Labeled Navigation 3 <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

Alt Text Quality

2 of 32 images have issues

REVIEW

2 of 32 images have issues

2 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

6 decorative image(s) correctly marked

24 image(s) with good alt text

32 images 24 good alt text 6 decorative 2 missing

Issue	Count
missing	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

C

Link & Button Quality

Action

5 issue(s) across 49 links and 3 buttons

REVIEW

5 issue(s) across 49 links and 3 buttons

4 link(s) with no accessible text

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

Got: https://wbsengineers.com.au/; https://wbsengineers.com.au/; https://wbsengineers.com.au/; https://wbsengineers.com.au/

1 link(s) with generic text

Generic link text like 'click here' doesn't describe the destination.

Got: https://wbsengineers.com.au/remediation-works/ ("Learn more")

2 link(s) open in new tab without warning

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

Got: https://twitter.com/WBSengineers; https://www.linkedin.com/company/wbs-engineers/

42 link(s) with descriptive text

49 links

4 empty

1 generic text

2 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://wbsengineers.com.au/	(empty)	empty	Add link text or aria-label
https://wbsengineers.com.au/	(empty)	empty	Add link text or aria-label
https://wbsengineers.com.au/	(empty)	empty	Add link text or aria-label
https://wbsengineers.com.au/	(empty)	empty	Add link text or aria-label
https://wbsengineers.com.au/remediation-…	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Remediation Works
https://twitter.com/WBSengineers	Twitter	new tab	Add '(opens in new tab)' to text
https://www.linkedin.com/company/wbs-eng…	Linkedin	new tab	Add '(opens in new tab)' to text

45 links and buttons have descriptive text

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

https://wbsengineers.com.au/; https://wbsengineers.com.au/; https://wbsengineers.com.au/; https://wbsengineers.com.au/

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

Generic link text like 'click here' doesn't describe the destination.

https://wbsengineers.com.au/remediation-works/ ("Learn more")

Why this matters

Generic anchor text ('click here', 'read more', 'learn more') tells screen readers and search engines nothing about the destination.

Learn more ▾

Out-of-context lists of links read by AT (one navigation pattern) become useless when every link says 'click here'. Use the destination's title or topic as anchor text. Doubles as SEO win — Google passes anchor-text relevance to the destination.

Source: WCAG 2.4.4 / Google Search Central

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

https://twitter.com/WBSengineers; https://www.linkedin.com/company/wbs-engineers/

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

B

Tap Target Adequacy

2 tap target(s) too small or too close together

REVIEW

2 tap target(s) too small or too close together

2 tap target(s) too small or too close to neighbors

WCAG 2.5.5 (Level AAA) requires interactive targets to be at least 44x44 CSS pixels; WCAG 2.5.8 (Level AA, added in 2.2) requires 24x24 minimum. Failing targets cause mis-taps for users with motor impairments, large fingers, or shaky hands -- and are a major bounce-rate driver on mobile commerce flows. Lighthouse measures rendered rects + adjacent-element spacing; the failing list is in the Lighthouse 'tap-targets' audit detail panel.

C

Favicon & Branding

Action

3 icon(s) detected

REVIEW

3 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

Multiple icon sizes detected

✗ favicon.ico Missing

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✓ Multiple Sizes Present

C

Color Contrast (Screenshot)

Action

20 text elements analyzed, 10 fail WCAG AA

REVIEW

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

10 pass 10 fail WCAG AA

a Home

4.28:1

#000000

on

#6F7172

needs 4.5:1 (normal text)

16px · top of page (header area) · over background image/gradient

a Who We Are

1.11:1

#000000

on

#101113

needs 4.5:1 (normal text)

16px · top of page (header area)

a Services

1.56:1

#000000

on

#18323B

needs 4.5:1 (normal text)

16px · above the fold

a Portfolio

1.70:1

#000000

on

#21383F

needs 4.5:1 (normal text)

16px · above the fold

a People And Culture

1.65:1

#000000

on

#1E363B

needs 4.5:1 (normal text)

16px · above the fold

a Reconciliation

1.58:1

#000000

on

#1D3339

needs 4.5:1 (normal text)

16px · above the fold

a Asbestos Remediation

1.51:1

#000000

on

#1D2E3B

needs 4.5:1 (normal text)

16px · above the fold

a Home

1.60:1

#000000

on

#2C3135

needs 4.5:1 (normal text)

16px · above the fold

a Who We Are

1.51:1

#000000

on

#332B26

needs 4.5:1 (normal text)

16px · above the fold

a Services

1.40:1

#000000

on

#2F2424

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 Strategize, You T…	19.61:1	3.0:1	#000000	#F7F7F8	Pass
h2 Ultimate Solution fo…	19.61:1	3.0:1	#000000	#F7F7F8	Pass
h2 Industrial Represent…	19.61:1	3.0:1	#000000	#F7F7F8	Pass
h2 Our Portfolio	19.61:1	3.0:1	#000000	#F7F7F8	Pass
h2 Assured Quality	19.61:1	3.0:1	#000000	#F7F7F8	Pass
h2 Our ISO Certificatio…	19.61:1	3.0:1	#000000	#F7F7F8	Pass
h2 Company	19.61:1	3.0:1	#000000	#F7F7F8	Pass
h2 Info	19.61:1	3.0:1	#000000	#F7F7F8	Pass
title WBS Engineers \| We s…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Skip to content	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Home	4.28:1	4.5:1	#000000	#6F7172	Fail
a Who We Are	1.11:1	4.5:1	#000000	#101113	Fail
a Services	1.56:1	4.5:1	#000000	#18323B	Fail
a Portfolio	1.70:1	4.5:1	#000000	#21383F	Fail
a People And Culture	1.65:1	4.5:1	#000000	#1E363B	Fail
a Reconciliation	1.58:1	4.5:1	#000000	#1D3339	Fail
a Asbestos Remediation	1.51:1	4.5:1	#000000	#1D2E3B	Fail
a Home	1.60:1	4.5:1	#000000	#2C3135	Fail
a Who We Are	1.51:1	4.5:1	#000000	#332B26	Fail
a Services	1.40:1	4.5:1	#000000	#2F2424	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.

B

Lighthouse Accessibility Audits

Score 86/100 — 4 failing, 24 passed

REVIEW

86

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
LEARN MORE `div.elementor-button-wrapper > a.elementor-button > span.elementor-button-content-wrapper > span.elementor-button-text`

These are opportunities to improve the legibility of your content.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Asbestos Remediation Services `div.elementor-widget-wrap > div.elementor-element > div.elementor-widget-container > h4.elementor-heading-title`
Goodwood Station, Civil and Power Works, Wilcannia `div.elementor-widget-wrap > div.elementor-element > div.elementor-widget-container > h5.elementor-heading-title`
contact@wbsnsw.com.au `div.footer-widget-area > div.ast-header-html > div.ast-builder-html-element > h5`
Australia `section#block-17 > div.wp-block-media-text > div.wp-block-media-text__content > h6.wp-block-heading`

These are opportunities to improve keyboard navigation in your application.

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.site-branding > div.ast-site-title-wrap > span.site-title > a `div.site-branding > div.ast-site-title-wrap > span.site-title > a`

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.

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
Services `nav.menu-footer-main-menu-container > ul#menu-footer-main-menu > li.menu-item > a.menu-link`
Portfolio `nav.menu-footer-main-menu-container > ul#menu-footer-main-menu > li.menu-item > a.menu-link`

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

●Buttons have an accessible name

●Image elements have `[alt]` attributes

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

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

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

●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

●Skip links are focusable.

●Document has a main landmark.

●Deprecated ARIA roles were not used

●`<video>` elements contain a `<track>` element with `[kind="captions"]`

●All heading elements contain content.

●Uses ARIA roles only on compatible elements

●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

○Form elements have associated labels

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

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

○`[lang]` attributes have a valid value

○Tables have different content in the summary attribute and `<caption>`.

○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

Landmark Structure

9 landmarks

PASS

9 landmarks

<main> landmark present

3 <nav> landmark(s) found

All <nav> elements are properly labeled

Skip navigation link present

Skip link target(s) don't exist on page: #content

The skip-link anchor (e.g., `href="#main"`) points at an ID that has no corresponding element on the page. Activating the link does nothing -- a silent WCAG 2.4.1 failure that the visual link presence hides. Add `id="main"` (or whichever matches the href) to the target landmark.

Page Structure — as a screen reader sees it

The skip-link anchor (e.g., `href="#main"`) points at an ID that has no corresponding element on the page. Activating the link does nothing -- a silent WCAG 2.4.1 failure that the visual link presence hides. Add `id="main"` (or whichever matches the href) to the target landmark.

Why this matters

Skip link points at an ID that doesn't exist on the page. The link looks fine visually but does nothing when activated -- silent WCAG 2.4.1 failure.

Learn more ▾

Find the target landmark (typically <main> or the first <h1>) and add `id="..."` matching the skip link's href fragment. Test by tabbing to the skip link and pressing Enter -- focus should jump to the target.

Source: WCAG 2.1 SC 2.4.1

A+

Heading Text Quality

1 heading-text-quality issue(s) detected

PASS

1 heading-text-quality issue(s) detected

1 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: 1 all-caps heading(s)

A+

Form Accessibility

No form controls

PASS

No form controls

No form controls on this page

No form controls found.

A+

Form Input Types

No form controls on this page

PASS

No form controls on this page

A+

Form Input Quality

No form controls on this page

PASS

No form controls on this page

A+

Mobile Keyboard & Autofill

No form controls -- mobile keyboard check is N/A

PASS

No form controls -- mobile keyboard check is N/A

No form controls on this page

A+

Document Language

Lang attribute set to "en-US"

PASS

Lang attribute set to "en-US"

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

Got: en-US

A+

Tabindex Anti-Patterns

No explicit tabindex attributes found

PASS

No explicit tabindex attributes found

A+

Iframe Accessibility

No iframes on this page

PASS

No iframes on this page

A+

Mobile-Readable Font Sizes

All 45 visible text node(s) render at >= 12 CSS pixels

PASS

All 45 visible text node(s) render at >= 12 CSS pixels

All text uses legible mobile font sizes (>= 12 CSS px)

A+

PWA Depth

No PWA depth issues detected

PASS

No PWA depth issues detected

A+

Mobile UX Depth

1 mobile-depth signal(s) detected

PASS

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