Accessibility
· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.FFavicon & BrandingAction1 icon(s) detectedFIX
DWeb ManifestActionNot foundFIX
No web manifest found.
DDark Mode SupportActionTheme color onlyFIX
Detection limited to meta tags and inline styles.
DPrint StylesheetActionNo print stylesFIX
CHeading HierarchyAction30 headings, 2 skip(s)REVIEW
- 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.
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.
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.
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
BForm Accessibility6 of 7 controls have issuesREVIEW
| Control | Type | Label | Method |
|---|---|---|---|
| #cmdk-input | search | Search | for/id |
| contact[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_PRA74n | (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">
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
BLink & Button Quality1 issue(s) across 70 links and 13 buttonsREVIEW
| Element | Text | Issue | Suggested Fix |
|---|---|---|---|
| / | (empty) | empty | Add link text or aria-label |
| https://www.facebook.com/Dependable.FE | new tab | Add '(opens in new tab)' to text | |
| https://www.instagram.com/dependable.fir… | new tab | Add '(opens in new tab)' to text | |
| https://www.linkedin.com/company/dependa… | new tab | Add '(opens in new tab)' to text | |
| https://x.com/dependable_ev | new tab | Add '(opens in new tab)' to text |
Links without text are announced as raw URLs by screen readers.
/
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
Add '(opens in new tab)' to link text or aria-label.
https://www.facebook.com/Dependable.FE; https://www.instagram.com/dependable.fire.equipment/; https://www.linkedin.com/company/dependable-fire-equipment/posts/?feedView=all; https://x.com/dependable_ev
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
BIframe Accessibility2/2 iframe(s) missing title; 0 placeholder(s)REVIEW
BTap Target Adequacy2 tap target(s) too small or too close togetherREVIEW
C404 Error PageActionHTTP 404, custom pageREVIEW
CColor Contrast (Screenshot)Action20 text elements analyzed, 1 fail WCAG AAREVIEW
Analyzes text contrast against the actual rendered page, including background images, gradients, and overlays that CSS-based tools cannot detect.
Show all checked elements (20)
| Element | Ratio | Required | FG | BG | Result |
|---|---|---|---|---|---|
| h1 Dependable Fire Equi… | 7.03:1 | 3.0:1 | #000000 | #90969C | Pass |
| h1 Dependable Fire Equi… | 1.00:1 | 3.0:1 | #FFFFFF | #FFFFFF | Fail |
| h2 Your cart is empty | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h2 We carry leading bra… | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h2 All Categories | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h2 Brands & Manufacture… | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h2 Apparatus Parts | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h2 Contact Us | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h2 Search | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h3 Industry - Leading B… | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h3 Proudly Canadian | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h3 Quality Equipment | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h3 Fast & Reliable Supp… | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h3 Industry - Leading B… | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h3 Proudly Canadian | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h3 Quality Equipment | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h3 Fast & Reliable Supp… | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h3 Industry - Leading B… | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h3 Proudly Canadian | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h3 Contact Info | 21.00:1 | 3.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.
BLighthouse Accessibility AuditsScore 86/100 — 5 failing, 26 passedREVIEW
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.
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.
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.
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.
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.
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 |
A+Landmark Structure7 landmarksPASS
A+Heading Text QualityAll 30 heading(s) have substantive, well-formed textPASS
AAlt Text Quality2 of 82 images have issuesPASS
| Issue | Count |
|---|---|
| missing | 1 image(s) |
| generic | 1 image(s) |
Images without alt text are invisible to screen readers.
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