Skip to content
https://mailerlite.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
55
GRADE
D
FIX
6
REVIEW
3
PASS
4
INFO
0
Checks
13
4 PASS 3 REVIEW 6 FIX
F
404 Error Page
Action
HTTP 403, custom page
FIX
HTTP 403, custom page
Warning::
Unexpected status code: HTTP 403
Expected HTTP 404 but received 403. This may confuse search engine crawlers.
Got: HTTP 403
Info::
Custom styled 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 403 ✗Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗
D
Web Manifest
Action
Not found
FIX
Not found
Info::
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.

D
Dark Mode Support
Action
Theme color only
FIX
Theme color only
Info::
Theme-color present but no dark variant
A theme-color is set but no dark-specific variant was found. The browser toolbar may not adapt for dark mode users.
Got: #ffffff
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 ModePartial Dark Mode
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::
1 navigation landmark(s) detected
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 1 <nav> element(s)
Back to Top
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.
C
Landmark Structure
Action
2 landmarks
REVIEW
2 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Info::
1 <nav> landmark(s) found
Info::
No banner (header) 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!) NAV MAIN (missing!) CONTENTINFO footer

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

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
Form Accessibility
2 of 8 controls have issues
REVIEW
2 of 8 controls have issues
Critical::
1 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-100000">
Warning::
1 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text">
Info::
6 control(s) properly labeled
8 controls
6 labeled
1 placeholder only
1 unlabeled
ControlTypeLabelMethod
#CybotCookiebotDialogBodyLevelButtonNecessarycheckboxStrictly Necessary Cookies (53)for/id
#CybotCookiebotDialogBodyLevelButtonPreferencescheckboxFunctional Cookies (56)for/id
#CybotCookiebotDialogBodyLevelButtonStatisticscheckboxPerformance Cookies (41)for/id
#CybotCookiebotDialogBodyLevelButtonMarketingcheckboxTargeting Cookies (87)for/id
#CybotCookiebotDialogBodyLevelButtonUnlassifiedcheckboxUnclassified Cookies (2)for/id
#emailAddressemailEnter your emailaria-label
inputtext(What are you looking for?)placeholder only
#g-recaptcha-response-100000textarea(none)none

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

<textarea name="g-recaptcha-response" id="g-recaptcha-response-100000">

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="text">

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

B
Favicon & Branding
5 icon(s) detected
REVIEW
5 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
Multiple icon sizes detected
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✓ Multiple Sizes Present
A+
Heading Hierarchy
8 headings
PASS
8 headings
Info::
Single H1 present
  • H6 Get inspired by email marketing case studies
  • H6 Lite is our philosophy
  • H1 Create email marketing automations landing pages signup forms we
  • H2 You're in good company
  • H2 Customer support is always here to help you
  • H2 Integrations
  • H2 Templates that work
  • H2 Keeping it Lite
A+
Alt Text Quality
All 50 images OK
PASS
All 50 images OK
Info::
50 decorative image(s) correctly marked
50 images 50 decorative
All images have appropriate alt text.
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
h2 You're in good compa…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Customer support is …21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Integrations21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Templates that work21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Keeping it Lite21.00:13.0:1
#000000
#FFFFFF
Pass
title Create Email Marketi…11.42:14.5:1
#000000
#BFBFBF
Pass
p By clicking “Accep…11.42:14.5:1
#000000
#BFBFBF
Pass
a View our Cookie Poli…11.42:14.5:1
#000000
#BFBFBF
Pass
button Cookies settings11.42:14.5:1
#000000
#BFBFBF
Pass
button Reject all11.42:14.5:1
#000000
#BFBFBF
Pass
button Accept all cookies11.42:14.5:1
#000000
#BFBFBF
Pass
legend Allow selection11.42:14.5:1
#000000
#BFBFBF
Pass
p Strictly Necessary C…11.42:14.5:1
#000000
#BFBFBF
Pass
button Show details11.42:14.5:1
#000000
#BFBFBF
Pass
span (Strictly Necessary …11.42:14.5:1
#000000
#BFBFBF
Pass
p These cookies are cr…11.42:14.5:1
#000000
#BFBFBF
Pass
th Name11.42:13.0:1
#000000
#BFBFBF
Pass
th Provider11.42:13.0:1
#000000
#BFBFBF
Pass
th Purpose11.42:13.0:1
#000000
#BFBFBF
Pass
th Maximum Storage Dura…11.03:13.0:1
#000000
#BBBCBC
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 93/100 — 2 failing, 27 passed
PASS
93

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

ARIA dialog elements without accessible names may prevent screen readers users from discerning the purpose of these elements. Learn how to make ARIA dialog elements more accessible.

Why this matters

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

Source: MDN Permissions-Policy

Failing Elements
By clicking “Accept all cookies”, you agree to the storing of cookies on your d… body.overflow-y-auto > div#CookieBanner > div#CookieBannerNotice

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
Accept all cookies div.cookiebanner__main > div.cookiebanner__main__inner > div.cookiebanner__buttons > button#CybotCookiebotDialogBodyLevelButtonLevelOptinAllowAll
Sign up free div.flex > div.flex > div.w-full > a.type-primary
Watch demo div.flex > div.flex > div.w-full > a.type-black-outline
Get a free 14-day trial of premium features | No credit card required div.mx-auto > div.flex > div.flex > span.text-sm
14-day div.flex > div.flex > span.text-sm > span.premium-days
always available div.text-center > div.grid > div.flex > span.opacity-50
satisfaction rate div.text-center > div.grid > div.flex > span.opacity-50
avg. response time on live chat div.text-center > div.grid > div.col-span-2 > span.opacity-50
PRODUCT div.container > div.grid > div > span.uppercase
SUPPORT div.container > div.grid > div > span.uppercase
COMPANY div.container > div.grid > div > span.uppercase
For more details, review our Privacy Policy. div.col-span-2 > div.ml-form-embedContainer > div.row-form > span.block
Privacy Policy div.ml-form-embedContainer > div.row-form > span.block > a.underline

These are opportunities to improve the legibility of your content.

○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
●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
●Links are distinguishable without relying on color.
●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
●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
●Identical links have the same purpose.
○`[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
○`<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
○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.
○`<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.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback