Skip to content
https://dependablefireequipment.ca

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
78
GRADE
C
FIX
5
REVIEW
8
PASS
11
INFO
0
Checks
24
11 PASS 8 REVIEW 5 FIX
F
Favicon & Branding
Action
1 icon(s) detected
FIX
1 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::
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'>.
✗ favicon.ico Missing
✓ PNG Icons Present
✗ 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: rgb(255 255 255)
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 ✗
D
Navigation UX
Action
2 navigation pattern(s)
FIX
2 navigation pattern(s)
Info::
Search functionality detected
Got: role-search
Info::
Skip navigation link detected
Info::
2 navigation landmark(s) detected
Breadcrumbs
Search role='search' landmark
Skip Link Skip link detected
Labeled Navigation 2 <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.
C
Heading Hierarchy
Action
30 headings, 2 skip(s)
REVIEW
30 headings, 2 skip(s)
Warning::
Multiple H1 headings (2 found)
A page should have only one H1. Multiple H1s dilute the document outline.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H1 Dependable Fire Equipment
  • H2 Your cart is empty
  • H2 Your cart is empty
  • H1 Dependable Fire Equipment Trusted. Proven. Ready duplicate H1
  • H2 We carry leading brands from the industry's most trusted suppliers,
  • H3 Industry - Leading Brands
  • H3 Proudly Canadian
  • H3 Quality Equipment
  • H3 Fast & Reliable Support
  • H3 Industry - Leading Brands
  • H3 Proudly Canadian
  • H3 Quality Equipment
  • H3 Fast & Reliable Support
  • H3 Industry - Leading Brands
  • H3 Proudly Canadian
  • H2 All Categories
  • H4 Find the Right Equipment for Your Team skipped
  • H5 Browse more equipment and accessories, or contact our team for help choosing.
  • H2 Brands & Manufacturers
  • H2 Apparatus Parts
  • H2 Contact Us
  • H3 Contact Info
  • H3 Address
  • H3 Subscribe To Our Newsletter
  • H3 Quick Links
  • H3 Rescue & Response
  • H3 Fire Suppression
  • H3 Dependable Group
  • H2 Search
  • H4 Products skipped

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
6 of 7 controls have issues
REVIEW
6 of 7 controls have issues
Warning::
6 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" name="contact[name]">; <input type="email" name="contact[email]">; <input type="text" name="contact[date]">; <input type="tel" name="contact[phone]">; <textarea name="contact[body]">; <input type="email" name="contact[email]" id="FooterEmail-sections--20101491884230__custom_footer_PRA74n">
Info::
1 control(s) properly labeled
7 controls
1 labeled
6 placeholder only
0 unlabeled
ControlTypeLabelMethod
#cmdk-inputsearchSearchfor/id
contact[email]email(Email address)placeholder only
contact[date]text(Date)placeholder only
contact[phone]tel(Phone number)placeholder only
contact[body]textarea(Your message)placeholder only
#FooterEmail-sections--20101491884230__custom_footer_PRA74nemail(Email)placeholder only
contact[name]text(Name)placeholder only

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

<input type="text" name="contact[name]">; <input type="email" name="contact[email]">; <input type="text" name="contact[date]">; <input type="tel" name="contact[phone]">; <textarea name="contact[body]">; <input type="email" name="contact[email]" id="FooterEmail-sections--20101491884230__custom_footer_PRA74n">

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

B
Iframe Accessibility
2/2 iframe(s) missing title; 0 placeholder(s)
REVIEW
2/2 iframe(s) missing title; 0 placeholder(s)
Warning::
<iframe> missing title attribute (src="")
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.
Warning::
<iframe> missing title attribute (src="")
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.
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
Info::
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
404 Error Page
Action
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title 404 Not Found – Dependable Fire Equipment ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 1 fail WCAG AA
REVIEW

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

19 pass 1 fail WCAG AA
h1 Dependable Fire Equipment Trusted. Prove…
1.00:1
#FFFFFF
on
#FFFFFF
needs 3.0:1 (large text)
32px · bottom of viewport
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Dependable Fire Equi…7.03:13.0:1
#000000
#90969C
Pass
h1 Dependable Fire Equi…1.00:13.0:1
#FFFFFF
#FFFFFF
Fail
h2 Your cart is empty21.00:13.0:1
#000000
#FFFFFF
Pass
h2 We carry leading bra…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 All Categories21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Brands & Manufacture…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Apparatus Parts21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Contact Us21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Search21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Industry - Leading B…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Proudly Canadian21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Quality Equipment21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Fast & Reliable Supp…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Industry - Leading B…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Proudly Canadian21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Quality Equipment21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Fast & Reliable Supp…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Industry - Leading B…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Proudly Canadian21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Contact Info21.00:13.0: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.

B
Lighthouse Accessibility Audits
Score 86/100 — 5 failing, 26 passed
REVIEW
86

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.

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
Find the Right Equipment for Your Team div.border-style > div.spacing-style > rte-formatter.spacing-style > h4

These are opportunities to improve keyboard navigation in your application.

Names and labels

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.custom-banner > div.banner-video > video > img div.custom-banner > div.banner-video > video > img

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.custom-footer__inner > div.custom-footer__grid > div.custom-footer__brand > a.custom-footer__logo-link div.custom-footer__inner > div.custom-footer__grid > div.custom-footer__brand > a.custom-footer__logo-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.

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
(905) 451-6878 div.custom-footer__inner > div.custom-footer__grid > div.custom-footer__contact > a.custom-footer__text-link
fireequipment@dependable.ca div.custom-footer__inner > div.custom-footer__grid > div.custom-footer__contact > a.custom-footer__text-link

These items highlight common accessibility best practices.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Nozzles section#all-categories-template--20101491392710__new_style_collection_4ciMPn > div.container > div.all-categories-grid > a.all-category-card
Hose section#all-categories-template--20101491392710__new_style_collection_4ciMPn > div.container > div.all-categories-grid > a.all-category-card
Foam section#all-categories-template--20101491392710__new_style_collection_4ciMPn > div.container > div.all-categories-grid > a.all-category-card
Ladders section#all-categories-template--20101491392710__new_style_collection_4ciMPn > div.container > div.all-categories-grid > a.all-category-card
Rescue Equipment section#all-categories-template--20101491392710__new_style_collection_4ciMPn > div.container > div.all-categories-grid > a.all-category-card
PPE section#all-categories-template--20101491392710__new_style_collection_4ciMPn > div.container > div.all-categories-grid > a.all-category-card
Portable Water Tanks section#all-categories-template--20101491392710__new_style_collection_4ciMPn > div.container > div.all-categories-grid > a.all-category-card
Lighting section#all-categories-template--20101491392710__new_style_collection_4ciMPn > div.container > div.all-categories-grid > a.all-category-card
Super Vac section#all-categories-template--20101491392710__new_style_collection_4ciMPn > div.container > div.all-categories-grid > a.all-category-card
Lights & Sirens section#all-categories-template--20101491392710__new_style_collection_niF7VC > div.container > div.all-categories-grid > a.all-category-card
Monitors section#all-categories-template--20101491392710__new_style_collection_niF7VC > div.container > div.all-categories-grid > a.all-category-card
Tool Mounts section#all-categories-template--20101491392710__new_style_collection_niF7VC > div.container > div.all-categories-grid > a.all-category-card
○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
●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.
●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.
●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"]`
●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
○`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
○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>`.
○All heading elements contain content.
○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
7 landmarks
PASS
7 landmarks
Info::
<main> landmark present
Info::
2 <nav> landmark(s) found
Info::
All <nav> elements are properly labeled
Info::
Skip navigation link present
Info::
Search landmark present
Page Structure — as a screen reader sees it
BANNER header NAV "Primary" SEARCH MAIN CONTENTINFO footer
A+
Heading Text Quality
All 30 heading(s) have substantive, well-formed text
PASS
All 30 heading(s) have substantive, well-formed text
Info::
Heading text quality is clean -- no placeholder, length, or styling issues
A
Alt Text Quality
2 of 82 images have issues
PASS
2 of 82 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::
15 decorative image(s) correctly marked
Info::
65 image(s) with good alt text
82 images 65 good alt text 15 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

A+
Form Input Types
7 form control(s) checked, no type mismatches
PASS
7 form control(s) checked, no type mismatches
Info::
No input-type mismatches detected
A+
Form Input Quality
7 form control(s) checked, no input-semantic issues
PASS
7 form control(s) checked, no input-semantic issues
Info::
All form input semantics look correct
A+
Mobile Keyboard & Autofill
No autofill-eligible form controls
PASS
No autofill-eligible form controls
Info::
No autofill-eligible form controls (no name/email/tel/address fields)
A+
Document Language
Lang attribute set to "en"
PASS
Lang attribute set to "en"
Info::
<html lang="en"> is set and valid
Got: en
A+
Tabindex Anti-Patterns
10 explicit tabindex attribute(s) checked, no anti-patterns
PASS
10 explicit tabindex attribute(s) checked, no anti-patterns
Info::
No tabindex anti-patterns detected
A+
Mobile-Readable Font Sizes
All 48 visible text node(s) render at >= 12 CSS pixels
PASS
All 48 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