Skip to content
https://datareportal.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
60
GRADE
D
FIX
5
REVIEW
4
PASS
4
INFO
0
Checks
13
4 PASS 4 REVIEW 5 FIX
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
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::
6 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 6 <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
13 landmarks
REVIEW
13 landmarks
Info::
<main> landmark present
Info::
6 <nav> landmark(s) found
Warning::
6 of 6 <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 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
Alt Text Quality
4 of 12 images have issues
REVIEW
4 of 12 images have issues
Warning::
4 image(s) with filename as alt text
Info::
8 image(s) with good alt text
12 images 8 good alt text 4 generic
IssueCount
filename4 image(s)
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 4 fail WCAG AA
REVIEW

Analyzes text contrast against the actual rendered page, including background images, gradients, and overlays that CSS-based tools cannot detect.

16 pass 4 fail WCAG AA
title DataReportal – Global Digital Insights
1.40:1
#000000
on
#21272F
needs 4.5:1 (normal text)
16px · top of page (header area)
span We value your privacy
1.40:1
#000000
on
#21272F
needs 4.5:1 (normal text)
16px · top of page (header area)
div We and our
1.40:1
#000000
on
#21272F
needs 4.5:1 (normal text)
16px · top of page (header area)
button partners
1.40:1
#000000
on
#21272F
needs 4.5:1 (normal text)
16px · top of page (header area)
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 ALL THE NUMBERS YOU …21.00:13.0:1
#000000
#FFFFFF
Pass
h1 Featured Reports21.00:13.0:1
#000000
#FFFFFF
Pass
h1 Quick Search21.00:13.0:1
#000000
#FFFFFF
Pass
h1 SELECTED CONTENT21.00:13.0:1
#000000
#FFFFFF
Pass
h1 Latest Reports21.00:13.0:1
#000000
#FFFFFF
Pass
h1 Complete Collection21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Digital 2026 Global …21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Digital 2026 Local C…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Digital 2025 July Gl…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Digital 2025 Global …21.00:13.0:1
#000000
#FFFFFF
Pass
h2 GLOBAL OVERVIEWS21.00:13.0:1
#000000
#FFFFFF
Pass
h2 LOCAL INSIGHTS21.00:13.0:1
#000000
#FFFFFF
Pass
h2 SPECIALIST REPORTS21.00:13.0:1
#000000
#FFFFFF
Pass
h2 DIGITAL 2024 GLOBAL …21.00:13.0:1
#000000
#FFFFFF
Pass
h2 JAPAN’S DIGITAL DI…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 GET INSIGHTS IN YOUR…21.00:13.0:1
#000000
#FFFFFF
Pass
title DataReportal – Glo…1.40:14.5:1
#000000
#21272F
Fail
span We value your privac…1.40:14.5:1
#000000
#21272F
Fail
div We and our1.40:14.5:1
#000000
#21272F
Fail
button partners1.40:14.5:1
#000000
#21272F
Fail

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
Heading Hierarchy
16 headings
PASS
16 headings
Warning::
Multiple H1 headings (6 found)
A page should have only one H1. Multiple H1s dilute the document outline.
  • H1 ALL THE NUMBERS YOU NEED
  • H1 Featured Reports duplicate H1
  • H2 Digital 2026 Global Overview Report
  • H2 Digital 2026 Local Country Headlines
  • H2 Digital 2025 July Global Statshot Report
  • H2 Digital 2025 Global Overview Report
  • H1 Quick Search duplicate H1
  • H2 GLOBAL OVERVIEWS
  • H2 LOCAL INSIGHTS
  • H2 SPECIALIST REPORTS
  • H1 SELECTED CONTENT duplicate H1
  • H2 DIGITAL 2024 GLOBAL NEWS REPORT
  • H2 JAPAN’S DIGITAL DIFFERENCES
  • H2 GET INSIGHTS IN YOUR INBOX
  • H1 Latest Reports duplicate H1
  • H1 Complete Collection duplicate H1

A page should have only one H1. Multiple H1s dilute the document outline.

Why this matters

Multiple H1s blur the page's primary topic — screen-reader users and Google both prefer one H1.

Learn more ▾

HTML5's outline algorithm technically allows multiple H1s within sectioning content, but no browser implements it. In practice: one H1 per page. Use H2-H6 for subsections.

Source: WCAG 2.4.6 / Google Search Central

A
Form Accessibility
1 of 4 controls have issues
PASS
1 of 4 controls have issues
Critical::
1 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-100000">
Info::
3 control(s) properly labeled
4 controls
3 labeled
0 placeholder only
1 unlabeled
ControlTypeLabelMethod
qtextSearcharia-label
inputsearchSearcharia-label
#email-yui_3_17_2_1_1537454203484_92915-fieldemailEmail Addressfor/id
#g-recaptcha-response-100000textarea(none)none

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

<textarea name="g-recaptcha-response" id="g-recaptcha-response-100000">

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 Lost — DataReportal – Global Digital Insights ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✓
A
Lighthouse Accessibility Audits
Score 93/100 — 2 failing, 24 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
div.newsletter-form-body > div.newsletter-form-fields-wrapper > div#email-yui_3_17_2_1_1537454203484_92915 > input#email-yui_3_17_2_1_1537454203484_92915-field div.newsletter-form-body > div.newsletter-form-fields-wrapper > div#email-yui_3_17_2_1_1537454203484_92915 > input#email-yui_3_17_2_1_1537454203484_92915-field

These are opportunities to improve the legibility of your content.

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#yui_3_17_2_1_1776815706188_70 > div.indesignWide > div.indesign-wrapper > iframe div#yui_3_17_2_1_1776815706188_70 > div.indesignWide > div.indesign-wrapper > iframe
div#yui_3_17_2_1_1776815706188_74 > div.indesignWide > div.indesign-wrapper > iframe div#yui_3_17_2_1_1776815706188_74 > div.indesignWide > div.indesign-wrapper > iframe
div#yui_3_17_2_1_1776815706188_78 > div.indesignWide > div.indesign-wrapper > iframe div#yui_3_17_2_1_1776815706188_78 > div.indesignWide > div.indesign-wrapper > iframe
div#yui_3_17_2_1_1776815706188_82 > div.indesignWide > div.indesign-wrapper > iframe div#yui_3_17_2_1_1776815706188_82 > div.indesignWide > div.indesign-wrapper > iframe
div#yui_3_17_2_1_1776815706188_86 > div.indesign-wrapper > div.indesignWide > iframe div#yui_3_17_2_1_1776815706188_86 > div.indesign-wrapper > div.indesignWide > iframe
div#yui_3_17_2_1_1776815706188_90 > div.slideshare-wrapper-landing > div.youtubeWide > iframe div#yui_3_17_2_1_1776815706188_90 > div.slideshare-wrapper-landing > div.youtubeWide > iframe

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
●`[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
●Form elements have associated labels
●`[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
●Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
●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
●No element has a `[tabindex]` value greater than 0
●Touch targets have sufficient size and spacing.
●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.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○`[aria-hidden="true"]` elements do not contain focusable descendents
○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
○Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
○List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
○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
○`<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