Skip to content
https://dotomi.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
48
GRADE
F
FIX
7
REVIEW
2
PASS
4
INFO
0
Checks
13
4 PASS 2 REVIEW 7 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-kuww7c
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
2 icon(s) detected
FIX
2 icon(s) detected
Info::
favicon.ico present at site root
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 Present
✓ 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://dotomi.com/manifest.json contains invalid JSON. Browsers cannot parse it.
Got: https://dotomi.com/manifest.json

Manifest contains invalid JSON.

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::
3 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 3 <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.
B
Landmark Structure
9 landmarks
REVIEW
9 landmarks
Info::
<main> landmark present
Info::
3 <nav> landmark(s) found
Warning::
1 of 3 <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 "Epsilon main navigation" MAIN CONTENTINFO footer

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

B
Form Accessibility
2 of 18 controls have issues
REVIEW
2 of 18 controls have issues
Critical::
2 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="text" id="react-select-4-input">
Info::
16 control(s) properly labeled
18 controls
16 labeled
0 placeholder only
2 unlabeled
ControlTypeLabelMethod
firstNametextnone
lastNametextnone
emailAddresstextnone
titletextnone
companytextnone
comments1textareanone
communicationsOptIncheckboxnone
selectselectSelect a regionaria-label
#ot-group-id-C0005checkboxPublicidadefor/id
#ot-group-id-C0003checkboxDesempenhofor/id
#ot-group-id-C0002checkboxFuncionalidadefor/id
#vendor-search-handlertextPesquisa de lista de cookiesaria-label
#chkbox-idcheckboxcheckbox labelfor/id
#select-all-hosts-groups-handlercheckboxcheckbox labelfor/id
#select-all-vendor-groups-handlercheckboxcheckbox labelfor/id
#select-all-vendor-leg-handlercheckboxcheckbox labelfor/id
#react-select-4-inputtext(none)none
#g-recaptcha-responsetextarea(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="text" id="react-select-4-input">

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

A+
Heading Hierarchy
25 headings
PASS
25 headings
Info::
Single H1 present
  • H1 Personalizationat scale.
  • H2 Trusted by the world's leading brands
  • H2 Epsilon PeopleCloud
  • H3 1 View, 1 Vision, 1 Voice
  • H2 1 View
  • H2 1 Vision
  • H2 1 Voice
  • H2 Reach real people, drive real results
  • H2 What Epsilon can do for you
  • H3 Identify high-value customers​​​​‌‍​‍​‍‌‍‌​‍‌‍‍‌‌‍‌‌‍‍‌‌‍‍​‍​‍​‍‍​‍​‍‌​‌‍​‌‌
  • H3 Unify and cleanse your first-party data
  • H3 Connect messages across email and digital media​​​​‌‍​‍​‍‌‍‌​‍‌‍‍‌‌‍‌‌‍‍‌‌‍‍​‍​‍​‍‍​‍​‍‌​
  • H2 Platform
  • H2 Products
  • H2 Industries
  • H2 Use cases
  • H2 Resources
  • H2 About
  • H2 Centro de preferências de privacidade
  • H3 Gerir preferências de cookies
  • H4 Estritamente necessários
  • H4 Publicidade
  • H4 Desempenho
  • H4 Funcionalidade
  • H3 Lista de cookies
A
Alt Text Quality
3 of 28 images have issues
PASS
3 of 28 images have issues
Warning::
3 image(s) with filename as alt text
Info::
14 decorative image(s) correctly marked
Info::
11 image(s) with good alt text
28 images 11 good alt text 14 decorative 3 generic
IssueCount
filename3 image(s)
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 Trusted by the world…5.24:13.0:1
#000000
#7F7F7F
Pass
h2 Epsilon PeopleCloud5.24:13.0:1
#000000
#7F7F7F
Pass
h2 1 View5.24:13.0:1
#000000
#7F7F7F
Pass
h2 1 Vision5.24:13.0:1
#000000
#7F7F7F
Pass
h2 1 Voice5.24:13.0:1
#000000
#7F7F7F
Pass
h2 Reach real people, d…5.24:13.0:1
#000000
#7F7F7F
Pass
h2 What Epsilon can do …5.24:13.0:1
#000000
#7F7F7F
Pass
h2 Platform5.24:13.0:1
#000000
#7F7F7F
Pass
h2 Products5.24:13.0:1
#000000
#7F7F7F
Pass
h2 Industries5.24:13.0:1
#000000
#7F7F7F
Pass
h2 Use cases5.24:13.0:1
#000000
#7F7F7F
Pass
h2 Resources5.24:13.0:1
#000000
#7F7F7F
Pass
h2 About5.24:13.0:1
#000000
#7F7F7F
Pass
h2 Centro de preferênc…5.24:13.0:1
#000000
#7F7F7F
Pass
h3 1 View, 1 Vision, 1 …5.24:13.0:1
#000000
#7F7F7F
Pass
h3 Identify high-value …5.24:13.0:1
#000000
#7F7F7F
Pass
h3 Unify and cleanse yo…5.24:13.0:1
#000000
#7F7F7F
Pass
h3 Connect messages acr…5.24:13.0:1
#000000
#7F7F7F
Pass
h3 Gerir preferências …5.24:13.0:1
#000000
#7F7F7F
Pass
h3 Lista de cookies5.24:13.0:1
#000000
#7F7F7F
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 94/100 — 2 failing, 29 passed
PASS
94

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.

Names and labels

Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.Panel-module_container__8j3Om > div.Panel-module_video__rFmRn > div.Panel-module_videoSpacer__fbxa- > iframe.vimeoIframe div.Panel-module_container__8j3Om > div.Panel-module_video__rFmRn > div.Panel-module_videoSpacer__fbxa- > iframe.vimeoIframe
div.Panel-module_container__8j3Om > div.Panel-module_video__rFmRn > div.Panel-module_videoSpacer__fbxa- > iframe.vimeoIframe div.Panel-module_container__8j3Om > div.Panel-module_video__rFmRn > div.Panel-module_videoSpacer__fbxa- > iframe.vimeoIframe
div.Panel-module_container__8j3Om > div.Panel-module_video__rFmRn > div.Panel-module_videoSpacer__fbxa- > iframe.vimeoIframe div.Panel-module_container__8j3Om > div.Panel-module_video__rFmRn > div.Panel-module_videoSpacer__fbxa- > iframe.vimeoIframe

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

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 section.CarouselClientSuccess-module-scss-module__AXIkRG__clientSuccessSlider > div.swiper > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide 2 section.CarouselClientSuccess-module-scss-module__AXIkRG__clientSuccessSlider > div.swiper > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide 3 section.CarouselClientSuccess-module-scss-module__AXIkRG__clientSuccessSlider > div.swiper > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide 4 section.CarouselClientSuccess-module-scss-module__AXIkRG__clientSuccessSlider > div.swiper > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide 5 section.CarouselClientSuccess-module-scss-module__AXIkRG__clientSuccessSlider > div.swiper > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide 6 section.CarouselClientSuccess-module-scss-module__AXIkRG__clientSuccessSlider > div.swiper > div.swiper-pagination > span.swiper-pagination-bullet

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.
●Select elements have associated label elements.
●`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
●Background and foreground colors have a sufficient contrast ratio
●Document has a `<title>` element
●`<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
●No element has a `[tabindex]` value greater than 0
●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.
●Elements with visible text labels have matching accessible names.
○`[accesskey]` values are unique
○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
○Form elements have associated labels
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○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.
○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