Skip to content
https://meltwater.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
65
GRADE
D
FIX
4
REVIEW
5
PASS
4
INFO
0
Checks
13
4 PASS 5 REVIEW 4 FIX
D
Alt Text Quality
Action
7 of 230 images have issues
FIX
7 of 230 images have issues
Critical::
4 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Warning::
3 image(s) with generic alt text
Info::
104 decorative image(s) correctly marked
Info::
119 image(s) with good alt text
230 images 119 good alt text 104 decorative 3 generic 4 missing
IssueCount
missing4 image(s)
generic3 image(s)

Images without alt text are invisible to screen readers.

Why this matters

Each image without alt text is a WCAG 1.1.1 failure — invisible to screen-reader users, lost from Google Image Search.

Learn more ▾

WCAG 2.1 Level A requires text alternatives for non-decorative images. Empty alt='' is fine for decorative; meaningful images need descriptive text. Common fixes: CMS audit + bulk add, build-time linter (alt-text-required ESLint rule), CI gate on Lighthouse a11y score.

Source: WCAG 2.1 SC 1.1.1 / WebAIM Million Report

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::
2 navigation landmark(s) detected
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 2 <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
Form Accessibility
Action
4 of 4 controls have issues
REVIEW
4 of 4 controls have issues
Critical::
4 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="radio" name="hero-carousel-:R2iqm:" id=":R39iiqm:">; <input type="radio" name="hero-carousel-:R2iqm:" id=":R59iiqm:">; <input type="radio" name="hero-carousel-:R2iqm:" id=":R79iiqm:">; <input type="radio" name="hero-carousel-:R2iqm:" id=":R99iiqm:">
4 controls
0 labeled
0 placeholder only
4 unlabeled
ControlTypeLabelMethod
#:R39iiqm:radio(none)none
#:R59iiqm:radio(none)none
#:R79iiqm:radio(none)none
#:R99iiqm:radio(none)none

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

<input type="radio" name="hero-carousel-:R2iqm:" id=":R39iiqm:">; <input type="radio" name="hero-carousel-:R2iqm:" id=":R59iiqm:">; <input type="radio" name="hero-carousel-:R2iqm:" id=":R79iiqm:">; <input type="radio" name="hero-carousel-:R2iqm:" id=":R99iiqm:">

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

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
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Page not found ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✗
B
Favicon & Branding
7 icon(s) detected
REVIEW
7 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 Present
✓ Multiple Sizes Present
B
Web Manifest
Valid manifest
REVIEW
Valid manifest
Info::
Name present: Meltwater
Info::
192x192 icon present
Info::
512x512 icon present
Info::
Display mode: standalone
PWA Install Criteria Not Installable
Name Meltwater ✓192×192 icon ✓512×512 icon ✓Start URL ✗Display Mode standalone ✓
Name Meltwater Display Mode standalone Theme Color #ffffff Background Color #ffffff Icons 2 icon(s)
B
Dark Mode Support
Dark mode detected
REVIEW
Dark mode detected
Info::
color-scheme meta tag present
The site declares support for light and dark color schemes via <meta name='color-scheme'>.
Got: only light
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::
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 only light ✓Dark theme-color Not set ✗CSS indicators Not detected ✗

Detection limited to meta tags and inline styles.

A+
Landmark Structure
5 landmarks
PASS
5 landmarks
Info::
<main> landmark present
Info::
2 <nav> landmark(s) found
Info::
All <nav> elements are properly labeled
Info::
Skip navigation link present
Page Structure — as a screen reader sees it
BANNER header NAV "nav-1" MAIN CONTENTINFO footer
A+
Heading Hierarchy
35 headings
PASS
35 headings
Info::
Single H1 present
  • H1 Gain deeper visibility into your competitors.brand.
  • H2 We empower businesses to be insight-driven
  • H2 Activating the power of data
  • H2 Making insights accessible
  • H2 Redefining PR & marketing impact
  • H2 Your Brand Through the Lens of AI
  • H2 Meet the Meltwater Suite Where smart AI meets human expertise
  • H3 Media Intelligence
  • H3 Social Listening & Analytics
  • H3 AI Visibility Tracking
  • H3 Media Relations
  • H3 Consumer Intelligence
  • H3 Influencer Marketing
  • H3 Sales Intelligence
  • H3 Data & API Integration
  • H2 Our customers say it best
  • H2 Step inside our product
  • H3 Mira: Meltwater AI
  • H3 Media Intelligence
  • H3 Social Listening & Analytics
  • H3 Influencer Marketing
  • H2 Take the guesswork out of your strategy.
  • H2 What makes Meltwater, Meltwater?
  • H3 Who we are
  • H4 Company & Culture
  • H3 Meltwater Community
  • H4 Connect with Peers
  • H3 Product updates
  • H4 From our Engineers
  • H3 Product Features
  • H3 Our Suite
  • H3 Contact
  • H3 Resources
  • H3 Connect
  • H3 About
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 Gain deeper visibili…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 We empower businesse…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Activating the power…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Making insights acce…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Redefining PR & mark…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Your Brand Through t…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Meet the Meltwater S…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Where smart AI meets…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Our customers21.00:13.0:1
#000000
#FFFFFF
Pass
h2 say it best21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Step inside our prod…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Take the guesswork21.00:13.0:1
#000000
#FFFFFF
Pass
h2 out of your strategy…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 What makes Meltwater…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Media Intelligence21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Social Listening & A…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 AI Visibility Tracki…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Media Relations21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Consumer Intelligenc…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Influencer Marketing21.00:13.0: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
Lighthouse Accessibility Audits
Score 90/100 — 3 failing, 33 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
REQUEST DEMO ul.list-none > li.__level1__ > a.header-nav-request-demo > span.CtaLink_tealText__NlKPI
industry. div.mt-20 > h1.text-[36px] > span.relative > span.absolute
80% div.jsx-5cd393af8a9f0d32 > figure.jsx-d3e561a2c22c7bef > div.jsx-d3e561a2c22c7bef > div.jsx-d3e561a2c22c7bef
increase in market research efficency div.jsx-5cd393af8a9f0d32 > figure.jsx-d3e561a2c22c7bef > div.jsx-d3e561a2c22c7bef > div.jsx-d3e561a2c22c7bef
Accept All div.sc-koXPp > div.sc-iHGNWf > div.sc-bmzYkS > button.sc-gsFSXq

These are opportunities to improve the legibility of your content.

Names and labels

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.jsx-5cd393af8a9f0d32 > figure.jsx-d3e561a2c22c7bef > div.jsx-d3e561a2c22c7bef > img.jsx-d3e561a2c22c7bef div.jsx-5cd393af8a9f0d32 > figure.jsx-d3e561a2c22c7bef > div.jsx-d3e561a2c22c7bef > img.jsx-d3e561a2c22c7bef
div.jsx-5cd393af8a9f0d32 > figure.jsx-d3e561a2c22c7bef > div.jsx-d3e561a2c22c7bef > img.jsx-d3e561a2c22c7bef div.jsx-5cd393af8a9f0d32 > figure.jsx-d3e561a2c22c7bef > div.jsx-d3e561a2c22c7bef > img.jsx-d3e561a2c22c7bef
div.jsx-5cd393af8a9f0d32 > figure.jsx-d3e561a2c22c7bef > div.jsx-d3e561a2c22c7bef > img.jsx-d3e561a2c22c7bef div.jsx-5cd393af8a9f0d32 > figure.jsx-d3e561a2c22c7bef > div.jsx-d3e561a2c22c7bef > img.jsx-d3e561a2c22c7bef
div.jsx-5cd393af8a9f0d32 > figure.jsx-d3e561a2c22c7bef > div.jsx-d3e561a2c22c7bef > img.jsx-d3e561a2c22c7bef div.jsx-5cd393af8a9f0d32 > figure.jsx-d3e561a2c22c7bef > div.jsx-d3e561a2c22c7bef > img.jsx-d3e561a2c22c7bef

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 > div.AboutMetaMain_items__Rbrdt > div.AboutMetaMain_item__PQ77V > a.AboutMetaMain_arw__RI4Ro div > div.AboutMetaMain_items__Rbrdt > div.AboutMetaMain_item__PQ77V > a.AboutMetaMain_arw__RI4Ro
div > div.AboutMetaMain_items__Rbrdt > div.AboutMetaMain_item__PQ77V > a.AboutMetaMain_arw__RI4Ro div > div.AboutMetaMain_items__Rbrdt > div.AboutMetaMain_item__PQ77V > a.AboutMetaMain_arw__RI4Ro
div > div.AboutMetaMain_items__Rbrdt > div.AboutMetaMain_item__PQ77V > a.AboutMetaMain_arw__RI4Ro div > div.AboutMetaMain_items__Rbrdt > div.AboutMetaMain_item__PQ77V > a.AboutMetaMain_arw__RI4Ro

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
●`[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
●ARIA input fields have accessible names
●Elements use only permitted ARIA attributes
●ARIA toggle fields have accessible names
●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.
●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.
●`[lang]` attributes have a valid value
●Heading elements appear in a sequentially-descending order
●Skip links are focusable.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●`<video>` elements contain a `<track>` element with `[kind="captions"]`
●Image elements do not have `[alt]` attributes that are redundant text.
●Elements with visible text labels have matching accessible names.
○`[accesskey]` values are unique
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○Elements with the `role=text` attribute do not have focusable descendents.
○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.
○Tables have different content in the summary attribute and `<caption>`.
○All heading elements contain content.
○Uses ARIA roles only on compatible elements
○Identical links have the same purpose.
○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