Skip to content
https://copernicus.eu

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
52
GRADE
F
FIX
6
REVIEW
6
PASS
1
INFO
0
Checks
13
1 PASS 6 REVIEW 6 FIX
F
Favicon & Branding
Action
1 icon(s) detected
FIX
1 icon(s) detected
Warning::
No favicon.ico at site root
Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.
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 Missing
✓ 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
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Skip navigation link detected
Info::
3 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 3 <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
Heading Hierarchy
19 headings
REVIEW
19 headings
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
  • H3 Select your language
  • H3 Highlights
  • H2 OBSERVER: A quantum secure future with IRIS²
  • H2 OBSERVER: Five Copernicus apps transforming climate and atmosphere…
  • H2 OBSERVER: Record-breaking 2025 fire season in the EU — insights from…
  • H2 OBSERVER: Understanding the role of CLMS in carbon removal monitoring
  • H2 OBSERVER: Understanding space weather events
  • H2 OBSERVER: Artificial Intelligence and Earth Observation workshop looks…
  • H3 Copernicus services catalogue
  • H2 Image of the day
  • H3 Snow-capped Mount Etna and coastal waters in Sicily, Italy
  • H3 Copernicus Services
  • H3 Copernicus Thematic Hubs
  • H3 Use cases
  • H3 Social Media Feed
  • H4 Newsletter
  • H4 Thank you!
  • H2 We use cookies on this site to enhance your user experience
  • H3 Select your language

Every page should have one H1 that describes the page content.

Why this matters

No H1 means screen-reader users can't identify the page's primary topic, and Google's content-extraction degrades.

Learn more ▾

The H1 is the document title for assistive tech and a strong signal to search engines about page topic. Pages without one force screen readers to fall back to the <title> attribute or page chrome. Add a single H1 that names the page's primary subject.

Source: WCAG 2.4.6 / Google Search Central

B
Alt Text Quality
2 of 37 images have issues
REVIEW
2 of 37 images have issues
Critical::
2 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Info::
23 decorative image(s) correctly marked
Info::
12 image(s) with good alt text
37 images 12 good alt text 23 decorative 2 missing
IssueCount
missing2 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

B
Form Accessibility
4 of 8 controls have issues
REVIEW
4 of 8 controls have issues
Warning::
4 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">; <input type="text" name="search_api_fulltext" id="edit-search-api-fulltext">; <input type="text" name="search_api_fulltext" id="edit-search-api-fulltext">; <input type="text" name="search_api_fulltext" id="edit-search-api-fulltext">
Info::
4 control(s) properly labeled
8 controls
4 labeled
4 placeholder only
0 unlabeled
ControlTypeLabelMethod
fields[email]emailemailaria-label
#cookie-category-necessarycheckboxStrictly necessaryfor/id
#cookie-category-performancecheckboxPerformancefor/id
#cookie-category-functionalcheckboxFunctionalfor/id
#edit-search-api-fulltexttext(search)placeholder only
#edit-search-api-fulltexttext(search)placeholder only
#edit-search-api-fulltexttext(search)placeholder only
#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">; <input type="text" name="search_api_fulltext" id="edit-search-api-fulltext">; <input type="text" name="search_api_fulltext" id="edit-search-api-fulltext">; <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

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 404 | Copernicus ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✗
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 16 pass AA only
title Homepage | Copernicus
2.11:1
#000000
on
#364261
needs 4.5:1 (normal text)
16px · top of page (header area)
a Skip to main content
2.11:1
#000000
on
#364261
needs 4.5:1 (normal text)
16px · top of page (header area)
a About Copernicus
1.78:1
#000000
on
#283759
needs 4.5:1 (normal text)
16px · top of page (header area)
a Copernicus Services
2.26:1
#000000
on
#3A4762
needs 4.5:1 (normal text)
16px · top of page (header area)
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 OBSERVER: A quantum …4.44:13.0:1
#000000
#677581
Pass
h2 OBSERVER: Five Coper…4.44:13.0:1
#000000
#677581
Pass
h2 OBSERVER: Record-bre…4.44:13.0:1
#000000
#677581
Pass
h2 OBSERVER: Understand…4.44:13.0:1
#000000
#677581
Pass
h2 OBSERVER: Understand…4.44:13.0:1
#000000
#677581
Pass
h2 OBSERVER: Artificial…4.44:13.0:1
#000000
#677581
Pass
h2 Image of the day4.44:13.0:1
#000000
#677581
Pass
h2 We use cookies on th…4.44:13.0:1
#000000
#677581
Pass
h3 Select your language4.44:13.0:1
#000000
#677581
Pass
h3 Highlights4.44:13.0:1
#000000
#677581
Pass
h3 Copernicus services …4.44:13.0:1
#000000
#677581
Pass
h3 Copernicus Services4.44:13.0:1
#000000
#677581
Pass
h3 Copernicus Thematic …4.44:13.0:1
#000000
#677581
Pass
h3 Use cases4.44:13.0:1
#000000
#677581
Pass
h3 Social Media Feed4.44:13.0:1
#000000
#677581
Pass
h3 Select your language4.44:13.0:1
#000000
#677581
Pass
title Homepage | Copernicu…2.11:14.5:1
#000000
#364261
Fail
a Skip to main content2.11:14.5:1
#000000
#364261
Fail
a About Copernicus1.78:14.5:1
#000000
#283759
Fail
a Copernicus Services2.26:14.5:1
#000000
#3A4762
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.

B
Lighthouse Accessibility Audits
Score 81/100 — 5 failing, 25 passed
REVIEW
81

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
OBSERVER: Five Copernicus apps transforming climate and atmosphere insights div.slick-slide > div > li > a.d-inline-block
View image information & credits div.ccl-container > div.ccl-banner-top-bar-right > span#btn-popup-banner > span

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.ccl-container > div.ccl-banner-top-bar-right > span#btn-popup-banner > img div.ccl-container > div.ccl-banner-top-bar-right > span#btn-popup-banner > img
footer.ccl-footer > div.ccl-footer-main > div.ccl-footer-logo > img.ccl-footer-logo-img footer.ccl-footer > div.ccl-footer-main > div.ccl-footer-logo > img.ccl-footer-logo-img

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.d-block > nav#siteNavigation > div.container > a.navbar-brand div.d-block > nav#siteNavigation > div.container > a.navbar-brand
div.slick-track > div.ccl-list-item > div.card-highlights > a.ccl-list-item-image div.slick-track > div.ccl-list-item > div.card-highlights > a.ccl-list-item-image
  div.slick-track > div.ccl-list-item > div.card-highlights > a.full-link
div.ccl-container > div.ccl-footer-col > div.ccl-footer-social > a div.ccl-container > div.ccl-footer-col > div.ccl-footer-social > a
div.ccl-container > div.ccl-footer-col > div.ccl-footer-social > a div.ccl-container > div.ccl-footer-col > div.ccl-footer-social > a
div.ccl-container > div.ccl-footer-col > div.ccl-footer-social > a div.ccl-container > div.ccl-footer-col > div.ccl-footer-social > a
div.ccl-container > div.ccl-footer-col > div.ccl-footer-social > a div.ccl-container > div.ccl-footer-col > div.ccl-footer-social > a
div.ccl-container > div.ccl-footer-col > div.ccl-footer-social > a div.ccl-container > div.ccl-footer-col > div.ccl-footer-social > 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 have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
OBSERVER: Understanding the role of CLMS in carbon removal monitoring OBSERVER:… div.ccl-banner-top-bar > div.ccl-container > div.ccl-banner-top-bar-left > ul#breakingNews

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
OBSERVER: Five Copernicus apps transforming climate and atmosphere insights div.slick-track > div.slick-slide > div > 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
●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.
●`[aria-hidden="true"]` elements do not contain focusable descendents
●Elements use only permitted ARIA attributes
●Document has a `<title>` element
●`<frame>` or `<iframe>` elements have a title
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●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
●ARIA IDs are unique
●Identical links have the same purpose.
●Elements with visible text labels have matching accessible names.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements 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
○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
○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.
○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.
A
Landmark Structure
8 landmarks
PASS
8 landmarks
Info::
<main> landmark present
Info::
3 <nav> landmark(s) found
Warning::
3 of 3 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
Info::
Skip navigation link present
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

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

Send Feedback