Skip to content
https://cbd.int

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
54
GRADE
F
FIX
5
REVIEW
8
PASS
0
INFO
0
Checks
13
8 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
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Skip navigation link detected
Info::
1 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
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)
3 of 6 testable patterns navigation patterns detected. Strong navigation UX with multiple discovery paths.
B
Landmark Structure
3 landmarks
REVIEW
3 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 MAIN (missing!) 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

C
Heading Hierarchy
Action
23 headings, 1 skip(s)
REVIEW
23 headings, 1 skip(s)
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H2 Updates
  • H3 Statement on International Mother Earth Day (22 April 2026)
  • H3 125 Countries Submit 7th National Reports Ahead of COP17
  • H3 Parties to the Convention on Biological Diversity advance key implementation enablers ahead of a decisive COP 17 in October
  • H3 Statement on World Health Day (7 April 2026)
  • H3 Renewed resolve for cooperation among the Secretariats of biodiversity-related conventions
  • H3 Fresh round of intergovernmental negotiations on biodiversity begins in Rome
  • H3 International Day for Biological Diversity (IDB) 2026
  • H3 The Cali Fund Marks One Year with Launch of Website, Logo and Social Media
  • H3 Operationalizing technical and scientific cooperation to turbocharge the KMGBF implementation
  • H3 Astrid Schomaker | Executive Secretary, CBD
  • H2 Programmes
  • H3 Thematic
  • H3 Cross-Cutting
  • H2 Newsletters
  • H2 Clearing-House
  • H4 Clearing-House Mechanism of the Convention on Biological Diversity skipped
  • H4 Biosafety Clearing-House
  • H4 Access and Benefit-Sharing Clearing-House
  • H5 quick links
  • H5 Topics
  • H5 Information
  • H5 A part of

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

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

B
Alt Text Quality
6 of 44 images have issues
REVIEW
6 of 44 images have issues
Warning::
6 image(s) with filename as alt text
Info::
11 decorative image(s) correctly marked
Info::
27 image(s) with good alt text
44 images 27 good alt text 11 decorative 6 generic
IssueCount
filename6 image(s)
B
Form Accessibility
2 of 5 controls have issues
REVIEW
2 of 5 controls have issues
Critical::
2 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="submit" id="edit-submit-search">; <input type="submit" name="op" id="edit-submit">
Info::
3 control(s) properly labeled
5 controls
3 labeled
0 placeholder only
2 unlabeled
ControlTypeLabelMethod
#edit-querytextSearchfor/id
#edit-mergevars-emailemailEmail Addressfor/id
#edit-privacytermscheckboxI accept the privacy termsfor/id
#edit-submit-searchsubmit(none)none
#edit-submitsubmit(none)none

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

<input type="submit" id="edit-submit-search">; <input type="submit" name="op" id="edit-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

C
404 Error Page
Action
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Under Construction ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 16 fail WCAG AA
REVIEW

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

4 pass 16 fail WCAG AA
h2 Updates
1.99:1
#000000
on
#00483A
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Programmes
1.99:1
#000000
on
#00483A
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Newsletters
1.99:1
#000000
on
#00483A
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Clearing-House
1.99:1
#000000
on
#00483A
needs 3.0:1 (large text)
24px · bottom of viewport
h3 Statement on International Mother Earth …
1.99:1
#000000
on
#00483A
needs 3.0:1 (large text)
19px · bottom of viewport
h3 125 Countries Submit 7th National Report…
1.99:1
#000000
on
#00483A
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Parties to the Convention on Biological …
1.99:1
#000000
on
#00483A
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Statement on World Health Day (7 April 2…
1.99:1
#000000
on
#00483A
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Renewed resolve for cooperation among th…
1.99:1
#000000
on
#00483A
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Fresh round of intergovernmental negotia…
1.99:1
#000000
on
#00483A
needs 3.0:1 (large text)
19px · bottom of viewport
h3 International Day for Biological Diversi…
1.99:1
#000000
on
#00483A
needs 3.0:1 (large text)
19px · bottom of viewport
h3 The Cali Fund Marks One Year with Launch…
1.99:1
#000000
on
#00483A
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Operationalizing technical and scientifi…
1.99:1
#000000
on
#00483A
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Astrid Schomaker | Executive Secretary, …
1.99:1
#000000
on
#00483A
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Thematic
1.99:1
#000000
on
#00483A
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Cross-Cutting
1.99:1
#000000
on
#00483A
needs 3.0:1 (large text)
19px · bottom of viewport
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 Updates1.99:13.0:1
#000000
#00483A
Fail
h2 Programmes1.99:13.0:1
#000000
#00483A
Fail
h2 Newsletters1.99:13.0:1
#000000
#00483A
Fail
h2 Clearing-House1.99:13.0:1
#000000
#00483A
Fail
h3 Statement on Interna…1.99:13.0:1
#000000
#00483A
Fail
h3 125 Countries Submit…1.99:13.0:1
#000000
#00483A
Fail
h3 Parties to the Conve…1.99:13.0:1
#000000
#00483A
Fail
h3 Statement on World H…1.99:13.0:1
#000000
#00483A
Fail
h3 Renewed resolve for …1.99:13.0:1
#000000
#00483A
Fail
h3 Fresh round of inter…1.99:13.0:1
#000000
#00483A
Fail
h3 International Day fo…1.99:13.0:1
#000000
#00483A
Fail
h3 The Cali Fund Marks …1.99:13.0:1
#000000
#00483A
Fail
h3 Operationalizing tec…1.99:13.0:1
#000000
#00483A
Fail
h3 Astrid Schomaker | E…1.99:13.0:1
#000000
#00483A
Fail
h3 Thematic1.99:13.0:1
#000000
#00483A
Fail
h3 Cross-Cutting1.99:13.0:1
#000000
#00483A
Fail
title Home | Convention on…21.00:14.5:1
#000000
#FFFFFF
Pass
a Skip to main content21.00:14.5:1
#000000
#FFFFFF
Pass
a Information21.00:14.5:1
#000000
#FFFFFF
Pass
span Contact us10.06:14.5:1
#000000
#B3B5A4
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.

B
Lighthouse Accessibility Audits
Score 83/100 — 6 failing, 24 passed
REVIEW
83

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.

ARIA

Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more about roles and required children elements.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Statement on World Health Day (7 April 2026) Statement by the Executive Secreta… div.updates-content > div#updatesCarousel > div.carousel > div.carousel-inner

When an input field doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more about input field labels.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Statement on World Health Day (7 April 2026) Statement by the Executive Secreta… div.updates-content > div#updatesCarousel > div.carousel > div.carousel-inner

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

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
ALL div.section-header > div.section-header-inner > div.category-wrapper > div.category-name
div.content > form#mailchimp-signup-subscribe-block-frontpage-signup-form-form > div#edit-actions > input#edit-submit div.content > form#mailchimp-signup-subscribe-block-frontpage-signup-form-form > div#edit-actions > input#edit-submit

These are opportunities to improve the legibility of your content.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Clearing-House Mechanism of the Convention on Biological Diversity div.col-md-4 > div.programmes-item > div.programmes-item-content > h4

These are opportunities to improve keyboard navigation in your application.

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.updates-content > div.secretary-block > div.secretary-links > a div.updates-content > div.secretary-block > div.secretary-links > 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.

Best practices

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html.js html.js

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
●Input buttons have discernible text.
●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
●`[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>`).
●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.
●Deprecated ARIA roles were not used
●Image elements do not have `[alt]` attributes that are redundant text.
●Identical links have the same purpose.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○`[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 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
○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