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

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
71
GRADE
C
FIX
7
REVIEW
7
PASS
10
INFO
0
Checks
24
10 PASS 7 REVIEW 7 FIX
D
Form Accessibility
Action
4 of 5 controls have issues
FIX
4 of 5 controls have issues
Critical::
3 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <textarea name="g-recaptcha-response" id="g-recaptcha-response">; <input type="submit">; <input type="submit">
Warning::
1 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="email" name="email" id="email-0d66079a-f8c7-43f6-99f1-5737fdd6443d">
Info::
1 control(s) properly labeled
5 controls
1 labeled
1 placeholder only
3 unlabeled
ControlTypeLabelMethod
#Footer-Newsletter-InputemailNamefor/id
#email-0d66079a-f8c7-43f6-99f1-5737fdd6443demail(Email Address*)placeholder only
inputsubmit(none)none
#g-recaptcha-responsetextarea(none)none
inputsubmit(none)none

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

<textarea name="g-recaptcha-response" id="g-recaptcha-response">; <input type="submit">; <input type="submit">

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

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

<input type="email" name="email" id="email-0d66079a-f8c7-43f6-99f1-5737fdd6443d">

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

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::
22 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 22 <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
Landmark Structure
28 landmarks
REVIEW
28 landmarks
Info::
<main> landmark present
Info::
22 <nav> landmark(s) found
Info::
All <nav> elements are properly labeled
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 "w-dropdown-toggle-0" MAIN CONTENTINFO (missing!)

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

C
Mobile Keyboard & Autofill
Action
1/3 eligible field(s) missing autocomplete or inputmode
REVIEW
1/3 eligible field(s) missing autocomplete or inputmode
Warning::
1 field(s) would benefit from inputmode attribute
Mobile browsers pick the on-screen keyboard layout from `inputmode=` when present (numeric pad, tel dialpad, email keyboard). Without it, users see the default text keyboard and must mode-switch -- 2-3 extra taps per phone-number or numeric-ID field. Type-based defaults exist (`type=tel` shows the tel keyboard on most browsers) but `inputmode` is the explicit, cross-browser way to control this. Affected types: email.
Got: <input type="email" name="Email-2" id="Footer-Newsletter-Input">
B
Iframe Accessibility
2/4 iframe(s) missing title; 0 placeholder(s)
REVIEW
2/4 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
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.
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
h1 TRANSFORMERS
1.01:1
#000000
on
#020202
needs 3.0:1 (large text)
32px · bottom of viewport
h1 TRANSFORMERS
1.01:1
#000000
on
#020202
needs 3.0:1 (large text)
32px · bottom of viewport
h2 Largest selection of new and remanufactu…
1.01:1
#000000
on
#020202
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Explore more products
1.01:1
#000000
on
#020202
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Delivered Fast & Hassle-Free
1.01:1
#000000
on
#020202
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Explore more products
1.01:1
#000000
on
#020202
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Get Any Transformer. Hit Every Deadline.
1.01:1
#000000
on
#020202
needs 3.0:1 (large text)
24px · bottom of viewport
h2 American Industry. Proven Performance.
1.01:1
#000000
on
#020202
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Simple Process. Serious Speed.
1.01:1
#000000
on
#020202
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Reliable Transformers. Responsive Suppor…
1.01:1
#000000
on
#020202
needs 3.0:1 (large text)
24px · bottom of viewport
h2 One Call.
1.01:1
#000000
on
#020202
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Total Solution.
1.01:1
#000000
on
#020202
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Transformer Questions. Answered.
1.01:1
#000000
on
#020202
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Get the
1.01:1
#000000
on
#020202
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Quote Today.
1.01:1
#000000
on
#020202
needs 3.0:1 (large text)
24px · bottom of viewport
title Maddox Transformer | Padmount, Substatio…
1.04:1
#000000
on
#070707
needs 4.5:1 (normal text)
16px · top of page (header area)
div Products & Services
1.04:1
#000000
on
#060606
needs 4.5:1 (normal text)
16px · top of page (header area)
div Transformers
1.06:1
#000000
on
#0A0A0A
needs 4.5:1 (normal text)
16px · top of page (header area)
div Padmount Transformers
1.04:1
#000000
on
#060606
needs 4.5:1 (normal text)
16px · top of page (header area)
div 3-Ph Padmount Transformer
1.15:1
#000000
on
#151515
needs 4.5:1 (normal text)
16px · above the fold
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 TRANSFORMERS1.01:13.0:1
#000000
#020202
Fail
h1 TRANSFORMERS1.01:13.0:1
#000000
#020202
Fail
h2 Largest selection of…1.01:13.0:1
#000000
#020202
Fail
h2 Explore more product…1.01:13.0:1
#000000
#020202
Fail
h2 Delivered Fast & Has…1.01:13.0:1
#000000
#020202
Fail
h2 Explore more product…1.01:13.0:1
#000000
#020202
Fail
h2 Get Any Transformer.…1.01:13.0:1
#000000
#020202
Fail
h2 American Industry. P…1.01:13.0:1
#000000
#020202
Fail
h2 Simple Process. Seri…1.01:13.0:1
#000000
#020202
Fail
h2 Reliable Transformer…1.01:13.0:1
#000000
#020202
Fail
h2 One Call.1.01:13.0:1
#000000
#020202
Fail
h2 Total Solution.1.01:13.0:1
#000000
#020202
Fail
h2 Transformer Question…1.01:13.0:1
#000000
#020202
Fail
h2 Get the1.01:13.0:1
#000000
#020202
Fail
h2 Quote Today.1.01:13.0:1
#000000
#020202
Fail
title Maddox Transformer |…1.04:14.5:1
#000000
#070707
Fail
div Products & Services1.04:14.5:1
#000000
#060606
Fail
div Transformers1.06:14.5:1
#000000
#0A0A0A
Fail
div Padmount Transformer…1.04:14.5:1
#000000
#060606
Fail
div 3-Ph Padmount Transf…1.15:14.5:1
#000000
#151515
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 88/100 — 3 failing, 23 passed
REVIEW
88

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

Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more about roles and required children elements.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
AUGUST 20, 2026 Why Do Transformers Fail? PARTS AUGUST 19, 2026 Maddox Name… div.grid-wrapper > div#w-node-_83db6561-3751-0e64-c596-fd895d5af3b1-69673727 > div.main-resources_list-wrapper > div#swiper-wrapper-fff10b2510b621a5e9

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.

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
Products div.main-products_heading-wrap > div.main-products_heading > div.heading-eyebrow_wrap > p.heading-eyebrow
Reviews div.main-products_heading-wrap > div.main-products_heading > div.heading-eyebrow_wrap > p.heading-eyebrow
Get a Quote div.main-reliable_content-wrap > div.button-wrap > a.button-main > div.button-label
Services div.main-products_heading-wrap > div.main-products_heading > div.heading-eyebrow_wrap > p.heading-eyebrow
Learn More div.main-services_block-wrapper > div.main-services_content-wrap > a.button-main > div.button-label
Learn More div.main-services_block-wrapper > div.main-services_content-wrap > a.button-main > div.button-label
Learn More div.main-services_block-wrapper > div.main-services_content-wrap > a.button-main > div.button-label
Learn More div.main-services_block-wrapper > div.main-services_content-wrap > a.button-main > div.button-label
Resources div.main-products_heading-wrap > div.main-products_heading > div.heading-eyebrow_wrap > p.heading-eyebrow
See All Articles div.main-resources_arrow-wrapper > div.main-resources_button-wrap > a.button-secondary > div.button-label
Start Your Quote div.quotes-button-wrapper > div.button-wrap > a.button-main > div.button-label
PRODUCTS & SERVICES div.footer-wrapper > div#w-node-b2b0e51a-e877-2a1f-cd72-6bb0f06b8ef6-f06b8edc > div.footer-column-title > div.caption-2
RESOURCES div.footer-wrapper > div#w-node-b2b0e51a-e877-2a1f-cd72-6bb0f06b8f0a-f06b8edc > div.footer-column-title > div.caption-2
COMPANY div.footer-wrapper > div#w-node-b2b0e51a-e877-2a1f-cd72-6bb0f06b8f20-f06b8edc > div.footer-column-title > div.caption-2
form#hsForm_0d66079a-f8c7-43f6-99f1-5737fdd6443d > div.hs_submit > div.actions > input.hs-button form#hsForm_0d66079a-f8c7-43f6-99f1-5737fdd6443d > div.hs_submit > div.actions > input.hs-button
© 2026  MADDOX INDUSTRIAL TRANSFORMER, LLC. | MADDOX.COM div.side-paddings > div.footer-wrapper > div#w-node-b2b0e51a-e877-2a1f-cd72-6bb0f06b8f3d-f06b8edc > div.caption-2
TERMS OF SERVICE div.side-paddings > div.footer-wrapper > div#w-node-b2b0e51a-e877-2a1f-cd72-6bb0f06b8f3d-f06b8edc > a.caption-link

These are opportunities to improve the legibility of your content.

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.container-1360px > div.nav-wrapper > div.nav-left > a.mobile-phone-button div.container-1360px > div.nav-wrapper > div.nav-left > a.mobile-phone-button
div.container-1360px > div.nav-wrapper > div.nav-left > a.mobile-menu-button div.container-1360px > div.nav-wrapper > div.nav-left > a.mobile-menu-button
div.container-1360px > div.nav-wrapper > div.nav-left > a.mobile-phone-button div.container-1360px > div.nav-wrapper > div.nav-left > a.mobile-phone-button
div.container-1360px > div.nav-wrapper > div.nav-left > a.mobile-menu-button div.container-1360px > div.nav-wrapper > div.nav-left > a.mobile-menu-button

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.

○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
●Input buttons have discernible text.
●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
●Document has a `<title>` element
●`<frame>` or `<iframe>` elements have a title
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●No element has a `[tabindex]` value greater than 0
●Touch targets have sufficient size and spacing.
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Deprecated ARIA roles were not used
●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
○`[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
○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
○`<input type="image">` elements have `[alt]` text
○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
○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.
○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
13 headings
PASS
13 headings
Warning::
Multiple H1 headings (2 found)
A page should have only one H1. Multiple H1s dilute the document outline.
  • H1 TRANSFORMERS
  • H2 Largest selection of new and remanufactured transformers. Delivered fast & hassle-free.
  • H2 Explore more products
  • H2 Delivered Fast & Hassle-Free
  • H1 TRANSFORMERS duplicate H1
  • H2 Explore more products
  • H2 Get Any Transformer. Hit Every Deadline.
  • H2 American Industry. Proven Performance.
  • H2 Simple Process. Serious Speed.
  • H2 Reliable Transformers. Responsive Support.
  • H2 One Call.Total Solution.
  • H2 Transformer Questions. Answered.
  • H2 Get theQuote Today.

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::
2 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: 2 all-caps heading(s)
A+
Alt Text Quality
All 155 images OK
PASS
All 155 images OK
Info::
105 decorative image(s) correctly marked
Info::
50 image(s) with good alt text
155 images 50 good alt text 105 decorative
All images have appropriate alt text.
A+
Form Input Types
5 form control(s) checked, no type mismatches
PASS
5 form control(s) checked, no type mismatches
Info::
No input-type mismatches detected
A+
Form Input Quality
5 form control(s) checked, no input-semantic issues
PASS
5 form control(s) checked, no input-semantic issues
Info::
All form input semantics look correct
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
0 positive, 2 -1-on-focusable
PASS
0 positive, 2 -1-on-focusable
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
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 459 visible text node(s) render at >= 12 CSS pixels
PASS
All 459 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.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback