Skip to content
https://terrebleu.ca

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
46
GRADE
F
FIX
7
REVIEW
4
PASS
2
INFO
0
Checks
13
2 PASS 4 REVIEW 7 FIX
F
404 Error Page
Action
HTTP 429, custom page
FIX
HTTP 429, custom page
Warning::
Unexpected status code: HTTP 429
Expected HTTP 404 but received 429. This may confuse search engine crawlers.
Got: HTTP 429
Info::
Custom styled 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 429 ✗Page Title Just a moment... ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗
F
Favicon & Branding
Action
No icons detected
FIX
No icons 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::
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'>.
Critical::
No favicon or icon links detected
Your site will show the browser's generic page icon in tabs, bookmarks, and home screens.
✗ favicon.ico Missing
✗ PNG Icons Missing
✗ Apple Touch Missing
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
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: #24417e
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
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Skip navigation link detected
Info::
2 navigation landmark(s) detected
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 2 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
2 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
C
Heading Hierarchy
Action
14 headings, 2 skip(s)
REVIEW
14 headings, 2 skip(s)
Warning::
Multiple H1 headings (3 found)
A page should have only one H1. Multiple H1s dilute the document outline.
Warning::
Heading level skipped: H2 → H6 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H5 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H1 Terre Bleu
  • H1 Live Lavender Plants PRE-ORDER 2026 duplicate H1
  • H2 Fennario Meadows
  • H6 Please note that the farm is not currently open to visitors. skipped
  • H2 Favourites View all
  • H1 Lavender Citrus Hand Cream duplicate H1
  • H2 Learn Lavender View all
  • H2 Instagram
  • H2 Policies
  • H2 Jobs/Our Farm
  • H2 Elora Boutique Hours
  • H5 Terre Bleu skipped
  • H5 Farm Not Open To Public
  • H2 Currency

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

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

B
Form Accessibility
2 of 10 controls have issues
REVIEW
2 of 10 controls have issues
Critical::
2 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <select name="id">; <select name="id">
Info::
8 control(s) properly labeled
10 controls
8 labeled
0 placeholder only
2 unlabeled
ControlTypeLabelMethod
#SearchsearchSearchfor/id
#ProductSelect-template--21487857074199__featured_product_CcCbPj-7037640507415-option-pickup-location-please-select-where-you-will-pickup-your-plants-see-below-for-details-EloraradioElorafor/id
#ProductSelect-template--21487857074199__featured_product_CcCbPj-7037640507415-option-pickup-location-please-select-where-you-will-pickup-your-plants-see-below-for-details-BurlingtonradioBurlingtonfor/id
#ProductSelect-template--21487857074199__featured_product_CcCbPj-7037640507415-option-variety-PhenomenalradioPhenomenalfor/id
#ProductSelect-template--21487857074199__featured_product_CcCbPj-7037640507415-option-variety-Super+BlueradioSuper Bluefor/id
#ProductSelect-template--21487857074199__featured_product_CcCbPj-7037640507415-option-variety-MelissaradioMelissafor/id
#ProductSelect-template--21487857074199__featured_product_CcCbPj-7037640507415-option-variety-FolgateradioFolgatefor/id
#ProductSelect-template--21487857074199__featured_product_CcCbPj-7037640507415-option-variety-Fern+Leaf+%28Indoor+Variety%29radioFern Leaf (Indoor Variety)for/id
idselect(none)none
idselect(none)none

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

<select name="id">; <select name="id">

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

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
title Terre Bleu
1.30:1
#000000
on
#12203F
needs 4.5:1 (normal text)
16px · top of page (header area)
a Skip to content
1.30:1
#000000
on
#12203F
needs 4.5:1 (normal text)
16px · top of page (header area)
span Our Farm Is Currently Not Open To The Pu…
1.30:1
#000000
on
#12203F
needs 4.5:1 (normal text)
16px · top of page (header area)
span Close menu
1.59:1
#000000
on
#2A303C
needs 4.5:1 (normal text)
16px · top of page (header area) · over background image/gradient
a SHOP
2.12:1
#000000
on
#434343
needs 4.5:1 (normal text)
16px · above the fold
a Holiday Gifting
2.45:1
#000000
on
#4D4C4B
needs 4.5:1 (normal text)
16px · above the fold
a Home & Gifts
2.64:1
#000000
on
#515150
needs 4.5:1 (normal text)
16px · above the fold
a Body & Skincare
2.65:1
#000000
on
#525150
needs 4.5:1 (normal text)
16px · above the fold
a Bath & Shower
2.61:1
#000000
on
#515050
needs 4.5:1 (normal text)
16px · above the fold
a Scents & Sprays
2.63:1
#000000
on
#505150
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)
ElementRatioRequiredFGBGResult
h1 Live Lavender Plants…5.24:13.0:1
#000000
#7F7F7F
Pass
h1 Lavender Citrus Hand…5.24:13.0:1
#000000
#7F7F7F
Pass
h2 Fennario Meadows5.24:13.0:1
#000000
#7F7F7F
Pass
h2 Favourites5.24:13.0:1
#000000
#7F7F7F
Pass
h2 Learn Lavender5.24:13.0:1
#000000
#7F7F7F
Pass
h2 Instagram5.24:13.0:1
#000000
#7F7F7F
Pass
h2 Policies5.24:13.0:1
#000000
#7F7F7F
Pass
h2 Jobs/Our Farm5.24:13.0:1
#000000
#7F7F7F
Pass
h2 Elora Boutique Hours5.24:13.0:1
#000000
#7F7F7F
Pass
h2 Currency5.24:13.0:1
#000000
#7F7F7F
Pass
title Terre Bleu1.30:14.5:1
#000000
#12203F
Fail
a Skip to content1.30:14.5:1
#000000
#12203F
Fail
span Our Farm Is Currentl…1.30:14.5:1
#000000
#12203F
Fail
span Close menu1.59:14.5:1
#000000
#2A303C
Fail
a SHOP2.12:14.5:1
#000000
#434343
Fail
a Holiday Gifting2.45:14.5:1
#000000
#4D4C4B
Fail
a Home & Gifts2.64:14.5:1
#000000
#515150
Fail
a Body & Skincare2.65:14.5:1
#000000
#525150
Fail
a Bath & Shower2.61:14.5:1
#000000
#515050
Fail
a Scents & Sprays2.63:14.5:1
#000000
#505150
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 81/100 — 6 failing, 28 passed
REVIEW
81

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.

ARIA

Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid values. Learn more about valid values for ARIA attributes.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Cart div.header-item > div.site-nav > div.site-nav__icons > a.site-nav__link

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

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
div > div.product__photos > div.product__thumbs > button.product__thumb-arrow div > div.product__photos > div.product__thumbs > button.product__thumb-arrow
div > div.product__photos > div.product__thumbs > button.product__thumb-arrow div > div.product__photos > div.product__thumbs > button.product__thumb-arrow

Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
body.template-index > div.emotive-popup-root > iframe#emotive-back-in-stock-popup body.template-index > div.emotive-popup-root > iframe#emotive-back-in-stock-popup

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.header-layout > div.header-item > h1#LogoContainer > a.site-header__logo-link div.header-layout > div.header-item > h1#LogoContainer > a.site-header__logo-link
div > div > div.hero > a.hero__slide-link div > div > div.hero > a.hero__slide-link
div.site-footer__bottom > div.footer__copyright > span.footer__powered_by > a.js-no-transition div.site-footer__bottom > div.footer__copyright > span.footer__powered_by > a.js-no-transition

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
Pick Up Only. Please see below for pickup information. While quantities last. p > span > span > b
 Not available to be shipped at this time. p > span > span > b

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
Please note that the farm is not currently open to visitors. div.animation-contents > div.background-media-text__text > div.rte > h6

These are opportunities to improve keyboard navigation in your application.

○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 are valid and not misspelled
●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
●Elements with the `role=text` attribute do not have focusable descendents.
●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.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●ARIA IDs are unique
●Uses ARIA roles only on compatible elements
●Image elements do not have `[alt]` attributes that are redundant text.
●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
○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
○No form fields have multiple labels
○`<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.
○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
6 landmarks
PASS
6 landmarks
Info::
<main> landmark present
Info::
2 <nav> landmark(s) found
Info::
All <nav> elements are properly labeled
Info::
Skip navigation link present
Page Structure — as a screen reader sees it
BANNER header NAV "Primary" MAIN CONTENTINFO footer
A
Alt Text Quality
2 of 75 images have issues
PASS
2 of 75 images have issues
Critical::
1 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Warning::
1 image(s) with generic alt text
Info::
32 decorative image(s) correctly marked
Info::
41 image(s) with good alt text
75 images 41 good alt text 32 decorative 1 generic 1 missing
IssueCount
missing1 image(s)
generic1 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

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

Send Feedback