Skip to content
https://imo.org

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
52
GRADE
F
FIX
7
REVIEW
4
PASS
2
INFO
0
Checks
13
2 PASS 4 REVIEW 7 FIX
D
Landmark Structure
Action
6 landmarks
FIX
6 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Info::
3 <nav> landmark(s) found
Warning::
3 of 3 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
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

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

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

D
404 Error Page
Action
HTTP 500, custom page
FIX
HTTP 500, custom page
Warning::
Unexpected status code: HTTP 500
Expected HTTP 404 but received 500. This may confuse search engine crawlers.
Got: HTTP 500
Info::
Custom styled 404 page
Info::
Navigation links present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 500 ✗Page Title Coming Soon ✓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
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 ✗
F
Navigation UX
Action
No navigation patterns
FIX
No navigation patterns
Info::
3 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
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 3 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
2 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
C
Heading Hierarchy
Action
31 headings, 2 skip(s)
REVIEW
31 headings, 2 skip(s)
Warning::
Multiple H1 headings (6 found)
A page should have only one H1. Multiple H1s dilute the document outline.
Warning::
Heading level skipped: H1 → H4 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H6 (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 Facilitation Committee approves digitalization strategy and cyber security measures
  • H1 IMO approves new guidelines on ship registration duplicate H1
  • H1 Hazardous cargo compensation regime moves to entry into force duplicate H1
  • H1 “Fragmented responses are no longer sufficient”: IMO Secretary-General duplicate H1
  • H1 Facilitation Committee approves digitalization strategy and cyber security measures duplicate H1
  • H1 IMO approves new guidelines on ship registration duplicate H1
  • H4 IMO At Glance skipped
  • H3 Applications open: technical assistance for passenger ship decarbonization feasibility studies
  • H3 Comoros launches National Maritime Security Committee with IMO support
  • H3 GMN project launches AI-driven fuel optimisation pilot in Mexico
  • H3 Middle East - Latest updates
  • H3 From Policy to Practice: Powering Maritime Excellence
  • H3 Supporting Seafarers: resources and general information
  • H3 PREVIEW: Marine Environment Protection Committee (MEPC 84) 27 April-1 May
  • H2 ​IMO Secretary-General Mr. Arsenio Dominguez
  • H3 Latest video
  • H2 Maritime Safety
  • H2 OUR WORK
  • H2 Marine Environment
  • H2 Maritime Safety
  • H2 OUR WORK
  • H2 CONVENTIONS
  • H2 PUBLICATIONS
  • H2 IMO Awards
  • H2 WORLD MARITIME THEME
  • H2 Day of the Seafarer
  • H2 IMO Awards
  • H2 WORLD MARITIME THEME
  • H2 RESOURCES
  • H2 IMO MEETINGS
  • H6 (empty)

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

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

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

B
Alt Text Quality
27 of 33 images have issues
REVIEW
27 of 33 images have issues
Critical::
1 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Warning::
26 image(s) with generic alt text
Info::
6 image(s) with good alt text
33 images 6 good alt text 26 generic 1 missing
IssueCount
missing1 image(s)
generic26 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

B
Favicon & Branding
4 icon(s) detected
REVIEW
4 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
Lighthouse Accessibility Audits
Score 83/100 — 6 failing, 25 passed
REVIEW
83

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

Focusable descendents within an `[aria-hidden="true"]` element prevent those interactive elements from being available to users of assistive technologies like screen readers. Learn how `aria-hidden` affects focusable elements.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
TOP STORY Facilitation Committee approves digitalization strategy and cyber sec… div#tns1-mw > div#tns1-iw > div#tns1 > div.tns-item
TOP STORY Hazardous cargo compensation regime moves to entry into force Belgiu… div#tns1-mw > div#tns1-iw > div#tns1 > div#tns1-item1
TOP STORY “Fragmented responses are no longer sufficient”: IMO Secretary-Genera… div#tns1-mw > div#tns1-iw > div#tns1 > div#tns1-item2
TOP STORY Facilitation Committee approves digitalization strategy and cyber sec… div#tns1-mw > div#tns1-iw > div#tns1 > div#tns1-item3
TOP STORY IMO approves new guidelines on ship registration IMO Legal Committee… div#tns1-mw > div#tns1-iw > div#tns1 > div.tns-item
MARITIME SAFETY FIND OUT MORE div#tns2-mw > div#tns2-iw > div#tns2 > div.entry-item
MARINE ENVIRONMENT FIND OUT MORE div#tns2-mw > div#tns2-iw > div#tns2 > div#tns2-item1
MARITIME SAFETY FIND OUT MORE div#tns2-mw > div#tns2-iw > div#tns2 > div#tns2-item2
OUR WORK FIND OUT MORE div#tns2-mw > div#tns2-iw > div#tns2 > div.entry-item
IMO AWARDS FIND OUT MORE div#tns3-mw > div#tns3-iw > div#tns3 > div.entry-item
DAY OF THE SEAFARER FIND OUT MORE div#tns3-mw > div#tns3-iw > div#tns3 > div#tns3-item1
IMO AWARDS FIND OUT MORE div#tns3-mw > div#tns3-iw > div#tns3 > div#tns3-item2
WORLD MARITIME THEME FIND OUT MORE div#tns3-mw > div#tns3-iw > div#tns3 > div.entry-item

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.

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
FIND OUT MORE div#tns1-item0 > div.hero-slide > div.text-container > a.btn
Copyright International Maritime Organization (IMO). div.col-md-12 > div.d-flex > div > p.copyright
Terms of use div > ul.secondary-nav > li > a.underlined
Privacy Policy div > ul.secondary-nav > li > a.underlined
The official languages of IMO are Arabic, Chinese, English, French, Russian and… div.col-md-12 > div.d-flex > div.w-100 > small

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
IMO At Glance div.row > div.col-lg-6 > div.imo-figures > h4.label-small
div.row > div.mt-md-5 > div.follow-us-box > h6 div.row > div.mt-md-5 > div.follow-us-box > h6

These are opportunities to improve keyboard navigation in your application.

Names and labels

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.row > div.col-sm-12 > div.media > img div.row > div.col-sm-12 > div.media > img

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
nav.navbar > div.container-fluid > div.nav-item > a.icon-button nav.navbar > div.container-fluid > div.nav-item > a.icon-button

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.

Best practices

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
●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
●`[role]` values are valid
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●Buttons have an accessible name
●`[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
●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.
●`[lang]` attributes have a valid value
●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 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
○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.
○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.
○`<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.
○Elements with visible text labels have matching accessible names.
○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+
Form Accessibility
No form controls
PASS
No form controls
Info::
No form controls on this page
No form controls found.
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 Facilitation Committ…19.57:13.0:1
#000000
#F5F7FA
Pass
h1 IMO approves new gui…19.57:13.0:1
#000000
#F5F7FA
Pass
h1 Hazardous cargo comp…19.57:13.0:1
#000000
#F5F7FA
Pass
h1 “Fragmented respon…19.57:13.0:1
#000000
#F5F7FA
Pass
h1 Facilitation Committ…19.57:13.0:1
#000000
#F5F7FA
Pass
h1 IMO approves new gui…19.57:13.0:1
#000000
#F5F7FA
Pass
h2 ​IMO Secretary-Gen…19.57:13.0:1
#000000
#F5F7FA
Pass
h2 Maritime Safety19.57:13.0:1
#000000
#F5F7FA
Pass
h2 OUR WORK19.57:13.0:1
#000000
#F5F7FA
Pass
h2 Marine Environment19.57:13.0:1
#000000
#F5F7FA
Pass
h2 Maritime Safety19.57:13.0:1
#000000
#F5F7FA
Pass
h2 OUR WORK19.57:13.0:1
#000000
#F5F7FA
Pass
h2 CONVENTIONS19.57:13.0:1
#000000
#F5F7FA
Pass
h2 PUBLICATIONS19.57:13.0:1
#000000
#F5F7FA
Pass
h2 IMO Awards19.57:13.0:1
#000000
#F5F7FA
Pass
h2 WORLD MARITIME THEME19.57:13.0:1
#000000
#F5F7FA
Pass
h2 Day of the Seafarer19.57:13.0:1
#000000
#F5F7FA
Pass
h2 IMO Awards19.57:13.0:1
#000000
#F5F7FA
Pass
h2 WORLD MARITIME THEME19.57:13.0:1
#000000
#F5F7FA
Pass
h2 RESOURCES19.57:13.0:1
#000000
#F5F7FA
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.

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback