Skip to content
https://weforum.org

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
54
GRADE
F
FIX
5
REVIEW
5
PASS
3
INFO
0
Checks
13
3 PASS 5 REVIEW 5 FIX
F
404 Error Page
Action
HTTP 403, bare page
FIX
HTTP 403, bare page
Warning::
Unexpected status code: HTTP 403
Expected HTTP 404 but received 403. This may confuse search engine crawlers.
Got: HTTP 403
Warning::
Bare server default 404 page
The 404 page has no custom styling. Users hitting a broken link see a generic error with no way to navigate back. Add a custom 404 page with your site navigation and a search bar.
404 Page Quality Default 404 Page
Status Code HTTP 403 ✗Page Title Access Denied ✓Custom Styling ✗Navigation ✗Homepage Link ✗Search Form ✗
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
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: #035b9c
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.

F
Navigation UX
Action
No navigation patterns
FIX
No navigation patterns
Info::
1 navigation landmark(s) detected
Info::
No breadcrumbs, search, or skip link detected
These navigation aids help users orient themselves and find content efficiently, especially on large sites.
Breadcrumbs
Search
Skip Link
Labeled Navigation 1 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
1 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
C
Landmark Structure
Action
27 landmarks
REVIEW
27 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
Warning::
Skip navigation link is missing (WCAG 2.4.1)
Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.
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

Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.

Why this matters

Without a skip-nav link, keyboard users tab through every nav item before reaching content — every page, every visit.

Learn more ▾

WCAG 2.4.1 (Bypass Blocks) requires a mechanism to skip past repeated content. The standard implementation is a 'Skip to main content' link that's the first focusable element, visually hidden until focused. Three lines of HTML + four of CSS.

Source: WCAG 2.1 SC 2.4.1

C
Form Accessibility
Action
4 of 9 controls have issues
REVIEW
4 of 9 controls have issues
Critical::
4 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="checkbox" id="CybotCookiebotDialogBodyLevelButtonNecessaryInline">; <input type="checkbox" id="CybotCookiebotDialogBodyLevelButtonPreferencesInline">; <input type="checkbox" id="CybotCookiebotDialogBodyLevelButtonStatisticsInline">; <input type="checkbox" id="CybotCookiebotDialogBodyLevelButtonMarketingInline">
Info::
5 control(s) properly labeled
9 controls
5 labeled
0 placeholder only
4 unlabeled
ControlTypeLabelMethod
#CybotCookiebotDialogBodyLevelButtonNecessarycheckboxNecessaryfor/id
#CybotCookiebotDialogBodyLevelButtonPreferencescheckboxPreferencesfor/id
#CybotCookiebotDialogBodyLevelButtonStatisticscheckboxPerformancefor/id
#CybotCookiebotDialogBodyLevelButtonMarketingcheckboxMarketingfor/id
#CybotCookiebotDialogBodyContentCheckboxPersonalInformationcheckboxDo not sell or share my personal informationfor/id
#CybotCookiebotDialogBodyLevelButtonPreferencesInlinecheckbox(none)none
#CybotCookiebotDialogBodyLevelButtonStatisticsInlinecheckbox(none)none
#CybotCookiebotDialogBodyLevelButtonMarketingInlinecheckbox(none)none
#CybotCookiebotDialogBodyLevelButtonNecessaryInlinecheckbox(none)none

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

<input type="checkbox" id="CybotCookiebotDialogBodyLevelButtonNecessaryInline">; <input type="checkbox" id="CybotCookiebotDialogBodyLevelButtonPreferencesInline">; <input type="checkbox" id="CybotCookiebotDialogBodyLevelButtonStatisticsInline">; <input type="checkbox" id="CybotCookiebotDialogBodyLevelButtonMarketingInline">

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
Favicon & Branding
Action
4 icon(s) detected
REVIEW
4 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, 20 fail WCAG AA
REVIEW

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

0 pass 20 fail WCAG AA
h1 Connecting leaders to make sense of glob…
2.63:1
#000000
on
#00509D
needs 3.0:1 (large text)
32px · bottom of viewport
h2 How we drive impact
2.63:1
#000000
on
#00509D
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Spotlight
2.63:1
#000000
on
#00509D
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Latest analysis on war in the Middle Eas…
2.63:1
#000000
on
#00509D
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Discover
2.63:1
#000000
on
#00509D
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Forum Stories
2.63:1
#000000
on
#00509D
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Forum in the news
2.63:1
#000000
on
#00509D
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Forum’s digital initiatives
2.63:1
#000000
on
#00509D
needs 3.0:1 (large text)
24px · bottom of viewport
h3 We tackle global challenges through our …
2.63:1
#000000
on
#00509D
needs 3.0:1 (large text)
19px · bottom of viewport
h3 We tackle global challenges through our …
2.63:1
#000000
on
#00509D
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Energy Transition
2.63:1
#000000
on
#00509D
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Manufacturing and Value Chains
2.63:1
#000000
on
#00509D
needs 3.0:1 (large text)
19px · bottom of viewport
title The World Economic Forum
2.09:1
#000000
on
#00427F
needs 4.5:1 (normal text)
16px · top of page (header area)
a Consent
2.14:1
#000000
on
#004481
needs 4.5:1 (normal text)
16px · top of page (header area)
a Details
2.24:1
#000000
on
#004785
needs 4.5:1 (normal text)
16px · top of page (header area)
a [#IABV2SETTINGS#]
2.30:1
#000000
on
#01488A
needs 4.5:1 (normal text)
16px · top of page (header area)
a About
2.38:1
#000000
on
#004A8F
needs 4.5:1 (normal text)
16px · above the fold
div This website uses cookies
2.48:1
#000000
on
#004D93
needs 4.5:1 (normal text)
16px · above the fold
div The World Economic Forum uses necessary …
2.57:1
#000000
on
#004F98
needs 4.5:1 (normal text)
16px · above the fold
div [#GPC_BANNER_ICON#]
2.69:1
#000000
on
#00529D
needs 4.5:1 (normal text)
16px · above the fold
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Connecting leaders t…2.63:13.0:1
#000000
#00509D
Fail
h2 How we drive impact2.63:13.0:1
#000000
#00509D
Fail
h2 Spotlight2.63:13.0:1
#000000
#00509D
Fail
h2 Latest analysis on w…2.63:13.0:1
#000000
#00509D
Fail
h2 Discover2.63:13.0:1
#000000
#00509D
Fail
h2 Forum Stories2.63:13.0:1
#000000
#00509D
Fail
h2 Forum in the news2.63:13.0:1
#000000
#00509D
Fail
h2 Forum’s digital in…2.63:13.0:1
#000000
#00509D
Fail
h3 We tackle global cha…2.63:13.0:1
#000000
#00509D
Fail
h3 We tackle global cha…2.63:13.0:1
#000000
#00509D
Fail
h3 Energy Transition2.63:13.0:1
#000000
#00509D
Fail
h3 Manufacturing and Va…2.63:13.0:1
#000000
#00509D
Fail
title The World Economic F…2.09:14.5:1
#000000
#00427F
Fail
a Consent2.14:14.5:1
#000000
#004481
Fail
a Details2.24:14.5:1
#000000
#004785
Fail
a [#IABV2SETTINGS#]2.30:14.5:1
#000000
#01488A
Fail
a About2.38:14.5:1
#000000
#004A8F
Fail
div This website uses co…2.48:14.5:1
#000000
#004D93
Fail
div The World Economic F…2.57:14.5:1
#000000
#004F98
Fail
div [#GPC_BANNER_ICON#]2.69:14.5:1
#000000
#00529D
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 87/100 — 3 failing, 27 passed
REVIEW
87

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
Sign in div#global-nav_root > div#global-nav_display > navbar > div#navbar_container

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.

Names and labels

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.wef-1l63pvi > div.wef-1wmycnq > div.wef-1l9nceh > button.chakra-button div.wef-1l63pvi > div.wef-1wmycnq > div.wef-1l9nceh > button.chakra-button

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
Join us div#navbar_right-panel > public-bar-panel > div#public_right-panel_container > a.public-bar-panel__link
article.wef-ahbhn4 > div.wef-xnqvtg > div.wef-1qbpo0l > a.chakra-link article.wef-ahbhn4 > div.wef-xnqvtg > div.wef-1qbpo0l > a.chakra-link
article.wef-ahbhn4 > div.wef-xnqvtg > div.wef-1qbpo0l > a.chakra-link article.wef-ahbhn4 > div.wef-xnqvtg > div.wef-1qbpo0l > a.chakra-link
div.wef-70qvj9 > div.wef-3eu5vo > div.wef-0 > a.chakra-link div.wef-70qvj9 > div.wef-3eu5vo > div.wef-0 > a.chakra-link
div.wef-70qvj9 > div.wef-3eu5vo > div.wef-0 > a.chakra-link div.wef-70qvj9 > div.wef-3eu5vo > div.wef-0 > a.chakra-link
div.wef-70qvj9 > div.wef-3eu5vo > div.wef-0 > a.chakra-link div.wef-70qvj9 > div.wef-3eu5vo > div.wef-0 > a.chakra-link
article.wef-lv2neg > div.wef-xnqvtg > div.wef-1qbpo0l > a.chakra-link article.wef-lv2neg > div.wef-xnqvtg > div.wef-1qbpo0l > a.chakra-link
article.wef-lv2neg > div.wef-xnqvtg > div.wef-1qbpo0l > a.chakra-link article.wef-lv2neg > div.wef-xnqvtg > div.wef-1qbpo0l > a.chakra-link

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.

○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]`s are contained by their required parent element
●`[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
●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
●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
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Deprecated ARIA roles were not used
●`<video>` elements contain a `<track>` element with `[kind="captions"]`
●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 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.
○Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
○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.
○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+
Heading Hierarchy
23 headings
PASS
23 headings
Info::
Single H1 present
  • H1 Connecting leaders to make sense of global challenges and move the world forward together
  • H2 How we drive impact
  • H3 We tackle global challenges through our 11 Centres
  • H3 We tackle global challenges through our 11 Centres
  • H4 Centre for Advanced Manufacturing and Supply Chains
  • H4 Centre for AI Excellence
  • H4 Centre for Cybersecurity
  • H4 Centre for Energy and Materials
  • H4 Centre for Financial and Monetary Systems
  • H4 Centre for Health and Healthcare
  • H4 Centre for Nature and Climate
  • H4 Centre for Regions, Trade and Geopolitics
  • H4 Centre for the New Economy and Society
  • H4 Centre for Urban Transformation
  • H4 Centre for Frontier Technologies and Innovation
  • H2 Spotlight
  • H2 Latest analysis on war in the Middle East
  • H2 Discover
  • H3 Energy Transition
  • H3 Manufacturing and Value Chains
  • H2 Forum Stories newsletter
  • H2 Forum in the news
  • H2 Forum’s digital initiatives
A+
Alt Text Quality
1 of 98 images have issues
PASS
1 of 98 images have issues
Warning::
1 image(s) with generic alt text
Info::
29 decorative image(s) correctly marked
Info::
68 image(s) with good alt text
98 images 68 good alt text 29 decorative 1 generic
IssueCount
generic1 image(s)
A+
Print Stylesheet
Print styles detected
PASS
Print styles detected
Info::
External print stylesheet detected
Got: /assets/print-f370127a3bbad053fa295c4ba298deef01b5103a0a1be66e8a0556e8cfbd76e0.css
Print Stylesheet ✓ Print Optimized
Print stylesheet /assets/print-f370127a3bbad053fa295c4ba298deef01b5103a0a1be66e8a0556e8cfbd76e0.css ✓Inline @media print Not detected ✗
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback