Skip to content
https://www.maersk.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
59
GRADE
D
FIX
5
REVIEW
4
PASS
4
INFO
0
Checks
13
4 PASS 4 REVIEW 5 FIX
D
404 Error Page
Action
HTTP 403, custom page
FIX
HTTP 403, custom page
Warning::
Unexpected status code: HTTP 403
Expected HTTP 404 but received 403. This may confuse search engine crawlers.
Got: HTTP 403
Info::
Custom styled 404 page
Info::
Navigation links present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 403 ✗Page Title Internal Server Error ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✗
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
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Search functionality detected
Got: role-search
Info::
7 navigation landmark(s) detected
Breadcrumbs
Search role='search' landmark
Skip Link
Labeled Navigation 7 <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.
B
Landmark Structure
12 landmarks
REVIEW
12 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.
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.
Info::
Search landmark present
Page Structure — as a screen reader sees it
BANNER header NAV "menu" 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

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
3 of 12 controls have issues
REVIEW
3 of 12 controls have issues
Critical::
2 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <select>; <select name="fld-regions" id="fld-regions">
Warning::
1 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <textarea id="ign-header__search--ai__input">
Info::
9 control(s) properly labeled
12 controls
9 labeled
1 placeholder only
2 unlabeled
ControlTypeLabelMethod
#cookie_cat_necessarycheckboxEssentialaria-label
#cookie_cat_functionalcheckboxFunctionalaria-label
#cookie_cat_statisticcheckboxStatisticalaria-label
#cookie_cat_marketingcheckboxMarketingaria-label
#cookie_cat_unclassifiedcheckboxUnclassifiedaria-label
#tracking-number_68dad9a3c09e4ace8a4472d3d8ddc5c9textThis is a required field.for/id
#schedules-9052d4e5-fd79-43e9-9722-dd8104b187fa-origin_idtextOrigin is incorrectfor/id
#schedules-02f8cee4-7ad6-4374-8e4c-0749093279a4-destination_idtextDestination is incorrectfor/id
#office_68dad9a3c09e4ace8a4472d3d8ddc5c9textThis is a required fieldfor/id
#ign-header__search--ai__inputtextarea(How can I help?)placeholder only
selectselect(none)none
#fld-regionsselect(none)none

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

<select>; <select name="fld-regions" id="fld-regions">

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.

<textarea id="ign-header__search--ai__input">

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

C
Favicon & Branding
Action
4 icon(s) detected
REVIEW
4 icon(s) detected
Info::
favicon.ico present at site root
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'>.
Info::
Multiple icon sizes detected
✓ favicon.ico Present
✓ PNG Icons Present
✗ Apple Touch Missing
✗ SVG Favicon Missing
✓ Manifest Icons Present
✓ Multiple Sizes Present
B
Lighthouse Accessibility Audits
Score 87/100 — 4 failing, 30 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.

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.service-widget__tabs > nav.tabs > div.tabs__wrapper > button.tabs__next div.service-widget__tabs > nav.tabs > div.tabs__wrapper > button.tabs__next
div.p-page__section__outer > div.p-page__section__inner > div.p-section__sticky-callout > button.p-section__sticky-callout__close div.p-page__section__outer > div.p-page__section__inner > div.p-section__sticky-callout > button.p-section__sticky-callout__close

Form elements without effective labels can create frustrating experiences for screen reader users. Learn more about the `select` element.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
All categories Digitalisation Growth Integrated logistics Resilience Sustainabi… div.p-page__section__inner > div.p-section__insights-mosaic > div.form-input > select.form-input__field
All regions North America Latin America Europe India Middle East and Africa Asi… div.p-page__section__chile > div.p-section__featured-news__actions__filter > div.form-input > select#fld-regions

Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
body > div#chatDiv > iframe#chatFrame body > div#chatDiv > iframe#chatFrame

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.

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
Middle East Situation div.p-page__section__inner > div.p-section__sticky-callout > div.p-section__sticky-callout__copy > h3.p-section__sticky-callout__title

These are opportunities to improve keyboard navigation in your application.

○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
●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 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
●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
●No element has a `[tabindex]` value greater than 0
●Touch targets have sufficient size and spacing.
●`[lang]` attributes have a valid value
●Document has a main landmark.
●Deprecated ARIA roles were not used
●`<video>` elements contain a `<track>` element with `[kind="captions"]`
●Image elements do not have `[alt]` attributes that are redundant text.
●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 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
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○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
○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
31 headings, 1 skip(s)
PASS
31 headings, 1 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H1 → H3 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H4 Popular searches
  • H4 Common tasks
  • H4 FAQ topics
  • H4 Use our East-West Network to set a new standard for reliability and service quality
  • H4 Explore the Global Logistics Trends of 2025
  • H4 Use our East-West Network to set a new standard for reliability and service quality
  • H4 Explore the Global Logistics Trends of 2025
  • H4 Use our East-West Network to set a new standard for reliability and service quality
  • H4 Explore the Global Logistics Trends of 2025
  • H1 Unlock the full potential of your supply chain
  • H3 Middle East Situation skipped
  • H3 How to get started
  • H3 Ready to book?
  • H3 Become a logistics expert
  • H2 Be ready for anything to go all the way
  • H3 Logistics services and solutions
  • H2 The Maersk East-West Network
  • H2 The Logistics Trend Map
  • H2 Industry sectors
  • H3 FMCG
  • H3 Retail
  • H3 Fashion & Lifestyle
  • H3 Chemicals
  • H3 Perishables
  • H3 Automotive
  • H3 Pharma & Healthcare
  • H3 Technology
  • H2 Latest insights
  • H2 Latest news
  • H3 No featured articles found
  • H3 Error occurred

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

A+
Alt Text Quality
1 of 64 images have issues
PASS
1 of 64 images have issues
Warning::
1 image(s) with generic alt text
Info::
1 decorative image(s) correctly marked
Info::
62 image(s) with good alt text
64 images 62 good alt text 1 decorative 1 generic
IssueCount
generic1 image(s)
A+
Web Manifest
PWA-ready
PASS
PWA-ready
Info::
Meets PWA install criteria
Info::
Name present: Maersk.com
Info::
192x192 icon present
Info::
512x512 icon present
Info::
Display mode: standalone
PWA Install Criteria ✓ Installable
Name Maersk.com ✓192×192 icon ✓512×512 icon ✓Start URL / ✓Display Mode standalone ✓
Name Maersk.com Display Mode standalone Theme Color #003e5e Background Color #003e5e Icons 2 icon(s)
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 Unlock the full pote…8.13:13.0:1
#000000
#A1A1A1
Pass
h2 Be ready for anythin…8.13:13.0:1
#000000
#A1A1A1
Pass
h2 The Maersk East-West…8.13:13.0:1
#000000
#A1A1A1
Pass
h2 The Logistics Trend …8.13:13.0:1
#000000
#A1A1A1
Pass
h2 Industry sectors8.13:13.0:1
#000000
#A1A1A1
Pass
h2 Latest insights8.13:13.0:1
#000000
#A1A1A1
Pass
h2 Latest news8.13:13.0:1
#000000
#A1A1A1
Pass
h3 Middle East Situatio…8.13:13.0:1
#000000
#A1A1A1
Pass
h3 How to get started8.13:13.0:1
#000000
#A1A1A1
Pass
h3 Ready to book?8.13:13.0:1
#000000
#A1A1A1
Pass
h3 Become a logistics e…8.13:13.0:1
#000000
#A1A1A1
Pass
h3 Logistics services a…8.13:13.0:1
#000000
#A1A1A1
Pass
h3 FMCG8.13:13.0:1
#000000
#A1A1A1
Pass
h3 Retail8.13:13.0:1
#000000
#A1A1A1
Pass
h3 Fashion & Lifestyle8.13:13.0:1
#000000
#A1A1A1
Pass
h3 Chemicals8.13:13.0:1
#000000
#A1A1A1
Pass
h3 Perishables8.13:13.0:1
#000000
#A1A1A1
Pass
h3 Automotive8.13:13.0:1
#000000
#A1A1A1
Pass
h3 Pharma & Healthcare8.13:13.0:1
#000000
#A1A1A1
Pass
h3 Technology8.13:13.0:1
#000000
#A1A1A1
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