Skip to content
https://www.meshdesignprojects.com.au

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
80
GRADE
B
FIX
5
REVIEW
5
PASS
14
INFO
0
Checks
24
14 PASS 5 REVIEW 5 FIX
D
Landmark Structure
Action
4 landmarks
FIX
4 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Info::
2 <nav> landmark(s) found
Warning::
2 of 2 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
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 NAV 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

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

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
Theme color only
FIX
Theme color only
Info::
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: #ffffff
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 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.

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::
2 navigation landmark(s) detected
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 2 <nav> element(s)
Back to Top
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.
C
404 Error Page
Action
Could not test
REVIEW
Could not test
Info::
404 page could not be tested
The 404 page check encountered an error. This may be due to a timeout or network issue.

404 page quality check not available.

C
Favicon & Branding
Action
3 icon(s) detected
REVIEW
3 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::
Apple touch icon present
Info::
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, 20 fail WCAG AA
REVIEW

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

0 pass 20 fail WCAG AA
h2 Comprehensive Design Solutions with a Fo…
1.07:1
#000000
on
#0E0B0E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Our Expertise
1.07:1
#000000
on
#0E0B0E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 AS SEEN IN
1.07:1
#000000
on
#0E0B0E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Melbourne Home & Building Design
1.07:1
#000000
on
#0E0B0E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 New Build
1.07:1
#000000
on
#0E0B0E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Alterations and Additions
1.07:1
#000000
on
#0E0B0E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Our Reviews
1.07:1
#000000
on
#0E0B0E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Our Melbourne Building Design Process
1.07:1
#000000
on
#0E0B0E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Design the Home You’ve Always Wanted w…
1.07:1
#000000
on
#0E0B0E
needs 3.0:1 (large text)
24px · bottom of viewport
h3 Welcome to Your Design Journey
1.07:1
#000000
on
#0E0B0E
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Pre-Design
1.07:1
#000000
on
#0E0B0E
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Concept Design
1.07:1
#000000
on
#0E0B0E
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Welcome to Your Design Journey
1.07:1
#000000
on
#0E0B0E
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Pre-Design
1.07:1
#000000
on
#0E0B0E
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Concept Design
1.07:1
#000000
on
#0E0B0E
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Working Drawings
1.07:1
#000000
on
#0E0B0E
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Building Permit
1.07:1
#000000
on
#0E0B0E
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Building Quotes
1.07:1
#000000
on
#0E0B0E
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Working Drawings
1.07:1
#000000
on
#0E0B0E
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Building Permit
1.07:1
#000000
on
#0E0B0E
needs 3.0:1 (large text)
19px · bottom of viewport
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 Comprehensive Design…1.07:13.0:1
#000000
#0E0B0E
Fail
h2 Our Expertise1.07:13.0:1
#000000
#0E0B0E
Fail
h2 AS SEEN IN1.07:13.0:1
#000000
#0E0B0E
Fail
h2 Melbourne Home & Bui…1.07:13.0:1
#000000
#0E0B0E
Fail
h2 New Build1.07:13.0:1
#000000
#0E0B0E
Fail
h2 Alterations and Addi…1.07:13.0:1
#000000
#0E0B0E
Fail
h2 Our Reviews1.07:13.0:1
#000000
#0E0B0E
Fail
h2 Our Melbourne Buildi…1.07:13.0:1
#000000
#0E0B0E
Fail
h2 Design the Home You…1.07:13.0:1
#000000
#0E0B0E
Fail
h3 Welcome to Your Desi…1.07:13.0:1
#000000
#0E0B0E
Fail
h3 Pre-Design1.07:13.0:1
#000000
#0E0B0E
Fail
h3 Concept Design1.07:13.0:1
#000000
#0E0B0E
Fail
h3 Welcome to Your Desi…1.07:13.0:1
#000000
#0E0B0E
Fail
h3 Pre-Design1.07:13.0:1
#000000
#0E0B0E
Fail
h3 Concept Design1.07:13.0:1
#000000
#0E0B0E
Fail
h3 Working Drawings1.07:13.0:1
#000000
#0E0B0E
Fail
h3 Building Permit1.07:13.0:1
#000000
#0E0B0E
Fail
h3 Building Quotes1.07:13.0:1
#000000
#0E0B0E
Fail
h3 Working Drawings1.07:13.0:1
#000000
#0E0B0E
Fail
h3 Building Permit1.07:13.0:1
#000000
#0E0B0E
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 89/100 — 3 failing, 22 passed
REVIEW
89

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
Book a Meeting div.et_pb_row > div.et_pb_column > div.et_pb_button_module_wrapper > a.et_pb_button
Get Started div.et_pb_row > div.et_pb_column > div.et_pb_button_module_wrapper > a.et_pb_button
Book a Meeting div.et_pb_row > div.et_pb_column > div.et_pb_button_module_wrapper > a.et_pb_button
Book a Meeting div#column-reverse > div.et_pb_column > div.et_pb_button_module_wrapper > a.et_pb_button
Learn More div.et_pb_row > div.et_pb_column > div.et_pb_button_module_wrapper > a.et_pb_button
Book a Meeting div.et_pb_row > div.et_pb_column > div.et_pb_button_module_wrapper > a.et_pb_button
Together, we’ll create a home that perfectly matches your vision and lifestyle. div.et_pb_column > div.et_pb_module > div.et_pb_text_inner > p
Book a Meeting div.et_pb_row > div.et_pb_column > div.et_pb_button_module_wrapper > a.et_pb_button
425 Smith St, Fitzroy VIC 3065, Australia ul.dsm_icon_list_items > li.dsm_icon_list_child > a > span.dsm_icon_list_text
md@meshdesignprojects.com.au ul.dsm_icon_list_items > li.dsm_icon_list_child > a > span.dsm_icon_list_text
0400 438 295 ul.dsm_icon_list_items > li.dsm_icon_list_child > a > span.dsm_icon_list_text
Sites at Scale div.et_pb_module > div.et_pb_text_inner > strong > a

These are opportunities to improve the legibility of your content.

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.js html.js

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
●`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
●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
●No element has a `[tabindex]` value greater than 0
●Touch targets have sufficient size and spacing.
●Heading elements appear in a sequentially-descending order
●Deprecated ARIA roles were not used
○`[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
○Buttons have an accessible name
○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
○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.
○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+
Heading Hierarchy
34 headings
PASS
34 headings
Info::
Single H1 present
  • H1 Building Designer in Melbourne for New Homes, Renovations & Extensions
  • H2 Comprehensive Design Solutions with a Focus on Sustainability and Modern Living
  • H2 Melbourne Building Designers for Homes & Extensions
  • H2 Our Expertise
  • H2 AS SEEN IN
  • H2 Melbourne Home & Building Design
  • H2 New Build
  • H2 Alterations and Additions
  • H2 Our Reviews
  • H2 Mike Kane
  • H2 Kirsty Fisher
  • H2 Matt Forssman
  • H2 Jennifer Green
  • H2 Scott G Wright Photography
  • H2 Roberta Thomson
  • H2 Our Melbourne Building Design Process
  • H3 Welcome to Your Design Journey
  • H3 Pre-Design
  • H3 Concept Design
  • H3 Welcome to Your Design Journey
  • H3 Pre-Design
  • H3 Concept Design
  • H3 Design Development
  • H3 Planning Permit and Application
  • H3 Working Drawings
  • H3 Building Permit
  • H3 Building Quotes
  • H3 Design Development
  • H3 Planning Permit and Application
  • H3 Working Drawings
  • H3 Building Permit
  • H3 Building Quotes
  • H3 We’re Now Ready to Build your Dream Home
  • H2 Design the Home You’ve Always Wanted with Melbourne’s Best
A+
Heading Text Quality
1 heading-text-quality issue(s) detected
PASS
1 heading-text-quality issue(s) detected
Info::
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+
Alt Text Quality
All 33 images OK
PASS
All 33 images OK
Info::
31 decorative image(s) correctly marked
Info::
2 image(s) with good alt text
33 images 2 good alt text 31 decorative
All images have appropriate alt text.
A+
Form Accessibility
No form controls
PASS
No form controls
Info::
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
Info::
No form controls on this page
A+
Form Input Quality
No form controls on this page
PASS
No form controls on this page
Info::
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
Info::
No form controls on this page
A+
Document Language
Lang attribute set to "en-US"
PASS
Lang attribute set to "en-US"
Info::
<html lang="en-US"> is set and valid
Got: en-US
A+
Tabindex Anti-Patterns
6 explicit tabindex attribute(s) checked, no anti-patterns
PASS
6 explicit tabindex attribute(s) checked, no anti-patterns
Info::
No tabindex anti-patterns detected
A+
Iframe Accessibility
No iframes on this page
PASS
No iframes on this page
Info::
No iframes on this page
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
Info::
All tap targets meet WCAG 2.5.5 (44x44px) sizing
A+
Mobile-Readable Font Sizes
All 79 visible text node(s) render at >= 12 CSS pixels
PASS
All 79 visible text node(s) render at >= 12 CSS pixels
Info::
All text uses legible mobile font sizes (>= 12 CSS px)
A+
PWA Depth
No PWA depth issues detected
PASS
No PWA depth issues detected
Info::
No PWA depth issues detected
A+
Mobile UX Depth
1 mobile-depth signal(s) detected
PASS
1 mobile-depth signal(s) detected
Info::
Browser-chrome `theme-color` meta tag present
The page sets `<meta name="theme-color" content="...">`, which Android Chrome uses to tint the status bar and iOS Safari uses for the toolbar background. Brand polish that costs nothing and Just Works.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback