Skip to content
https://itu.int

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
57
GRADE
D
FIX
6
REVIEW
4
PASS
3
INFO
0
Checks
13
3 PASS 4 REVIEW 6 FIX
D
Landmark Structure
Action
No landmarks
FIX
No landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Warning::
No <nav> landmark found
Info::
No banner (header) landmark
Info::
No contentinfo (footer) landmark
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.

No landmarks detected

Screen reader users have no way to navigate by region.

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

F
404 Error Page
Action
HTTP 404, bare page
FIX
HTTP 404, bare page
Info::
Correct 404 status code returned
Got: HTTP 404
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 404 ✓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
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 ✗
F
Navigation UX
Action
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Back-to-top link 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
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.
B
Favicon & Branding
5 icon(s) detected
REVIEW
5 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 Missing
✓ Multiple Sizes Present
B
Dark Mode Support
Dark mode detected
REVIEW
Dark mode detected
Info::
prefers-color-scheme CSS detected in inline styles
Info::
Detection limited to meta tags and inline styles
External CSS files may contain prefers-color-scheme rules not visible to this scan.
Dark Mode✓ Dark Mode Supported
color-scheme meta Not set ✗Dark theme-color Not set ✗CSS indicators Detected ✓

Detection limited to meta tags and inline styles.

C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 1 fail WCAG AA
REVIEW

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

19 pass 1 fail WCAG AA
a Español
2.21:1
#000000
on
#134779
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient

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
h1 Connecting the world…20.65:13.0:1
#000000
#FDFDFD
Pass
h1 Advancing the spirit…20.65:13.0:1
#000000
#FDFDFD
Pass
h1 Artemis II: Spectrum…20.65:13.0:1
#000000
#FDFDFD
Pass
h1 Coming up: Internati…20.65:13.0:1
#000000
#FDFDFD
Pass
h1 World Telecommunicat…20.65:13.0:1
#000000
#FDFDFD
Pass
h2 Connecting the world…18.56:13.0:1
#000000
#EFF1F4
Pass
h2 News and views20.65:13.0:1
#000000
#FDFDFD
Pass
h2 ​20.65:13.0:1
#000000
#FDFDFD
Pass
h2 ​20.65:13.0:1
#000000
#FDFDFD
Pass
h2 In depth​​​20.65:13.0:1
#000000
#FDFDFD
Pass
h2 DIGITAL LIFELINES20.65:13.0:1
#000000
#FDFDFD
Pass
h2 WTPF-2620.65:13.0:1
#000000
#FDFDFD
Pass
h2 PLENIPOTENTIARY CONF…20.65:13.0:1
#000000
#FDFDFD
Pass
h2 About ITU20.65:13.0:1
#000000
#FDFDFD
Pass
h2 Governance20.65:13.0:1
#000000
#FDFDFD
Pass
h2 Events20.65:13.0:1
#000000
#FDFDFD
Pass
title ITU: Connecting the …20.41:14.5:1
#000000
#FAFCFD
Pass
a عربي20.41:14.5:1
#000000
#FAFCFD
Pass
a 中文21.00:14.5:1
#000000
#FFFFFF
Pass
a Español2.21:14.5:1
#000000
#134779
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 89/100 — 4 failing, 26 passed
REVIEW
89

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
Handbook: Amateur and amateur-satellite services​​ dt.flexviewerMainDivDT-newsviews > div.flexviewerMainDivDT-textarea-newsviews > p > a
 Action, progress and impact in digital development​​​ dt.flexviewerMainDivDT-newsviews > div.flexviewerMainDivDT-textarea-newsviews > p > a
From Digital skills to growth: Women-led SMEs in Nigeria​​​ dt.flexviewerMainDivDT-newsviews > div.flexviewerMainDivDT-textarea-newsviews > p > a
Facts and Figures 2025​​​ dt.flexviewerMainDivDT-indepth > div.flexviewerMainDivDT-textarea-indepth > p > a
Latest AI for Good publications​ dt.flexviewerMainDivDT-indepth > div.flexviewerMainDivDT-textarea-indepth > p > a
ITU Journal: Enhanced underwater communications​ dt.flexviewerMainDivDT-indepth > div.flexviewerMainDivDT-textarea-indepth > p > a
Feedback div.css-sfbnep > div.css-112xj8j > button#hj-survey-toggle-1 > span.css-1qk2dqd

These are opportunities to improve the legibility of your content.

Tables and lists

When definition lists are not properly marked up, screen readers may produce confusing or inaccurate output. Learn how to structure definition lists correctly.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
​Handbook: Amateur and amateur-satellite services​​ div#WebPartctl00_SPWebPartManager1_g_ad916b9a_709b_40d9_a89e_b35f4cc90486 > div#ctl00_SPWebPartManager1_g_ad916b9a_709b_40d9_a89e_b35f4cc90486 > div.flexviewerMainDiv-newsviews > dl.flexviewerMainDivDL-newsviews
​ Action, progress and impact in digital development​​​ div#WebPartctl00_SPWebPartManager1_g_ad916b9a_709b_40d9_a89e_b35f4cc90486 > div#ctl00_SPWebPartManager1_g_ad916b9a_709b_40d9_a89e_b35f4cc90486 > div.flexviewerMainDiv-newsviews > dl.flexviewerMainDivDL-newsviews
​From Digital skills to growth: Women-led SMEs in Nigeria​​​ div#WebPartctl00_SPWebPartManager1_g_ad916b9a_709b_40d9_a89e_b35f4cc90486 > div#ctl00_SPWebPartManager1_g_ad916b9a_709b_40d9_a89e_b35f4cc90486 > div.flexviewerMainDiv-newsviews > dl.flexviewerMainDivDL-newsviews
Facts and Figures 2025​​​ div#WebPartctl00_SPWebPartManager1_g_fbb63ac0_ea34_4c3a_bc78_75ae515494ed > div#ctl00_SPWebPartManager1_g_fbb63ac0_ea34_4c3a_bc78_75ae515494ed > div.flexviewerMainDiv-indepth > dl.flexviewerMainDivDL-indepth
​​Latest AI for Good publications​ div#WebPartctl00_SPWebPartManager1_g_fbb63ac0_ea34_4c3a_bc78_75ae515494ed > div#ctl00_SPWebPartManager1_g_fbb63ac0_ea34_4c3a_bc78_75ae515494ed > div.flexviewerMainDiv-indepth > dl.flexviewerMainDivDL-indepth
​​​​ITU Journal: Enhanced underwater communications​​​ ​ div#WebPartctl00_SPWebPartManager1_g_fbb63ac0_ea34_4c3a_bc78_75ae515494ed > div#ctl00_SPWebPartManager1_g_fbb63ac0_ea34_4c3a_bc78_75ae515494ed > div.flexviewerMainDiv-indepth > dl.flexviewerMainDivDL-indepth

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Facts and Figures 2025​​​ dt.flexviewerMainDivDT-indepth > div.flexviewerMainDivDT-textarea-indepth > p > a

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html html

These items highlight common accessibility best practices.

○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
●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
●Definition list items are wrapped in `<dl>` elements
●Document has a `<title>` element
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●Links are distinguishable without relying on color.
●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
●Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
●`[lang]` attributes have a valid value
●Heading elements appear in a sequentially-descending order
●Deprecated ARIA roles were not used
●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 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
○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
○The document does not use `<meta http-equiv="refresh">`
○`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
○`<object>` elements have alternate text
○Select elements have associated label elements.
○Skip links are focusable.
○No element has a `[tabindex]` value greater than 0
○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
○`<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.
○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
14 headings
PASS
14 headings
Warning::
Multiple H1 headings (5 found)
A page should have only one H1. Multiple H1s dilute the document outline.
  • H2 Connecting the world and beyond
  • H1 Connecting the world and beyond
  • H1 Advancing the spirit of amateur radio duplicate H1
  • H1 Artemis II: Spectrum and ITU coding duplicate H1
  • H1 Coming up: International Girls in ICT Day duplicate H1
  • H1 World Telecommunication/ICT Policy Forum duplicate H1
  • H2 News and views​​
  • H2 In depth​​​
  • H2 DIGITAL LIFELINES
  • H2 WTPF-26
  • H2 PLENIPOTENTIARY CONFERENCE
  • H2 About ITU
  • H2 Governance
  • H2 Events

A page should have only one H1. Multiple H1s dilute the document outline.

Why this matters

Multiple H1s blur the page's primary topic — screen-reader users and Google both prefer one H1.

Learn more ▾

HTML5's outline algorithm technically allows multiple H1s within sectioning content, but no browser implements it. In practice: one H1 per page. Use H2-H6 for subsections.

Source: WCAG 2.4.6 / Google Search Central

A
Alt Text Quality
1 of 30 images have issues
PASS
1 of 30 images have issues
Critical::
1 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Info::
4 decorative image(s) correctly marked
Info::
25 image(s) with good alt text
30 images 25 good alt text 4 decorative 1 missing
IssueCount
missing1 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

A+
Form Accessibility
All 3 controls labeled
PASS
All 3 controls labeled
Info::
3 control(s) properly labeled
3 controls
3 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
#gsc-i-id1textsearcharia-label
#a2a_copy_link_texttextCopy linkfor/id
#a2apage_findtextFind any servicefor/id
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback