Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

7 PASS 2 REVIEW 4 FIX

Favicon & Branding

Action

1 icon(s) detected

FIX

1 icon(s) detected

No favicon.ico at site root

Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.

HTML icon links detected

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

Web Manifest

Action

Not found

FIX

Not found

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.

Dark Mode Support

Action

No dark mode signals

FIX

No dark mode signals

No dark mode signals detected

Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.

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.

Print Stylesheet

Action

No print styles

FIX

No print styles

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 ✗

Navigation UX

Action

2 navigation pattern(s)

REVIEW

2 navigation pattern(s)

Search functionality detected

Got: role-search

Skip navigation link detected

1 navigation landmark(s) detected

Hamburger menu detected (responsive design)

Breadcrumbs

Search role='search' landmark

Skip Link Skip link detected

Labeled Navigation 1 <nav> element(s)

Hamburger Menu

Sticky Navigation Cannot reliably detect (CSS-based)

4 of 6 testable patterns navigation patterns detected. Strong navigation UX with multiple discovery paths.

Color Contrast (Screenshot)

Action

20 text elements analyzed, 13 fail WCAG AA

REVIEW

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

7 pass 13 fail WCAG AA

span United Nations University

2.64:1

#000000

#1C5A55

needs 4.5:1 (normal text)

16px · top of page (header area)

a Projects

2.64:1

#000000

#1C5A55

needs 4.5:1 (normal text)

16px · top of page (header area)

a Experts

2.64:1

#000000

#1C5A55

needs 4.5:1 (normal text)

16px · above the fold

a Careers

2.64:1

#000000

#1C5A55

needs 4.5:1 (normal text)

16px · above the fold

a Our World

2.64:1

#000000

#1C5A55

needs 4.5:1 (normal text)

16px · above the fold

a 日本語

2.64:1

#000000

#1C5A55

needs 4.5:1 (normal text)

16px · above the fold

a Institutes

2.64:1

#000000

#1C5A55

needs 4.5:1 (normal text)

16px · above the fold

a Topics

2.64:1

#000000

#1C5A55

needs 4.5:1 (normal text)

16px · above the fold

a Publications

3.96:1

#000000

#347762

needs 4.5:1 (normal text)

16px · above the fold · over background image/gradient

a News

2.82:1

#000000

#365F25

needs 4.5:1 (normal text)

16px · above the fold

a Events

2.82:1

#000000

#365F25

needs 4.5:1 (normal text)

16px · above the fold

a Learning

2.82:1

#000000

#365F25

needs 4.5:1 (normal text)

16px · mid-page

a About

2.82:1

#000000

#365F25

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)

Element	Ratio	Required	FG	BG	Result
h1 Evidence-based Solut…	4.50:1	3.0:1	#000000	#0779BF	Pass
h2 UNU Events Mailing L…	4.50:1	3.0:1	#000000	#0779BF	Pass
h2 We use cookies on th…	4.50:1	3.0:1	#000000	#0779BF	Pass
h3 Expert Insights	4.50:1	3.0:1	#000000	#0779BF	Pass
h3 New Publications	4.50:1	3.0:1	#000000	#0779BF	Pass
title UNU \| United Nations…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Skip to main content	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span United Nations Unive…	2.64:1	4.5:1	#000000	#1C5A55	Fail
a Projects	2.64:1	4.5:1	#000000	#1C5A55	Fail
a Experts	2.64:1	4.5:1	#000000	#1C5A55	Fail
a Careers	2.64:1	4.5:1	#000000	#1C5A55	Fail
a Our World	2.64:1	4.5:1	#000000	#1C5A55	Fail
a 日本語	2.64:1	4.5:1	#000000	#1C5A55	Fail
a Institutes	2.64:1	4.5:1	#000000	#1C5A55	Fail
a Topics	2.64:1	4.5:1	#000000	#1C5A55	Fail
a Publications	3.96:1	4.5:1	#000000	#347762	Fail
a News	2.82:1	4.5:1	#000000	#365F25	Fail
a Events	2.82:1	4.5:1	#000000	#365F25	Fail
a Learning	2.82:1	4.5:1	#000000	#365F25	Fail
a About	2.82:1	4.5:1	#000000	#365F25	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

7 landmarks

PASS

7 landmarks

<main> landmark present

1 <nav> landmark(s) found

Skip navigation link present

Search landmark present

Page Structure — as a screen reader sees it

Heading Hierarchy

21 headings, 1 skip(s)

PASS

21 headings, 1 skip(s)

Single H1 present

Heading level skipped: H1 → H3 (missing H2)

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

H1 Evidence-based Solutions for a Sustainable Future
H3 Expert Insights skipped
H3 Learning Matters: Navigating the First Funding Cycle for Responding to Loss and Damage
H3 Can Deep Learning Predict War, and Should It?
H3 Digital Maturity and Sustainability: An Interview with Dr. Jaimee Stuart
H3 News
H3 House of No Waste Announces Winners of Global Ideas Competition and Launches Online Exhibition
H3 UNU-EHS and Eurac Research Renew Partnership for GLOMOS Programme (2027–2036)
H3 UNU Paris at ChangeNOW 2026: Collective Solutions for Global Challenges
H3 Event Explores Links Between Culture, Nature and Recovery in Noto Peninsula
H3 Events
H3 Turning the Tide, Restoring Balance: Practical Action on Super Climate Pollutants
H3 Documentary Film Screening: Astropolitics
H3 Communicating Science-Based Public Policies: Challenges in the Digital Age
H2 UNU Events Mailing List
H3 New Publications
H3 Moving from Crisis Management to Resource Mobilization in the UN80 Process
H3 ClimateTech in Focus: Artificial Intelligence for Sustainability
H3 Unlocking AI’s Potential to Serve Humanity: Robotics, Geospatial AI and Communications Networks
H4 UNU INSIGHTS Newsletter
H2 We use cookies on this site to enhance your user experience

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

A+

Alt Text Quality

All 13 images OK

PASS

All 13 images OK

1 image(s) with alt text over 125 characters

3 decorative image(s) correctly marked

9 image(s) with good alt text

13 images 9 good alt text 3 decorative

Issue	Count
too long	1 image(s)

A+

Form Accessibility

All 2 controls labeled

PASS

All 2 controls labeled

2 control(s) properly labeled

2 controls

2 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
#header-search-input	search	Search all content	for/id
#sticky-header-search-input	search	Search all content	for/id

A+

Link & Button Quality

83 links, 14 buttons — all OK

PASS

83 links, 14 buttons — all OK

83 link(s) with descriptive text

83 links

0 empty

0 generic text

0 new tab

0 empty buttons

All links and buttons have descriptive accessible text.

97 links and buttons have descriptive text

404 Error Page

HTTP 404, custom page

PASS

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

Navigation links present on 404 page

Homepage link present on 404 page

Search form present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title 404 | United Nations University ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✓

Lighthouse Accessibility Audits

Score 94/100 — 2 failing, 23 passed

PASS

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
Sign up to stay informed about in-person and online events at UNU Headquarters. `div.c-call-to-action__container > div.c-call-to-action__inner > div.c-call-to-action__content > div.c-call-to-action__excerpt`
SUBSCRIBE `div.c-call-to-action__inner > div.c-call-to-action__content > a.o-button > span.o-button__text`

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
Expert Insights `article > div > div.c-cards > h3.c-cards__title`

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.

●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 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.

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Elements with visible text labels have matching accessible names.

○`[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

○`<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.

○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.

○Identical links have the same purpose.

○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.