Skip to content
https://ipsos.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
58
GRADE
D
FIX
6
REVIEW
2
PASS
5
INFO
0
Checks
13
5 PASS 2 REVIEW 6 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-8m1n0y
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://ipsos.com/manifest.json contains invalid JSON. Browsers cannot parse it.
Got: https://ipsos.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
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Skip navigation link detected
Info::
4 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 4 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
3 of 6 testable patterns navigation patterns detected. Strong navigation UX with multiple discovery paths.
B
Lighthouse Accessibility Audits
Score 89/100 — 3 failing, 24 passed
REVIEW
89

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
We and our 4 partners wish to store and access information on your devices (suc… div.sd-cmp-gpI1s > div.sd-cmp-xbcna > div.sd-cmp-VhJqD > div
partners div.sd-cmp-xbcna > div.sd-cmp-VhJqD > div > strong.vendors
This is used to develop and provide you with services, content, and advertiseme… div.sd-cmp-gpI1s > div.sd-cmp-xbcna > div.sd-cmp-VhJqD > div
You can "accept all" and withdraw your consent at any time via the "cookies" fo… div.sd-cmp-vfoED > div.sd-cmp-gpI1s > div.sd-cmp-xbcna > div.sd-cmp-VhJqD
powered by div.sd-cmp-Wfd7X > div.sd-cmp-KebVX > a > span

These are opportunities to improve the legibility of your content.

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.latest-insights__publications > div.latest-insights__left > div.insights-block > a div.latest-insights__publications > div.latest-insights__left > div.insights-block > a
div.footer__social > ul.links > li > a div.footer__social > ul.links > li > a
div.footer__social > ul.links > li > a div.footer__social > ul.links > li > a
div.footer__social > ul.links > li > a div.footer__social > ul.links > li > a
div.footer__social > ul.links > li > a div.footer__social > ul.links > li > a
div.footer__social > ul.links > li > a div.footer__social > ul.links > li > 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.

Tables and lists

Screen readers require list items (`<li>`) to be contained within a parent `<ul>`, `<ol>` or `<menu>` to be announced properly. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Open header#header > div.header__inner > ul.header__buttons > li
Select header#header > div.header__inner > ul.header__buttons > li

These are opportunities to improve the experience of reading tabular or list data using 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
●`[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.
●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
●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
●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
●Uses ARIA roles only on compatible elements
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○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
○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.
○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.
○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.
A+
Landmark Structure
11 landmarks
PASS
11 landmarks
Info::
<main> landmark present
Info::
4 <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 "Skip links" MAIN CONTENTINFO footer
A+
Heading Hierarchy
12 headings
PASS
12 headings
Info::
Single H1 present
  • H4 Search
  • H1 How to build trust in the AI era
  • H2 About Ipsos
  • H2 Featured Insights & Publications
  • H2 What The Future
  • H3 Ipsos Data Drops 2026
  • H3 Insights to Activate
  • H3 Discover Ipsos’ KnowledgePanel: The Gold Standard in Online Research Panels
  • H3 Welcome to The Path
  • H2 Insights to Activate Impact Stories
  • H2 90 markets
  • H2 Follow us on
A+
Alt Text Quality
All 5 images OK
PASS
All 5 images OK
Info::
1 decorative image(s) correctly marked
Info::
4 image(s) with good alt text
5 images 4 good alt text 1 decorative
All images have appropriate alt text.
A
Form Accessibility
1 of 1 controls have issues
PASS
1 of 1 controls have issues
Warning::
1 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" name="search_api_fulltext" id="edit-search-api-fulltext">
1 controls
0 labeled
1 placeholder only
0 unlabeled
ControlTypeLabelMethod
#edit-search-api-fulltexttext(Search)placeholder only

Placeholder text disappears on focus and is not a reliable label.

<input type="text" name="search_api_fulltext" id="edit-search-api-fulltext">

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

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 How to build trust i…14.68:13.0:1
#000000
#B4E0E0
Pass
h2 About Ipsos14.68:13.0:1
#000000
#B4E0E0
Pass
h2 Featured Insights & …14.68:13.0:1
#000000
#B4E0E0
Pass
h2 Insights to Activate…14.68:13.0:1
#000000
#B4E0E0
Pass
h2 90 markets14.68:13.0:1
#000000
#B4E0E0
Pass
h2 Follow us on14.68:13.0:1
#000000
#B4E0E0
Pass
title Ipsos | Global Marke…14.68:14.5:1
#000000
#B4E0E0
Pass
a Skip to Content14.68:14.5:1
#000000
#B4E0E0
Pass
a Skip to Footer12.64:14.5:1
#000000
#B2CED1
Pass
a Ipsos iSay10.38:14.5:1
#000000
#B4B6BE
Pass
a Ipsos.Digital10.75:14.5:1
#000000
#BAB8C5
Pass
a Contact us11.10:14.5:1
#000000
#BFBACB
Pass
a Solutions11.26:14.5:1
#000000
#C3BAD1
Pass
a Insights Hub11.52:14.5:1
#000000
#C7BBD7
Pass
button Insights Hub11.66:14.5:1
#000000
#C8BCDA
Pass
span Insights Hub11.58:14.5:1
#000000
#C8BBDA
Pass
a Publications11.60:14.5:1
#000000
#C9BBDA
Pass
a Surveys11.63:14.5:1
#000000
#CABBDA
Pass
a Event Replays11.60:14.5:1
#000000
#C9BBDA
Pass
a News11.55:14.5:1
#000000
#C7BBDA
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.

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback