Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

11 PASS 7 REVIEW 6 FIX

404 Error Page

Action

HTTP 404, custom page

FIX

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗

Favicon & Branding

Action

1 icon(s) detected

FIX

1 icon(s) detected

favicon.ico present at site root

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 Present

✗ PNG Icons Missing

✗ Apple Touch Missing

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

Web Manifest

Action

Not found

FIX

Not found

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.

Dark Mode Support

Action

No dark mode signals

FIX

No dark mode signals

No dark mode signals detected

Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.

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.

Print Stylesheet

Action

No print styles

FIX

No print styles

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 ✗

Navigation UX

Action

No navigation patterns

FIX

No navigation patterns

3 navigation landmark(s) detected

Hamburger menu detected (responsive design)

No breadcrumbs, search, or skip link detected

These navigation aids help users orient themselves and find content efficiently, especially on large sites.

Breadcrumbs

Skip Link

Labeled Navigation 3 <nav> element(s)

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.

Landmark Structure

7 landmarks

REVIEW

7 landmarks

<main> landmark present

3 <nav> landmark(s) found

1 of 3 <nav> elements are unlabeled

Multiple navigations need aria-label to distinguish them for screen readers.

No contentinfo (footer) landmark

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

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

Alt Text Quality

1 of 10 images have issues

REVIEW

1 of 10 images have issues

1 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

1 image-in-link without alt text

An image inside a link with no alt creates an empty link.

1 decorative image(s) correctly marked

8 image(s) with good alt text

10 images 8 good alt text 1 decorative 1 missing

Issue	Count
missing	1 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

An image inside a link with no alt creates an empty link.

Why this matters

Image-only links with no alt create empty links — screen-reader users hear 'link' with no destination context.

Learn more ▾

An <a><img></a> with no img alt is the worst-case for accessibility: AT announces the link but can't describe where it goes. Either add alt to the image OR add aria-label to the link.

Source: WCAG 2.1 SC 2.4.4

Link & Button Quality

Action

3 issue(s) across 43 links and 24 buttons

REVIEW

3 issue(s) across 43 links and 24 buttons

3 link(s) with no accessible text

Links without text are announced as raw URLs by screen readers.

Got: https://anticimexonline.sharepoint.com/sites/AxSmartNet/SitePages/WarrantyAnd…; https://anticimexonline.sharepoint.com/sites/AxSmartNet/SitePages/Update-on-l…; https://anticimexonline.sharepoint.com/sites/AxSmartNet/SitePages/SmartProduc…

16 link(s) open in new tab without warning

Add '(opens in new tab)' to link text or aria-label.

Got: https://business.safety.google/privacy/; https://cookieinformation.com/cookie-and-privacy-policy/; https://cookieinformation.com/; https://tools.google.com/dlpage/gaoptout; https://support.google.com/chrome/answer/95647?hl=en; https://support.apple.com/en-us/HT201265; https://support.microsoft.com/en-us/help/4027947/microsoft-edge-delete-cookies; https://support.mozilla.org/en-US/kb/delete-cookies-remove-info-websites-stored; https://www.samsung.com/uk/support/mobile-devices/using-the-samsung-internet-…; https://help.opera.com/en/latest/web-preferences/#cookies (+6 more)

24 link(s) with descriptive text

43 links

3 empty

0 generic text

16 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://business.safety.google/privacy/	Google privacy policy …	new tab	Add '(opens in new tab)' to text
https://cookieinformation.com/cookie-and…	Cookie Information - Privacy …	new tab	Add '(opens in new tab)' to text
https://cookieinformation.com/	Cookie Information …	new tab	Add '(opens in new tab)' to text
https://tools.google.com/dlpage/gaoptout	You can opt-out of cookies fro…	new tab	Add '(opens in new tab)' to text
https://support.google.com/chrome/answer…	Google Chromeopens in new tab	new tab	Add '(opens in new tab)' to text
https://support.apple.com/en-us/HT201265	Safariopens in new tab	new tab	Add '(opens in new tab)' to text
https://support.microsoft.com/en-us/help…	Microsoft Edgeopens in new tab	new tab	Add '(opens in new tab)' to text
https://support.mozilla.org/en-US/kb/del…	Mozilla Firefoxopens in new ta…	new tab	Add '(opens in new tab)' to text
https://www.samsung.com/uk/support/mobil…	Samsung Internetopens in new t…	new tab	Add '(opens in new tab)' to text
https://help.opera.com/en/latest/web-pre…	Operaopens in new tab	new tab	Add '(opens in new tab)' to text
https://timeread.hubpages.com/hub/How-to…	Androidopens in new tab	new tab	Add '(opens in new tab)' to text
https://cookieinformation.com/	Cookie Information opens in ne…	new tab	Add '(opens in new tab)' to text
https://cookieinformation.com/	Cookie Information …	new tab	Add '(opens in new tab)' to text
/	Anticimex	img no alt	Add alt attribute to the image
https://anticimexonline.sharepoint.com/s…	(empty)	empty	Add link text or aria-label
https://anticimexonline.sharepoint.com/s…	Warranty & Claims	new tab	Add '(opens in new tab)' to text
https://anticimexonline.sharepoint.com/s…	(empty)	empty	Add link text or aria-label
https://anticimexonline.sharepoint.com/s…	Leadtime	new tab	Add '(opens in new tab)' to text
https://anticimexonline.sharepoint.com/s…	(empty)	empty	Add link text or aria-label
https://anticimexonline.sharepoint.com/s…	Smart Products	new tab	Add '(opens in new tab)' to text

48 links and buttons have descriptive text

Links without text are announced as raw URLs by screen readers.

https://anticimexonline.sharepoint.com/sites/AxSmartNet/SitePages/WarrantyAnd…; https://anticimexonline.sharepoint.com/sites/AxSmartNet/SitePages/Update-on-l…; https://anticimexonline.sharepoint.com/sites/AxSmartNet/SitePages/SmartProduc…

Why this matters

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://business.safety.google/privacy/; https://cookieinformation.com/cookie-and-privacy-policy/; https://cookieinformation.com/; https://tools.google.com/dlpage/gaoptout; https://support.google.com/chrome/answer/95647?hl=en; https://support.apple.com/en-us/HT201265; https://support.microsoft.com/en-us/help/4027947/microsoft-edge-delete-cookies; https://support.mozilla.org/en-US/kb/delete-cookies-remove-info-websites-stored; https://www.samsung.com/uk/support/mobile-devices/using-the-samsung-internet-…; https://help.opera.com/en/latest/web-preferences/#cookies (+6 more)

Why this matters

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

Tabindex Anti-Patterns

0 positive, 4 -1-on-focusable

REVIEW

0 positive, 4 -1-on-focusable

tabindex="-1" on naturally-focusable <button>

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.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" on naturally-focusable <button id="updateButton">

tabindex="-1" on naturally-focusable <input id="cookie_cat_necessary">

Mobile-Readable Font Sizes

93% of visible text renders at >= 12 CSS px (3 below threshold)

REVIEW

93% of visible text renders at >= 12 CSS px (3 below threshold)

3 text node(s) render below 12 CSS pixels on mobile

Mobile browsers default the root font-size to 16 px; text below ~ 12 px (75% of root) is hard to read without zooming. WCAG 1.4.4 (Resize Text) requires the page to support 200% zoom without loss of functionality -- which most layouts handle, but small base text still costs readability and conversion. Audit which selectors set sizes below 12 px (often footers, fine print, table cells) and bump them to 14-16 px or use rem units that scale with user preferences. Examples: <span> 10.0px ("Powered by:"); <a> 10.0px ("Cookie Information"); <span> 10.0px ("opens in new tab").

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

h2 You control your data

2.45:1

#000000

#4C4C4C

needs 3.0:1 (large text)

24px · top of page (header area)

h2 Cookie policy

2.45:1

#000000

#4C4C4C

needs 3.0:1 (large text)

24px · bottom of viewport

h2 What is a cookie?

2.45:1

#000000

#4C4C4C

needs 3.0:1 (large text)

24px · bottom of viewport

h2 How our website uses cookies

2.45:1

#000000

#4C4C4C

needs 3.0:1 (large text)

24px · bottom of viewport

h2 How long are cookies stored?

2.45:1

#000000

#4C4C4C

needs 3.0:1 (large text)

24px · bottom of viewport

h2 How to block or delete cookies

2.45:1

#000000

#4C4C4C

needs 3.0:1 (large text)

24px · bottom of viewport

h2 How can you delete cookies?

2.45:1

#000000

#4C4C4C

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Changing your consent

2.45:1

#000000

#4C4C4C

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Do you have any questions?

2.45:1

#000000

#4C4C4C

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Warranty & Claims

2.45:1

#000000

#4C4C4C

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Leadtime

2.45:1

#000000

#4C4C4C

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Smart Products

2.45:1

#000000

#4C4C4C

needs 3.0:1 (large text)

24px · bottom of viewport

title Home

1.35:1

#000000

#072543

needs 4.5:1 (normal text)

16px · top of page (header area)

div We and our business partners use technol…

2.45:1

#000000

#4C4C4C

needs 4.5:1 (normal text)

16px · top of page (header area)

div By clicking ‘Accept’, you give your …

1.30:1

#000000

#06213F

needs 4.5:1 (normal text)

16px · top of page (header area)

div You can withdraw your consent anytime by…

1.30:1

#000000

#06213F

needs 4.5:1 (normal text)

16px · above the fold

div You can read more about how we use cooki…

1.30:1

#000000

#06213F

needs 4.5:1 (normal text)

16px · above the fold

button Read more about cookies

1.63:1

#000000

#243343

needs 4.5:1 (normal text)

16px · above the fold · over background image/gradient

a Google privacy policy

1.92:1

#000000

#373D46

needs 4.5:1 (normal text)

16px · above the fold

span opens in new tab

1.89:1

#000000

#363C46

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)

Element	Ratio	Required	FG	BG	Result
h2 You control your dat…	2.45:1	3.0:1	#000000	#4C4C4C	Fail
h2 Cookie policy	2.45:1	3.0:1	#000000	#4C4C4C	Fail
h2 What is a cookie?	2.45:1	3.0:1	#000000	#4C4C4C	Fail
h2 How our website uses…	2.45:1	3.0:1	#000000	#4C4C4C	Fail
h2 How long are cookies…	2.45:1	3.0:1	#000000	#4C4C4C	Fail
h2 How to block or dele…	2.45:1	3.0:1	#000000	#4C4C4C	Fail
h2 How can you delete c…	2.45:1	3.0:1	#000000	#4C4C4C	Fail
h2 Changing your consen…	2.45:1	3.0:1	#000000	#4C4C4C	Fail
h2 Do you have any ques…	2.45:1	3.0:1	#000000	#4C4C4C	Fail
h2 Warranty & Claims	2.45:1	3.0:1	#000000	#4C4C4C	Fail
h2 Leadtime	2.45:1	3.0:1	#000000	#4C4C4C	Fail
h2 Smart Products	2.45:1	3.0:1	#000000	#4C4C4C	Fail
title Home	1.35:1	4.5:1	#000000	#072543	Fail
div We and our business …	2.45:1	4.5:1	#000000	#4C4C4C	Fail
div By clicking ‘Accep…	1.30:1	4.5:1	#000000	#06213F	Fail
div You can withdraw you…	1.30:1	4.5:1	#000000	#06213F	Fail
div You can read more ab…	1.30:1	4.5:1	#000000	#06213F	Fail
button Read more about cook…	1.63:1	4.5:1	#000000	#243343	Fail
a Google privacy polic…	1.92:1	4.5:1	#000000	#373D46	Fail
span opens in new tab	1.89:1	4.5:1	#000000	#363C46	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.

Lighthouse Accessibility Audits

Score 83/100 — 4 failing, 23 passed

REVIEW

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.

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
Anticimex - Ordering portal `div.container > div.flex > div.flex > span`
HOME `div.text-left > div.mt-4 > a.router-link-active > button.!rounded-full`

These are opportunities to improve the legibility of your content.

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.flex > div.flex > a.router-link-active > img.w-full `div.flex > div.flex > a.router-link-active > img.w-full`

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.grid > article.flex > div.h-[150px] > a.full-link `div.grid > article.flex > div.h-[150px] > a.full-link`
div.grid > article.flex > div.h-[150px] > a.full-link `div.grid > article.flex > div.h-[150px] > a.full-link`
div.grid > article.flex > div.h-[150px] > a.full-link `div.grid > article.flex > div.h-[150px] > a.full-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

Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
head > meta `head > meta`

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

●`[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

●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

●Document has a `<title>` element

●`<html>` element has a `[lang]` attribute

●`<html>` element has a valid value for its `[lang]` attribute

●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.

●`[lang]` attributes have a valid value

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

○`[accesskey]` values are unique

○`button`, `link`, and `menuitem` elements 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

○Links are distinguishable without relying on color.

○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.

○`<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.

A+

Heading Hierarchy

14 headings

PASS

14 headings

Single H1 present

H2 You control your data
H2 Cookie policy
H2 What is a cookie?
H2 How our website uses cookies
H2 How long are cookies stored?
H2 How to block or delete cookies
H2 How can you delete cookies?
H2 Changing your consent
H2 Do you have any questions?
H1 Pest Control and Pest Management
H2 Warranty & Claims
H2 Leadtime
H2 Smart Products
H2 What can you do on the order portal?

A+

Heading Text Quality

All 14 heading(s) have substantive, well-formed text

PASS

All 14 heading(s) have substantive, well-formed text

Heading text quality is clean -- no placeholder, length, or styling issues

Form Accessibility

1 of 1 controls have issues

PASS

1 of 1 controls have issues

1 control(s) rely on placeholder only

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

Got: <input type="text">

1 controls

0 labeled

1 placeholder only

0 unlabeled

Control	Type	Label	Method
input	text	(What are you searching?)	placeholder only

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

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

A+

Form Input Types

1 form control(s) checked, no type mismatches

PASS

1 form control(s) checked, no type mismatches

No input-type mismatches detected

A+

Form Input Quality

1 form control(s) checked, no input-semantic issues

PASS

1 form control(s) checked, no input-semantic issues

All form input semantics look correct

A+

Mobile Keyboard & Autofill

No autofill-eligible form controls

PASS

No autofill-eligible form controls

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"

<html lang="en"> is set and valid

Got: en

A+

Iframe Accessibility

All 1 iframe(s) have descriptive titles

PASS

All 1 iframe(s) have descriptive titles

All 1 iframe(s) have title attributes

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

All tap targets meet WCAG 2.5.5 (44x44px) sizing

A+

PWA Depth

No PWA depth issues detected

PASS

No PWA depth issues detected

A+

Mobile UX Depth

1 mobile-depth signal(s) detected

PASS

1 mobile-depth signal(s) detected

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.