Skip to content
https://iucn.org

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
63
GRADE
D
FIX
4
REVIEW
6
PASS
3
INFO
0
Checks
13
3 PASS 6 REVIEW 4 FIX
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.

F
Navigation UX
Action
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Skip navigation link detected
Info::
18 navigation landmark(s) detected
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 18 <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
Heading Hierarchy
7 headings, 1 skip(s)
REVIEW
7 headings, 1 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H1 → H3 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
2 empty heading(s)
Empty headings appear in the document outline but provide no information.
  • H1 Emperor penguin and Antarctic fur seal now Endangered due to climate change – IUCN Red List
  • H3 Heading Our Members skipped
  • H3 (empty)
  • H3 (empty)
  • H2 75 years of vision and impact
  • H3 Stay informed.
  • H2 Use of personal data and cookies

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

Empty headings appear in the document outline but provide no information.

Why this matters

Empty <hN> tags break the document outline — screen-reader users navigating by heading hit dead silence.

Source: WCAG 2.4.6

B
Alt Text Quality
3 of 43 images have issues
REVIEW
3 of 43 images have issues
Critical::
3 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Info::
3 decorative image(s) correctly marked
Info::
37 image(s) with good alt text
43 images 37 good alt text 3 decorative 3 missing
IssueCount
missing3 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
2 of 4 controls have issues
REVIEW
2 of 4 controls have issues
Warning::
2 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" name="search_input" id="edit-search-input">; <input type="text" name="search_input" id="edit-search-input">
Info::
2 control(s) properly labeled
4 controls
2 labeled
2 placeholder only
0 unlabeled
ControlTypeLabelMethod
#edit-submitsubmitsite searcharia-label
#edit-submitsubmitsite searcharia-label
#edit-search-inputtext(Search)placeholder only
#edit-search-inputtext(Search)placeholder only

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

<input type="text" name="search_input" id="edit-search-input">; <input type="text" name="search_input" id="edit-search-input">

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
Info::
Homepage link present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Page not found | IUCN ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
C
Favicon & Branding
Action
13 icon(s) detected
REVIEW
13 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::
Apple touch icon present
Info::
Multiple icon sizes detected
✗ favicon.ico Missing
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✓ Multiple Sizes Present
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 10 fail WCAG AA
REVIEW

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

10 pass 10 fail WCAG AA 7 pass AA only
h2 Use of personal data and cookies
1.05:1
#000000
on
#000915
needs 3.0:1 (large text)
24px · bottom of viewport
h3 Stay informed.
1.05:1
#000000
on
#000915
needs 3.0:1 (large text)
19px · bottom of viewport
a About IUCN
4.38:1
#000000
on
#717278
needs 4.5:1 (normal text)
16px · top of page (header area)
a Mediterranean
4.17:1
#000000
on
#6B6F78
needs 4.5:1 (normal text)
16px · above the fold
a Mexico, Central America and the Caribbea…
3.22:1
#000000
on
#585E68
needs 4.5:1 (normal text)
16px · above the fold
a North America
2.05:1
#000000
on
#3A414F
needs 4.5:1 (normal text)
16px · mid-page · over background image/gradient
a Oceania
2.26:1
#000000
on
#3D4856
needs 4.5:1 (normal text)
16px · mid-page
a South America
1.74:1
#000000
on
#2B3747
needs 4.5:1 (normal text)
16px · mid-page
a West and Central Africa
1.37:1
#000000
on
#182637
needs 4.5:1 (normal text)
16px · mid-page
a West Asia
1.08:1
#000000
on
#040D18
needs 4.5:1 (normal text)
16px · mid-page

1 contrast failures on background images/gradients

These failures are invisible to CSS-based accessibility tools like Lighthouse. The text may be fine on a solid background, but fails when rendered over an image or gradient.

Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 Use of personal data…1.05:13.0:1
#000000
#000915
Fail
h3 Stay informed.1.05:13.0:1
#000000
#000915
Fail
title IUCN21.00:14.5:1
#000000
#FFFFFF
Pass
a Skip to main content21.00:14.5:1
#000000
#FFFFFF
Pass
a About IUCN4.38:14.5:1
#000000
#717278
Fail
a News & Events6.98:14.5:1
#000000
#91959B
Pass
a Press7.18:14.5:1
#000000
#94979E
Pass
a Blog6.44:14.5:1
#000000
#8D8E95
Pass
a Regions5.20:14.5:1
#000000
#7F7E81
Pass
a Asia5.01:14.5:1
#000000
#7C7B81
Pass
a Eastern and Southern…4.64:14.5:1
#000000
#76767A
Pass
a Eastern Europe and C…4.67:14.5:1
#000000
#77767C
Pass
a Europe5.99:14.5:1
#000000
#868990
Pass
a Mediterranean4.17:14.5:1
#000000
#6B6F78
Fail
a Mexico, Central Amer…3.22:14.5:1
#000000
#585E68
Fail
a North America2.05:14.5:1
#000000
#3A414F
Fail
a Oceania2.26:14.5:1
#000000
#3D4856
Fail
a South America1.74:14.5:1
#000000
#2B3747
Fail
a West and Central Afr…1.37:14.5:1
#000000
#182637
Fail
a West Asia1.08:14.5:1
#000000
#040D18
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
Landmark Structure
22 landmarks
PASS
22 landmarks
Info::
<main> landmark present
Info::
18 <nav> landmark(s) found
Warning::
3 of 18 <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

A+
Print Stylesheet
Print styles detected
PASS
Print styles detected
Info::
External print stylesheet detected
Got: /sites/default/files/css/css_CopJ4JgM9EQmeziaa1hxzMDBq6Wq627JrDcxolzguuU.css?delta=2&language=en&theme=iucn_revamp&include=eJx9kIFqwzAMRH_Ijj_JOPYlNbUtI8lJ8_dLM-jKOgZCiKdDOm4O8e6Vzupu_pm94qFmJlJRDt3PgTmTS0x9HqrUPncLcf2ka6E5FCt6lNxWE4nhItVODU1lyiM2z9hC7dYuCDoYyUdqeq7_V9_AdH5pDfwtTDx6KNObx0uPR9ZOfXT3mqxEzl3N273fRu8lMLmrmxIOGupTlkgb-HCnnUjFCAqiZmpeboHB7gXsBZKR0cFLlpvLLauRQxT1zFlgFFzP3wsYLcIrA-4P5qOI2TJ2cVefKqVRYHb4ijVUtHElP-2wT2CfxC58JZi-AMhhvSE
Print Stylesheet ✓ Print Optimized
Print stylesheet /sites/default/files/css/css_CopJ4JgM9EQmeziaa1hxzMDBq6Wq627JrDcxolzguuU.css?delta=2&language=en&theme=iucn_revamp&include=eJx9kIFqwzAMRH_Ijj_JOPYlNbUtI8lJ8_dLM-jKOgZCiKdDOm4O8e6Vzupu_pm94qFmJlJRDt3PgTmTS0x9HqrUPncLcf2ka6E5FCt6lNxWE4nhItVODU1lyiM2z9hC7dYuCDoYyUdqeq7_V9_AdH5pDfwtTDx6KNObx0uPR9ZOfXT3mqxEzl3N273fRu8lMLmrmxIOGupTlkgb-HCnnUjFCAqiZmpeboHB7gXsBZKR0cFLlpvLLauRQxT1zFlgFFzP3wsYLcIrA-4P5qOI2TJ2cVefKqVRYHb4ijVUtHElP-2wT2CfxC58JZi-AMhhvSE ✓Inline @media print Not detected ✗
A+
Lighthouse Accessibility Audits
Score 98/100 — 1 failing, 29 passed
PASS
98

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.

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
Heading Our Members div.brick > div.wrapper-content > div.wrapper-body > h3.highlighted

These are opportunities to improve keyboard navigation in your application.

○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
●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
●Background and foreground colors have a sufficient contrast ratio
●Document has a `<title>` element
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●Links have a discernible name
●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
●Skip links are focusable.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●`<video>` elements contain a `<track>` element with `[kind="captions"]`
●All heading elements contain content.
●Identical links have the same purpose.
○`[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
○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.
○Tables have different content in the summary attribute and `<caption>`.
○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