Skip to content
https://mez.ink

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
51
GRADE
F
FIX
5
REVIEW
5
PASS
3
INFO
0
Checks
13
3 PASS 5 REVIEW 5 FIX
F
404 Error Page
Action
Soft 404 detected
FIX
Soft 404 detected
Critical::
Soft 404: server returns HTTP 200 for non-existent pages
The server returns HTTP 200 for a path that does not exist. Search engines will index these pages, diluting your real content. Configure your server to return a proper 404 status code for missing pages.
Got: Status: 200 for /beavercheck-404-test-c6v73y
404 Page Quality ✗ Soft 404 (HTTP 200)
Status Code: HTTP 200

The server returned HTTP 200 for a non-existent path. Search engines will index this page as real content. Configure your server to return HTTP 404 for missing pages.

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
F
Web Manifest
Action
Invalid JSON
FIX
Invalid JSON
Warning::
Manifest contains invalid JSON
Manifest at https://mez.ink/manifest.json contains invalid JSON. Browsers cannot parse it.
Got: https://mez.ink/manifest.json

Manifest contains invalid JSON.

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::
Hamburger menu detected (responsive design)
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
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.
C
Landmark Structure
Action
1 landmarks
REVIEW
1 landmarks
Info::
<main> landmark present
Warning::
No <nav> landmark found
Info::
No banner (header) landmark
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 (missing!) 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

B
Heading Hierarchy
18 headings, 1 skip(s)
REVIEW
18 headings, 1 skip(s)
Warning::
Multiple H1 headings (15 found)
A page should have only one H1. Multiple H1s dilute the document outline.
Warning::
Heading level skipped: H1 → H3 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H1 Mezink makes running marketing campaigns
  • H1 fast with 10x outcomes duplicate H1
  • H1 Powering top-tier brands across the globe duplicate H1
  • H1 What sets Mezink apart duplicate H1
  • H1 All-in-one solution for seamless growth duplicate H1
  • H1 Everything you need to run your campaigns duplicate H1
  • H1 Powering smarter campaigns with AI duplicate H1
  • H1 Grow your TikTok Shop with KOL-powered campaigns duplicate H1
  • H3 Strategic creator matching skipped
  • H3 Content that sells through storytelling
  • H3 Results that go beyond reach
  • H1 Mezink by the numbers duplicate H1
  • H1 Mezink by the numbers duplicate H1
  • H1 100M+ duplicate H1
  • H1 100+ duplicate H1
  • H1 20+ duplicate H1
  • H1 Meet the next generation marketing leaders duplicate H1
  • H1 We're making marketing easy and fast duplicate H1

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

B
Dark Mode Support
Dark mode detected
REVIEW
Dark mode detected
Info::
prefers-color-scheme CSS detected in inline styles
Info::
Detection limited to meta tags and inline styles
External CSS files may contain prefers-color-scheme rules not visible to this scan.
Dark Mode✓ Dark Mode Supported
color-scheme meta Not set ✗Dark theme-color Not set ✗CSS indicators Detected ✓

Detection limited to meta tags and inline styles.

C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 6 fail WCAG AA
REVIEW

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

14 pass 6 fail WCAG AA
h1 100M+
1.38:1
#000000
on
#292524
needs 3.0:1 (large text)
32px · bottom of viewport
h1 100+
1.38:1
#000000
on
#292524
needs 3.0:1 (large text)
32px · bottom of viewport
h1 20+
1.38:1
#000000
on
#292524
needs 3.0:1 (large text)
32px · bottom of viewport
h3 Strategic creator matching
1.38:1
#000000
on
#292524
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Content that sells through storytelling
1.38:1
#000000
on
#292524
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Results that go beyond reach
1.38:1
#000000
on
#292524
needs 3.0:1 (large text)
19px · bottom of viewport
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Mezink makes running…21.00:13.0:1
#000000
#FFFFFF
Pass
h1 with 10x outcomes21.00:13.0:1
#000000
#FFFFFF
Pass
h1 100M+1.38:13.0:1
#000000
#292524
Fail
h1 100+1.38:13.0:1
#000000
#292524
Fail
h1 20+1.38:13.0:1
#000000
#292524
Fail
h3 Strategic creator ma…1.38:13.0:1
#000000
#292524
Fail
h3 Content that sells t…1.38:13.0:1
#000000
#292524
Fail
h3 Results that go beyo…1.38:13.0:1
#000000
#292524
Fail
title Mezink: AI Agency to…20.70:14.5:1
#000000
#FEFDFE
Pass
div About20.53:14.5:1
#000000
#FDFCFE
Pass
div Industries18.77:14.5:1
#000000
#F2F2F3
Pass
div Products21.00:14.5:1
#000000
#FFFFFF
Pass
div Use Cases20.36:14.5:1
#000000
#FCFBFD
Pass
div Case Studies20.02:14.5:1
#000000
#FAF9FC
Pass
div Resources21.00:14.5:1
#000000
#FFFFFF
Pass
button Sign in21.00:14.5:1
#000000
#FFFFFF
Pass
button Get a demo21.00:14.5:1
#000000
#FFFFFF
Pass
div Powered by ai21.00:14.5:1
#000000
#FFFFFF
Pass
span fast21.00:14.5:1
#000000
#FFFFFF
Pass
p Experience the power…21.00:14.5: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
Alt Text Quality
3 of 344 images have issues
PASS
3 of 344 images have issues
Warning::
3 image(s) with generic alt text
Info::
1 decorative image(s) correctly marked
Info::
340 image(s) with good alt text
344 images 340 good alt text 1 decorative 3 generic
IssueCount
generic3 image(s)
A+
Form Accessibility
No form controls
PASS
No form controls
Info::
No form controls on this page
No form controls found.
A
Lighthouse Accessibility Audits
Score 90/100 — 3 failing, 22 passed
PASS
90

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
OUR GLOBAL PRESENCE div.flex > div.mx-auto > div.flex > p.text-primary
AI-POWERED DISCOVERY ENGINE div.grid > div.flex > div.flex > span.text-xs
AI-POWERED EVALUATION ENGINE div.grid > div.flex > div.flex > span.text-xs
AI CONTENT INTELLIGENCE div.grid > div.flex > div.flex > span.text-xs

These are opportunities to improve the legibility of your content.

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
Strategic creator matching div.flex > div > div.mb-3 > h3.new-ui
Ideas to level-up your marketing game div.container > div.flex > div.flex > h3.text-base

These are opportunities to improve keyboard navigation in your application.

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
Go to slide 1 div.py-[64px] > div.mb-2.5 > div.flex > button.hover:bg-primary/20
Go to slide 2 div.py-[64px] > div.mb-2.5 > div.flex > button.hover:bg-primary/20
Go to slide 3 div.py-[64px] > div.mb-2.5 > div.flex > button.hover:bg-primary/20
Go to slide 4 div.py-[64px] > div.mb-2.5 > div.flex > button.hover:bg-primary/20
Go to slide 2 main > div.py-16 > div.mt-6 > button.hover:bg-primary/20
Go to slide 3 main > div.py-16 > div.mt-6 > button.hover:bg-primary/20
Go to slide 4 main > div.py-16 > div.mt-6 > button.hover:bg-primary/20
Go to slide 5 main > div.py-16 > div.mt-6 > button.hover:bg-primary/20
Go to slide 6 main > div.py-16 > div.mt-6 > button.hover:bg-primary/20

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
●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.
●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
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●Links have a discernible name
●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Identical links have the same purpose.
●Elements with visible text labels have matching accessible names.
○`[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
○Form elements have associated labels
○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.
○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
○`<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.
○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