Skip to content
https://matomo.org

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
67
GRADE
D
FIX
4
REVIEW
3
PASS
6
INFO
0
Checks
13
6 PASS 3 REVIEW 4 FIX
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
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Skip navigation link detected
Info::
1 navigation landmark(s) detected
Breadcrumbs
Search
Skip Link Skip link detected
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.
B
Landmark Structure
15 landmarks
REVIEW
15 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::
Skip navigation link present
Page Structure — as a screen reader sees it
BANNER header NAV "Primary" MAIN (missing!) ASIDE 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

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+
Heading Hierarchy
35 headings
PASS
35 headings
Info::
Single H1 present
  • H5 Explore the new Data Warehouse Connector feature. Let’s go →
  • H1 Web & app analytics for teams who demand accuracy
  • H2 Boost your website performance in three easy steps
  • H3 Start a 21-day free Cloud trial. No credit card required
  • H3 Add tracking code to your website or mobile app
  • H3 Start improving your website using real-time data, features and reports
  • H3 Start a 21-day free Cloud trial. No credit card required
  • H3 Add tracking code to your website or mobile app
  • H3 Start improving your website using real-time data, features and reports
  • H2 Recognised as a leading global web analytics solution
  • H2 Don’t damage your reputation with Google Analytics
  • H2 Be in full control with data ownership and privacy protection
  • H2 The 2025 Ethical Marketing Field Guide
  • H2 The 2025 Ethical Marketing Field Guide
  • H2 More reasons why our clients love Matomo
  • H2 Google Analytics Importer
  • H2 Tracking personal data
  • H2 100% accurate data
  • H2 Open source
  • H2 No data limitations
  • H3 Easy to use
  • H3 Enhanced insights
  • H2 Adjust to your needs
  • H2 Support
  • H2 What our clients say about us
  • H3 Certified ISO 27001:2022
  • H2 Company
  • H2 Support
  • H2 Sales
  • H2 Product
  • H2 Industries
  • H2 Legal
  • H2 Resources
  • H2 Comparisons
  • H2 Privacy
A+
Alt Text Quality
All 33 images OK
PASS
All 33 images OK
Info::
7 decorative image(s) correctly marked
Info::
26 image(s) with good alt text
33 images 26 good alt text 7 decorative
All images have appropriate alt text.
A
Form Accessibility
1 of 2 controls have issues
PASS
1 of 2 controls have issues
Critical::
1 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="submit">
Info::
1 control(s) properly labeled
2 controls
1 labeled
0 placeholder only
1 unlabeled
ControlTypeLabelMethod
#mega-search-36573textSearch...aria-label
inputsubmit(none)none

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

<input type="submit">

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
404 Error Page
HTTP 404, custom page
PASS
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
Info::
Search form present on 404 page
404 Page Quality Custom 404 Page
Status Code HTTP 404 Page Title Page Not Found - Analytics Platform - Matomo Custom Styling Navigation Homepage Link Search Form
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 Web & app analytics …19.11:13.0:1
#000000
#EDF5FF
Pass
h2 Boost your website p…19.11:13.0:1
#000000
#EDF5FF
Pass
h2 Recognised as a lead…19.11:13.0:1
#000000
#EDF5FF
Pass
h2 Don’t damage your …19.11:13.0:1
#000000
#EDF5FF
Pass
h2 Be in full control w…19.11:13.0:1
#000000
#EDF5FF
Pass
h2 The 2025 Ethical Mar…19.11:13.0:1
#000000
#EDF5FF
Pass
h2 The 2025 Ethical Mar…19.11:13.0:1
#000000
#EDF5FF
Pass
h2 More reasons why our…19.11:13.0:1
#000000
#EDF5FF
Pass
h2 What our clients say…19.11:13.0:1
#000000
#EDF5FF
Pass
h2 Company19.11:13.0:1
#000000
#EDF5FF
Pass
h2 Support19.11:13.0:1
#000000
#EDF5FF
Pass
h2 Sales19.11:13.0:1
#000000
#EDF5FF
Pass
h2 Product19.11:13.0:1
#000000
#EDF5FF
Pass
h2 Industries19.11:13.0:1
#000000
#EDF5FF
Pass
h2 Legal19.11:13.0:1
#000000
#EDF5FF
Pass
h2 Resources19.11:13.0:1
#000000
#EDF5FF
Pass
h2 Comparisons19.11:13.0:1
#000000
#EDF5FF
Pass
h2 Privacy19.11:13.0:1
#000000
#EDF5FF
Pass
h3 Start a19.11:13.0:1
#000000
#EDF5FF
Pass
h3 No credit card requi…19.11:13.0:1
#000000
#EDF5FF
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, 26 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.

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
21-day free Cloud trial. div.elementor-image-box-content > h3.elementor-image-box-title > span > a
TRY IT FOR FREE div.elementor-button-wrapper > a.elementor-button > span.elementor-button-content-wrapper > span.elementor-button-text
4.8 out of 5 div.elementor-widget-wrap > div.elementor-element > div.elementor-widget-container > p
4.8 out of 5 div.elementor-widget-wrap > div.elementor-element > div.elementor-widget-container > p
4.8 out of 5 div.elementor-widget-wrap > div.elementor-element > div.elementor-widget-container > p
GDPR div.elementor-widget-wrap > div.elementor-element > div.elementor-widget-container > a
CCPA div.elementor-widget-wrap > div.elementor-element > div.elementor-widget-container > a
Take back control of your data now div.elementor-button-wrapper > a.elementor-button > span.elementor-button-content-wrapper > span.elementor-button-text
Get the guide div.elementor-button-wrapper > a.elementor-button > span.elementor-button-content-wrapper > span.elementor-button-text
Learn more div.elementor-element > div.elementor-widget-container > p > a
Learn more div.elementor-widget-wrap > div.elementor-element > div.elementor-widget-container > a
Learn more div.elementor-widget-wrap > div.elementor-element > div.elementor-widget-container > a
Learn more div.elementor-widget-wrap > div.elementor-element > div.elementor-widget-container > a
Learn more div.elementor-widget-wrap > div.elementor-element > div.elementor-widget-container > a
Learn more div.elementor-widget-wrap > div.elementor-element > div.elementor-widget-container > a
Read more testimonials div.elementor-element > div.elementor-widget-container > p > a
Read more div.elementor-widget-container > div.matomo-iso-widget > a.matomo-iso-widget__button > span
TRY IT FOR FREE div.elementor-button-wrapper > a.elementor-button > span.elementor-button-content-wrapper > span.elementor-button-text

These are opportunities to improve the legibility of your content.

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.elementor-swiper > div.elementor-main-swiper > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide 2 div.elementor-swiper > div.elementor-main-swiper > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide 3 div.elementor-swiper > div.elementor-main-swiper > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide 4 div.elementor-swiper > div.elementor-main-swiper > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide 5 div.elementor-swiper > div.elementor-main-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.
`button`, `link`, and `menuitem` elements have accessible names
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 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
Skip links are focusable.
Document has a main landmark.
Deprecated ARIA roles were not used
Identical links have the same purpose.
`[accesskey]` values are unique
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
The document does not use `<meta http-equiv="refresh">`
`<object>` elements have alternate text
Select elements have associated label elements.
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.
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