Skip to content
https://www.hightolowvoltage.com

Accessibility

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

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

F
Document Language
Action
Missing <html lang> attribute (WCAG 3.1.1)
FIX
Missing <html lang> attribute (WCAG 3.1.1)
Critical::
Missing <html lang> attribute (WCAG 3.1.1)
Without `<html lang="...">`, screen readers default to the user's system language even when reading content in a different one -- words get pronounced wrong (English text read with French phonetics, etc.). Add a BCP-47 language tag to the <html> root element.
F
Favicon & Branding
Action
2 icon(s) detected
FIX
2 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
✗ favicon.ico Missing
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
F
Web Manifest
Action
Valid manifest
FIX
Valid manifest
Warning::
No name or short_name
Add a name field to identify the app.
Warning::
No 192x192 icon
A 192px icon is required for PWA installation.
PWA Install Criteria Not Installable
Name ✗192×192 icon ✗512×512 icon ✗Start URL ✗Display Mode ✗
D
Dark Mode Support
Action
No dark mode signals
FIX
No dark mode signals
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 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
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::
4 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 4 <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.
B
404 Error Page
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
Info::
Navigation links present on 404 page
Info::
Homepage link present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Not Found ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
B
PWA Depth
3 PWA signal(s) surfaced
REVIEW
3 PWA signal(s) surfaced
Warning::
Manifest is missing `display` -- defaults to browser, no PWA UX
When `display` is `browser` (or unset, which is the spec default), the installed app opens in a regular browser tab -- no install prompt, no standalone window, no app-shell experience. The intended values for a PWA are `standalone` (most common; full-screen, no browser chrome) or `fullscreen` (games / immersive apps). `minimal-ui` is a middle ground (basic browser controls but no address bar).
Info::
Manifest has no maskable icon
Android 12+ Adaptive Icons crop non-maskable icons to a circle or squircle -- frequently hiding important parts of the logo. Add at least one icon entry with `"purpose": "maskable"` (or `"any maskable"`) and a maskable-aware design (16% safe-zone padding around the inner mark).
Info::
Manifest is missing `theme_color`
Without `theme_color`, the install prompt and Android status bar fall back to a generic tint instead of your brand color. Add a hex color (e.g. `"theme_color": "#0066cc"`); for richer support, mirror it via `<meta name="theme-color" content="#0066cc">` so non-installed browsers also pick it up.
A
Heading Hierarchy
29 headings
PASS
29 headings
Warning::
Multiple H1 headings (2 found)
A page should have only one H1. Multiple H1s dilute the document outline.
  • H1 Your Full-Service Electrical Transformer & Solutions Supplier
  • H1 High to Low Voltage is your One-Stop-Shop Transformer Company duplicate H1
  • H2 Sales. Repair. Rentals.
  • H2 All In One Sales and Services
  • H2 3 Simple Steps
  • H3 Source Your Solution
  • H3 Quick Quotes
  • H3 Solution Review
  • H3 Your Issue Solved
  • H2 INDUSTRIES WE SUPPORT
  • H2 Testimonials
  • H2 All In One Sales and Services
  • H2 Sales
  • H3 Stocked, Sourced, and Ready to Ship
  • H2 Repair
  • H3 Recondition, Rebuild, Rapid Response
  • H2 Rental
  • H3 Quick-Ship Power When You Need It
  • H2 Let's Get Started
  • H2 Transformer and Switchgear Lineup
  • H3 Reliable, Quick-Ship Electrical Solutions
  • H4 Padmount Transformers
  • H4 Substation Transformers
  • H4 Dry Type Transformers
  • H4 Switchgear
  • H4 Pole Mount Transformers
  • H4 Cable
  • H2 Buy a Dry Type
  • H2 Have you tested your transformer oil to assess its health?

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

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 30 images OK
PASS
All 30 images OK
Info::
20 decorative image(s) correctly marked
Info::
10 image(s) with good alt text
30 images 10 good alt text 20 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+
Tabindex Anti-Patterns
21 explicit tabindex attribute(s) checked, no anti-patterns
PASS
21 explicit tabindex attribute(s) checked, no anti-patterns
Info::
No tabindex anti-patterns detected
A
Iframe Accessibility
1/1 iframe(s) missing title; 0 placeholder(s)
PASS
1/1 iframe(s) missing title; 0 placeholder(s)
Warning::
<iframe> missing title attribute (src="https://js.stripe.com/v3/m-outer-3437aaddcdf6922d623e172c2d6f9278.html#url=http…")
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.
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 143 visible text node(s) render at >= 12 CSS pixels
PASS
All 143 visible text node(s) render at >= 12 CSS pixels
Info::
All text uses legible mobile font sizes (>= 12 CSS px)
A+
Mobile UX Depth
1 mobile-depth signal(s) detected
PASS
1 mobile-depth signal(s) detected
Info::
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.
A+
Color Contrast (Screenshot)
20 text elements analyzed, 0 fail WCAG AA
PASS

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

20 pass
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Electrical Transform…21.00:13.0:1
#000000
#FFFFFF
Pass
h1 High to Low Voltage …21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Sales. Repair. Renta…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 All In One Sales and…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 3 Simple Steps21.00:13.0:1
#000000
#FFFFFF
Pass
h2 INDUSTRIES WE SUPPOR…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Testimonials21.00:13.0:1
#000000
#FFFFFF
Pass
h2 All In One Sales and…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Sales21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Repair21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Rental21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Let's Get Started21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Transformer and Swit…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Buy a Dry Type21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Have you tested your21.00:13.0:1
#000000
#FFFFFF
Pass
h2 to assess its21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Source Your Solution21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Quick Quotes21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Solution Review21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Your Issue Solved21.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.

A
Lighthouse Accessibility Audits
Score 91/100 — 3 failing, 21 passed
PASS
91

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.

Internationalization and localization

If a page doesn't specify a `lang` attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more about the `lang` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html.wf-montserrat-n7-active html.wf-montserrat-n7-active

These are opportunities to improve the interpretation of your content by users in different locales.

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.w-layout-blockcontainer > div#w-node-f205e0aa-8d77-abbe-4daa-683a2e59d960-2e59d95c > div.w-layout-cell > a.link-block div.w-layout-blockcontainer > div#w-node-f205e0aa-8d77-abbe-4daa-683a2e59d960-2e59d95c > div.w-layout-cell > a.link-block
div.w-layout-blockcontainer > div#w-node-f205e0aa-8d77-abbe-4daa-683a2e59d960-2e59d95c > div.w-layout-cell > a.link-block div.w-layout-blockcontainer > div#w-node-f205e0aa-8d77-abbe-4daa-683a2e59d960-2e59d95c > div.w-layout-cell > a.link-block
div.w-layout-blockcontainer > div#w-node-f205e0aa-8d77-abbe-4daa-683a2e59d960-2e59d95c > div.w-layout-cell > a.link-block div.w-layout-blockcontainer > div#w-node-f205e0aa-8d77-abbe-4daa-683a2e59d960-2e59d95c > div.w-layout-cell > a.link-block
div.w-layout-blockcontainer > div#w-node-f205e0aa-8d77-abbe-4daa-683a2e59d960-2e59d95c > div.w-layout-cell > a.link-block div.w-layout-blockcontainer > div#w-node-f205e0aa-8d77-abbe-4daa-683a2e59d960-2e59d95c > div.w-layout-cell > a.link-block
div.w-layout-blockcontainer > div#w-node-f205e0aa-8d77-abbe-4daa-683a2e59d960-2e59d95c > div.w-layout-cell > a.link-block div.w-layout-blockcontainer > div#w-node-f205e0aa-8d77-abbe-4daa-683a2e59d960-2e59d95c > div.w-layout-cell > a.link-block
div.w-layout-blockcontainer > div#w-node-f205e0aa-8d77-abbe-4daa-683a2e59d960-2e59d95c > div.w-layout-cell > a.link-block div.w-layout-blockcontainer > div#w-node-f205e0aa-8d77-abbe-4daa-683a2e59d960-2e59d95c > div.w-layout-cell > a.link-block
div.copyright-site > div.w-layout-hflex > div.text-block-4 > a.yellow div.copyright-site > div.w-layout-hflex > div.text-block-4 > a.yellow

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

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.wf-montserrat-n7-active html.wf-montserrat-n7-active

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
●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
●`[role]` values are valid
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●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.
●`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
●Background and foreground colors have a sufficient contrast ratio
●Document has a `<title>` element
●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 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 a valid value for its `[lang]` attribute
○`<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.
○Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
○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.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback