Skip to content
https://optinmonster.com

Accessibility

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

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

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
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::
19 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 19 <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
Heading Hierarchy
Action
33 headings, 3 skip(s)
REVIEW
33 headings, 3 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H1 → H3 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H2 [Announcement] Mobile Popup Design: Full Control Over How Your Popups Look on Every Device
  • H2 How Storyly Increased Conversions by 80% with Exit-Intent® and Content-Gating
  • H1 Get More Subscribers. Grow Faster.
  • H3 Trusted by 1,200,000+ websites generating millions of leads every month skipped
  • H2 Everything You Need to Convert More Visitors
  • H3 Exit Intent Technology
  • H3 700+ Templates
  • H3 Popups
  • H3 Floating Bars
  • H3 Gamified Wheels
  • H3 Countdown Timers
  • H3 Page Level Targeting
  • H3 Geolocation Targeting
  • H3 8000+ Integrations
  • H2 Why 1.2 Million+ Marketers Choose OptinMonster
  • H2 Recover Abandoning Visitorswith Exit-Intent®
  • H2 Grow Your Email List 2-6x Faster
  • H2 Increase Sales withTargeted Offers
  • H2 Launch Campaigns in Minutes
  • H2 Target With Precision
  • H2 Connect Your Entire Stack
  • H2 What Business Owners Say About OptinMonster
  • H2 Frequently Asked Questions
  • H4 What is OptinMonster? skipped
  • H4 Do I need to have coding skills to use OptinMonster?
  • H4 What’s websites does OptinMonster work with?
  • H4 How much does OptinMonster cost?
  • H4 What integrations are supported?
  • H2 Stop Losing Visitors. Start Converting. It’s That Simple.
  • H4 Company skipped
  • H4 Top Features
  • H4 .
  • H4 Helpful Links

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

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

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
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 Page not found – OptinMonster ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
B
Favicon & Branding
4 icon(s) detected
REVIEW
4 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
Alt Text Quality
All 36 images OK
PASS
All 36 images OK
Info::
3 image(s) with alt text over 125 characters
Info::
8 decorative image(s) correctly marked
Info::
25 image(s) with good alt text
36 images 25 good alt text 8 decorative
IssueCount
too long3 image(s)
A+
Form Accessibility
No form controls
PASS
No form controls
Info::
No form controls on this page
No form controls found.
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 Get More Subscribers…14.31:13.0:1
#000000
#D5D5D5
Pass
h2 Everything You Need …14.31:13.0:1
#000000
#D5D5D5
Pass
h2 Why 1.2 Million+ Mar…14.31:13.0:1
#000000
#D5D5D5
Pass
h2 Recover Abandoning V…14.31:13.0:1
#000000
#D5D5D5
Pass
h2 with Exit-Intent®14.31:13.0:1
#000000
#D5D5D5
Pass
h2 Grow Your Email List…14.31:13.0:1
#000000
#D5D5D5
Pass
h2 Increase Sales with14.31:13.0:1
#000000
#D5D5D5
Pass
h2 Targeted Offers14.31:13.0:1
#000000
#D5D5D5
Pass
h2 Launch Campaigns in …14.31:13.0:1
#000000
#D5D5D5
Pass
h2 Target With Precisio…14.31:13.0:1
#000000
#D5D5D5
Pass
h2 Connect Your Entire …14.31:13.0:1
#000000
#D5D5D5
Pass
h2 What Business Owners…14.31:13.0:1
#000000
#D5D5D5
Pass
h2 Frequently Asked Que…14.31:13.0:1
#000000
#D5D5D5
Pass
h2 Stop Losing Visitors…14.31:13.0:1
#000000
#D5D5D5
Pass
h3 Trusted by 1,200,000…14.31:13.0:1
#000000
#D5D5D5
Pass
h3 Exit Intent Technolo…14.31:13.0:1
#000000
#D5D5D5
Pass
h3 700+ Templates14.31:13.0:1
#000000
#D5D5D5
Pass
h3 Popups14.31:13.0:1
#000000
#D5D5D5
Pass
h3 Floating Bars14.31:13.0:1
#000000
#D5D5D5
Pass
h3 Gamified Wheels14.31:13.0:1
#000000
#D5D5D5
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 92/100 — 3 failing, 27 passed
PASS
92

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
#1 RATED CONVERSION OPTIMIZATION SOFTWARE div.wp-block-group > div.wp-block-cover > div.wp-block-cover__inner-container > p.has-text-align-center
Get OptinMonster Now  div.wp-block-cover__inner-container > div.wp-block-buttons > div.wp-block-button > a.wp-block-button__link
14-Day Money-Back Guarantee div.wp-block-cover__inner-container > div.trust-badges > div.badge > p.badge-text
Setup in Minutes div.wp-block-cover__inner-container > div.trust-badges > div.badge > p.badge-text
No Coding Required div.wp-block-cover__inner-container > div.trust-badges > div.badge > p.badge-text
Popups div.wp-block-group > div.omtc > div.omtc__nav > button.omtc__tab
Recover Abandoning Visitors Now → div.wp-block-column > div.wp-block-group > p.has-primary-500-color > a
Get More Email Subscribers Now → div.wp-block-column > div.wp-block-group > p.has-primary-500-color > a
Increase Your Sales Now → div.wp-block-column > div.wp-block-group > p.has-primary-500-color > a
Get OptinMonster Now→ div.wp-block-column > div.wp-block-group > p.has-primary-500-color > a
Create Personalized Campaigns Now → div.wp-block-column > div.wp-block-group > p.has-primary-500-color > a
Get OptinMonster Now→ div.wp-block-column > div.wp-block-group > p.has-primary-500-color > a
Get OptinMonster Now      div.wp-block-column > div.wp-block-buttons > div.wp-block-button > a.wp-block-button__link

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
Trusted by 1,200,000+ websites generating millions of leads every month div.wp-site-blocks > div.entry-content > div.wp-block-group > h3.wp-block-heading
Company div.wp-block-group > div.wp-block-columns > div.wp-block-column > h4.wp-block-heading

These are opportunities to improve keyboard navigation in your application.

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.wp-block-group > div.wp-block-group > figure.wp-block-image > a div.wp-block-group > div.wp-block-group > figure.wp-block-image > a

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
●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
●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.
●`button`, `link`, and `menuitem` elements have accessible names
●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.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●`<video>` elements contain a `<track>` element with `[kind="captions"]`
●Uses ARIA roles only on compatible elements
○`[accesskey]` values are unique
○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
○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.
○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
○Tables have different content in the summary attribute and `<caption>`.
○All heading elements contain content.
○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