Skip to content
https://who.int

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
77
GRADE
C
FIX
2
REVIEW
5
PASS
6
INFO
0
Checks
13
6 PASS 5 REVIEW 2 FIX
D
Dark Mode Support
Action
Theme color only
FIX
Theme color only
Info::
Theme-color present but no dark variant
A theme-color is set but no dark-specific variant was found. The browser toolbar may not adapt for dark mode users.
Got: #007eb4
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 ModePartial Dark Mode
color-scheme meta Not set ✗Dark theme-color Not set ✗CSS indicators Not detected ✗

Detection limited to meta tags and inline styles.

D
Navigation UX
Action
2 navigation pattern(s)
FIX
2 navigation pattern(s)
Info::
Search functionality detected
Got: role-search
Info::
Skip navigation link detected
Info::
28 navigation landmark(s) detected
Breadcrumbs
Search role='search' landmark
Skip Link Skip link detected
Labeled Navigation 28 <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.
C
Landmark Structure
Action
31 landmarks
REVIEW
31 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Info::
28 <nav> landmark(s) found
Warning::
26 of 28 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
Info::
Skip navigation link present
Info::
Search landmark present
Page Structure — as a screen reader sees it
BANNER header NAV "Regions" SEARCH 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

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

B
Heading Hierarchy
38 headings
REVIEW
38 headings
Info::
Single H1 present
Warning::
5 empty heading(s)
Empty headings appear in the document outline but provide no information.
  • H1 Ensuring access to safe, effective and quality-assured health products
  • H2 Latest news
  • H2 Latest on emergencies
  • H3 Conflict in the Middle East
  • H3 (empty)
  • H3 Read about the health situation
  • H3 Investigations into illness in Burundi
  • H3 (empty)
  • H3 (empty)
  • H3 Read more
  • H3 Meningitis
  • H3 Read our fact sheet
  • H3 COVID-19
  • H3 (empty)
  • H3 See the latest data
  • H2 Highlights
  • H3 WHO Pandemic Agreement
  • H3 Learn more
  • H3 Chagas disease
  • H3 Read our fact sheet
  • H3 Prequalification of health products
  • H3 (empty)
  • H3 Read our fact sheet
  • H3 Global health architecture
  • H3 Provide your input
  • H2 Invest in WHO
  • H3 Read more
  • H2 Publications
  • H3 Find a publication
  • H2 Videos
  • H3 Let's unpack menopause
  • H2 Speeches
  • H3 Read WHO Director-General's speeches
  • H2 Campaigns
  • H3 World Immunization Week
  • H3 World Malaria Day
  • H3 World Hand Hygiene Day
  • H2 Events

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
Form Accessibility
2 of 3 controls have issues
REVIEW
2 of 3 controls have issues
Critical::
1 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <select name="language-selector">
Warning::
1 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="search" id="e83da4ab-e9d9-48d0-80a5-3289055f430b">
Info::
1 control(s) properly labeled
3 controls
1 labeled
1 placeholder only
1 unlabeled
ControlTypeLabelMethod
#language-selectorselectSelect languagefor/id
#e83da4ab-e9d9-48d0-80a5-3289055f430bsearch(Search)placeholder only
language-selectorselect(none)none

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

<select name="language-selector">

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

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

<input type="search" id="e83da4ab-e9d9-48d0-80a5-3289055f430b">

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
Favicon & Branding
17 icon(s) detected
REVIEW
17 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
Multiple icon sizes detected
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✓ Manifest Icons Present
✓ Multiple Sizes Present
A
Alt Text Quality
All 29 images OK
PASS
All 29 images OK
Info::
3 image(s) with alt text over 125 characters
Info::
1 decorative image(s) correctly marked
Info::
25 image(s) with good alt text
29 images 25 good alt text 1 decorative
IssueCount
too long3 image(s)
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 404 ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✓
A+
Web Manifest
PWA-ready
PASS
PWA-ready
Info::
Meets PWA install criteria
Info::
Name present: World Health Organization
Info::
192x192 icon present
Info::
512x512 icon present
Info::
Display mode: minimal-ui
PWA Install Criteria ✓ Installable
Name World Health Organization ✓192×192 icon ✓512×512 icon ✓Start URL / ✓Display Mode minimal-ui ✓
Name World Health Organization Display Mode minimal-ui Theme Color #00205c Background Color #ffffff Icons 14 icon(s)
A+
Print Stylesheet
Print styles detected
PASS
Print styles detected
Info::
External print stylesheet detected
Got: /ResourcePackages/WHO/assets/dist/styles/print.min.css?v=14.0.7729.20343
Print Stylesheet ✓ Print Optimized
Print stylesheet /ResourcePackages/WHO/assets/dist/styles/print.min.css?v=14.0.7729.20343 ✓Inline @media print Not detected ✗
A+
Color Contrast (Screenshot)
20 text elements analyzed, 0 fail WCAG AA
PASS

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

20 pass
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 Latest news21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Latest on emergencie…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Highlights21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Invest in WHO21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Publications21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Videos21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Speeches21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Campaigns21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Events21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Conflict in the Midd…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Read about the healt…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Investigations into …21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Read more21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Meningitis21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Read our fact sheet21.00:13.0:1
#000000
#FFFFFF
Pass
h3 See the latest data21.00:13.0:1
#000000
#FFFFFF
Pass
h3 WHO Pandemic Agreeme…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Learn more21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Chagas disease21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Read our fact sheet21.00:13.0:1
#000000
#FFFFFF
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.

A+
Lighthouse Accessibility Audits
Score 96/100 — 2 failing, 27 passed
PASS
96

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.

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.row > div.sf_colsIn > div.slicknav_menu > a.slicknav_btn div.row > div.sf_colsIn > div.slicknav_menu > a.slicknav_btn

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.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
14 April 2026 News release After three years of conflict, Sudan faces a deeper… div#PageContent_C510_Col00 > div.list-view > div.list-view--item > a.link-container
9 April 2026 News release First-ever WHO Forum unites 800+ Collaborating Centr… div#PageContent_C510_Col00 > div.list-view > div.list-view--item > a.link-container
7 April 2026 News release WHO and France shift One Health vision to action wit… div#PageContent_C510_Col00 > div.list-view > div.list-view--item > a.link-container
6 April 2026 News release WHO calls for action: “Together for health. Stand wi… div#PageContent_C510_Col00 > div.list-view > div.list-view--item > a.link-container
82nd INN Consultation 21 – 24 April 2026 div#PageContent_C633_Col01 > div.list-view > div.list-view--item > a.link-container
INN Session with INN stakeholders 21 April 2026 09:00 – 10:30 UTC Time div#PageContent_C633_Col01 > div.list-view > div.list-view--item > a.link-container
The role of the health sector in supporting parents and their caregiving potent… div#PageContent_C633_Col01 > div.list-view > div.list-view--item > a.link-container
World Immunization Week World Immunization Week 2026: For every generation, va… div#PageContent_C633_Col01 > div.list-view > div.list-view--item > a.link-container
2026 World Malaria Day 2026 - Driven to End Malaria: Now We Can. Now We Must. … div#PageContent_C633_Col01 > div.list-view > div.list-view--item > a.link-container
○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
●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
●`[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
●`<frame>` or `<iframe>` elements have a title
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●Links are distinguishable without relying on color.
●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.
●Heading elements appear in a sequentially-descending order
●Skip links are focusable.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●All heading elements contain content.
●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 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
○Buttons have an accessible name
○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
○Form elements have associated labels
○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.
○`[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>`.
○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.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback