Skip to content
https://unwto.org

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
62
GRADE
D
FIX
4
REVIEW
3
PASS
6
INFO
0
Checks
13
6 PASS 3 REVIEW 4 FIX
F
Favicon & Branding
Action
1 icon(s) detected
FIX
1 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::
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
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 ✗
B
Heading Hierarchy
59 headings, 1 skip(s)
REVIEW
59 headings, 1 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
1 empty heading(s)
Empty headings appear in the document outline but provide no information.
  • H1 UN Tourism Data Dashboard
  • H2 Our latest news
  • H2 Local Observatories Key to Delivering on National Tourism Strategies, New Report Concludes
  • H2 Tourism Leaders Convene on Zero Waste Day to Launch Global “Recipe of Change”
  • H2 UN Tourism strengthens tourism measurement in global economic system
  • H2 In Memoriam: Rafeeuddin Ahmed
  • H2 UN Tourism and TUI Care Foundation join hands to support Rural Artists and Artisans Across Africa
  • H2 UN Tourism opens call for Best Tourism Villages 2026
  • H2 UN Tourism launches road map towards the International Year of Sustainable and Resilient Tourism 2027
  • H2 International tourist arrivals up 4% in 2025 reflecting strong travel demand around the world
  • H2 Tourism Investment in Bulgaria: new UN Tourism Guidelines Highlight Opportunities in the Sector
  • H2 UN Tourism and International Baccalaureate Organization partner to grow tourism education at high school level
  • H2 (empty)
  • H2 UN Tourism Events & Projects
  • H4 Americas skipped
  • H3 National Strategy and Policy for Sustainable Tourism in the Dominic...
  • H4 All Regions
  • H3 Executive Council - 126th session
  • H4 Asia and the Pacific
  • H3 The 20th UN Tourism/PATA Forum on Tourism Trends and Outlook
  • H4 Africa
  • H3 The 69th UN Tourism Commission for Africa and Thematic Conference o...
  • H4 Africa
  • H3 2nd UN Tourism Regional Congress on Women Empowerment in Tourism in...
  • H4 Americas
  • H3 71st UN Tourism Regional Commission for the Americas and Workshop o...
  • H4 Africa
  • H3 TSA Technical Assistance for Cabo Verde
  • H4 Africa
  • H3 Development and Promotion of Sustainable Forms of Tourism in the Us...
  • H4 Americas
  • H3 Development and support in the implementation of the National Susta...
  • H4 Americas
  • H3 Case Study on Sustainable Urban Tourism for Medellín
  • H4 Americas
  • H3 Update of Guatemala's Sustainable Tourism Master Plan
  • H4 Asia and the Pacific
  • H3 Fujian as a World - Renowned Tourist Destination: Goals, Vision and...
  • H4 Middle East
  • H3 The Update of Hotel Classification Scheme
  • H4 Europe
  • H3 72nd Meeting of the Commission for Europe (CEU)
  • H2 International tourist arrivals up 4% in 2025 reflecting strong travel demand around the world
  • H2 New UN Tourism publications
  • H2 Innovating Undergraduate and Graduate Programmes in Tourism – A multidisciplinary approach
  • H2 Accessibility Guidelines for Tourism Businesses
  • H2 Fifty Years of Tourism
  • H2 Tourism for Rural Development Programme – Impact Report 2021–2025
  • H2 Compendium of Good Practices in Indigenous Tourism – Regional Focus on Asia and the Pacific
  • H2 World Tourism Barometer
  • H2 The Integration of Biodiversity in National Tourism Policies
  • H2 Artificial Intelligence Adoption in Tourism – Key Considerations for Sector Stakeholders
  • H2 Supporting Climate Action Planning in Tourism Destinations – A Review of Literature and Tools for Local Authorities
  • H2 Global Roadmap for Waste Reduction in the Tourism Sector
  • H2 Related sites
  • H2 Shorcuts
  • H2 Footer
  • H2 Regions
  • H2 Follow Us

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

C
Navigation UX
Action
2 navigation pattern(s)
REVIEW
2 navigation pattern(s)
Info::
Search functionality detected
Got: role-search
Info::
Skip navigation link detected
Info::
7 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Breadcrumbs
Search role='search' landmark
Skip Link Skip link detected
Labeled Navigation 7 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
4 of 6 testable patterns navigation patterns detected. Strong navigation UX with multiple discovery paths.
A
Landmark Structure
11 landmarks
PASS
11 landmarks
Info::
<main> landmark present
Info::
7 <nav> landmark(s) found
Warning::
2 of 7 <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 SEARCH 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+
Alt Text Quality
1 of 40 images have issues
PASS
1 of 40 images have issues
Warning::
1 image(s) with generic alt text
Info::
12 decorative image(s) correctly marked
Info::
27 image(s) with good alt text
40 images 27 good alt text 12 decorative 1 generic
IssueCount
generic1 image(s)
A
Form Accessibility
1 of 2 controls have issues
PASS
1 of 2 controls have issues
Critical::
1 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--3">
Info::
1 control(s) properly labeled
2 controls
1 labeled
0 placeholder only
1 unlabeled
ControlTypeLabelMethod
#edit-keys--2searchSearchfor/id
#edit-submit--3submit(none)none

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

<input type="submit" id="edit-submit--3">

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

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 Page not found | UN Tourism ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✓
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
h1 UN Tourism Data Dash…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Our latest news21.00:13.0:1
#000000
#FFFFFF
Pass
h2 UN Tourism Events & …21.00:13.0:1
#000000
#FFFFFF
Pass
h2 International touris…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 New UN Tourism publi…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Related sites21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Shorcuts21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Footer21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Regions21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Follow Us21.00:13.0:1
#000000
#FFFFFF
Pass
h3 National Strategy an…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Executive Council - …21.00:13.0:1
#000000
#FFFFFF
Pass
h3 The 20th UN Tourism/…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 The 69th UN Tourism …21.00:13.0:1
#000000
#FFFFFF
Pass
h3 2nd UN Tourism Regio…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 71st UN Tourism Regi…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 TSA Technical Assist…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Development and Prom…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Development and supp…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Case Study on Sustai…21.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 93/100 — 2 failing, 27 passed
PASS
93

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
Americas div.field__item > div#taxonomy-term-10 > a > span.term--label
Events div.block > div.b--content > div.marker-tabs > a.marker-tab

These are opportunities to improve the legibility of your content.

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#block-untourism-socialmedialinks > ul.social-media-links--platforms > li > a.is-external div#block-untourism-socialmedialinks > ul.social-media-links--platforms > li > a.is-external
div#block-untourism-socialmedialinks > ul.social-media-links--platforms > li > a.is-external div#block-untourism-socialmedialinks > ul.social-media-links--platforms > li > a.is-external
div#block-untourism-socialmedialinks > ul.social-media-links--platforms > li > a.is-external div#block-untourism-socialmedialinks > ul.social-media-links--platforms > li > a.is-external
div#block-untourism-socialmedialinks > ul.social-media-links--platforms > li > a.is-external div#block-untourism-socialmedialinks > ul.social-media-links--platforms > li > a.is-external
div#block-untourism-socialmedialinks > ul.social-media-links--platforms > li > a.is-external div#block-untourism-socialmedialinks > ul.social-media-links--platforms > li > a.is-external
div#block-untourism-socialmedialinks > ul.social-media-links--platforms > li > a.is-external div#block-untourism-socialmedialinks > ul.social-media-links--platforms > li > a.is-external

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]` 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
●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
●Elements use only permitted ARIA attributes
●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
●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.
●Elements with visible text labels have matching accessible names.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○Elements with `role="dialog"` or `role="alertdialog"` 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
○`<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
○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.
○`[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