Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

11 PASS 7 REVIEW 6 FIX

Alt Text Quality

Action

17 of 148 images have issues

FIX

17 of 148 images have issues

15 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

3 image-in-link without alt text

An image inside a link with no alt creates an empty link.

2 image(s) with generic alt text

19 decorative image(s) correctly marked

112 image(s) with good alt text

148 images 112 good alt text 19 decorative 2 generic 15 missing

Issue	Count
missing	15 image(s)
generic	2 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

An image inside a link with no alt creates an empty link.

Why this matters

Image-only links with no alt create empty links — screen-reader users hear 'link' with no destination context.

Learn more ▾

An <a><img></a> with no img alt is the worst-case for accessibility: AT announces the link but can't describe where it goes. Either add alt to the image OR add aria-label to the link.

Source: WCAG 2.1 SC 2.4.4

Link & Button Quality

Action

5 issue(s) across 319 links and 10 buttons

FIX

5 issue(s) across 319 links and 10 buttons

2 link(s) with no accessible text

Links without text are announced as raw URLs by screen readers.

Got: /en; /en

1 link(s) with generic text

Generic link text like 'click here' doesn't describe the destination.

Got: /it/newsroom/news-e-comunicati-stampa/2026/fincantieri-la-sicurezza-come-valo… ("LEARN MORE")

7 link(s) open in new tab without warning

Add '(opens in new tab)' to link text or aria-label.

Got: /en/newsroom/press-releases/2026/first-half-2026-results-approved; /en/newsroom/press-releases/2026/fincantieri-and-princess-cruises-sign-contra…; https://www.linkedin.com/posts/fincantieri_sustainability-on-board-activity-7…; https://www.instagram.com/p/DbVwsZuouo0/?igsh=MW55aDZqcXhnbDVoeg%3D%3D; https://www.youtube.com/watch?v=jB8fS4wp7r4; https://x.com/Fincantieri/status/2084649270427140337; https://www.fincantieri.com/en/policies/cookie-policy/

2 button(s) with no accessible text

Icon-only buttons need an aria-label so screen readers can announce them.

Got: button#sendButton; button#backToTop

309 link(s) with descriptive text

319 links

2 empty

1 generic text

7 new tab

2 empty buttons

Element	Text	Issue	Suggested Fix
/en	(empty)	empty	Add link text or aria-label
/en	(empty)	empty	Add link text or aria-label
/en/newsroom/press-releases/2026/first-h…	LEARN MORE opens in a new …	new tab	Add '(opens in new tab)' to text
/it/newsroom/news-e-comunicati-stampa/20…	LEARN MORE	generic text	Replace with descriptive text
Before: LEARN MORE Suggested: Fincantieri La Sicurezza Come Valore Fondante Dello Sviluppo Industriale
/en/newsroom/press-releases/2026/fincant…	LEARN MORE opens in a new …	new tab	Add '(opens in new tab)' to text
/en/newsroom/press-releases/2026/Fincant…	20 Aug …	img no alt	Add alt attribute to the image
/en/newsroom/press-releases/2026/first-h…	29 Jul Fir…	img no alt	Add alt attribute to the image
/en/newsroom/press-releases/2026/fincant…	24 Jul Fin…	img no alt	Add alt attribute to the image
/en/newsroom/press-releases/2026/explora…	23 Jul Exp…	img no alt	Add alt attribute to the image
https://www.linkedin.com/posts/fincantie…	opens in a new tab	new tab	Add '(opens in new tab)' to text
https://www.instagram.com/p/DbVwsZuouo0/…	opens in a new tab	new tab	Add '(opens in new tab)' to text
https://www.youtube.com/watch?v=jB8fS4wp…	opens in a new tab	new tab	Add '(opens in new tab)' to text
https://x.com/Fincantieri/status/2084649…	opens in a new tab	new tab	Add '(opens in new tab)' to text
/en/newsroom/editorials/storie-di-sosten…	Editorial Uniting…	img no alt	Add alt attribute to the image
https://www.fincantieri.com/en/policies/…	cookie policy	new tab	Add '(opens in new tab)' to text
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label

317 links and buttons have descriptive text

Links without text are announced as raw URLs by screen readers.

/en; /en

Why this matters

Links with no accessible text (empty <a></a>, image-only no alt, icon-only no aria-label) are unidentifiable to screen readers.

Source: WCAG 2.1 SC 2.4.4

Generic link text like 'click here' doesn't describe the destination.

/it/newsroom/news-e-comunicati-stampa/2026/fincantieri-la-sicurezza-come-valo… ("LEARN MORE")

Why this matters

Generic anchor text ('click here', 'read more', 'learn more') tells screen readers and search engines nothing about the destination.

Learn more ▾

Out-of-context lists of links read by AT (one navigation pattern) become useless when every link says 'click here'. Use the destination's title or topic as anchor text. Doubles as SEO win — Google passes anchor-text relevance to the destination.

Source: WCAG 2.4.4 / Google Search Central

Add '(opens in new tab)' to link text or aria-label.

/en/newsroom/press-releases/2026/first-half-2026-results-approved; /en/newsroom/press-releases/2026/fincantieri-and-princess-cruises-sign-contra…; https://www.linkedin.com/posts/fincantieri_sustainability-on-board-activity-7…; https://www.instagram.com/p/DbVwsZuouo0/?igsh=MW55aDZqcXhnbDVoeg%3D%3D; https://www.youtube.com/watch?v=jB8fS4wp7r4; https://x.com/Fincantieri/status/2084649270427140337; https://www.fincantieri.com/en/policies/cookie-policy/

Why this matters

Links with target="_blank" without rel="noopener" leak the originating page's window context — security and UX issue.

Learn more ▾

Without rel="noopener", the new tab can navigate the original tab via window.opener (tab-nabbing attack). Modern browsers default to noopener for target=_blank but only since recent versions. Always set rel="noopener noreferrer" explicitly.

Source: MDN target / OWASP

Icon-only buttons need an aria-label so screen readers can announce them.

button#sendButton; button#backToTop

Why this matters

Buttons with no accessible text (icon-only, no aria-label) can't be activated by voice control or understood by screen readers.

Source: WCAG 2.1 SC 4.1.2

Web Manifest

Action

Not found

FIX

Not found

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.

Dark Mode Support

Action

No dark mode signals

FIX

No dark mode signals

No dark mode signals detected

Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.

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.

Print Stylesheet

Action

No print styles

FIX

No print styles

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 ✗

Landmark Structure

10 landmarks

REVIEW

10 landmarks

<main> landmark present

3 <nav> landmark(s) found

1 of 3 <nav> elements are unlabeled

Multiple navigations need aria-label to distinguish them for screen readers.

Skip navigation link present

Skip link target(s) don't exist on page: (empty fragment)

The skip-link anchor (e.g., `href="#main"`) points at an ID that has no corresponding element on the page. Activating the link does nothing -- a silent WCAG 2.4.1 failure that the visual link presence hides. Add `id="main"` (or whichever matches the href) to the target landmark.

Page Structure — as a screen reader sees it

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

Why this matters

Skip link points at an ID that doesn't exist on the page. The link looks fine visually but does nothing when activated -- silent WCAG 2.4.1 failure.

Learn more ▾

Find the target landmark (typically <main> or the first <h1>) and add `id="..."` matching the skip link's href fragment. Test by tabbing to the skip link and pressing Enter -- focus should jump to the target.

Source: WCAG 2.1 SC 2.4.1

Form Accessibility

2 of 7 controls have issues

REVIEW

2 of 7 controls have issues

1 control(s) without accessible label

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

Got: <textarea id="captain-page-new-chat-mobile__chat-input">

1 control(s) rely on placeholder only

Placeholder text disappears on focus and is not a reliable label.

Got: <textarea id="chatInput">

5 control(s) properly labeled

7 controls

5 labeled

1 placeholder only

1 unlabeled

Control	Type	Label	Method
#iub-toggle-id-1	checkbox	Necessary	for/id
#iub-toggle-id-2	checkbox	Functionality	for/id
#iub-toggle-id-3	checkbox	Experience	for/id
#iub-toggle-id-4	checkbox	Measurement	for/id
#iub-toggle-id-5	checkbox	Marketing	for/id
#chatInput	textarea	(Enter Text)	placeholder only
#captain-page-new-chat-mobile__chat-input	textarea	(none)	none

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

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.

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

Tap Target Adequacy

1 tap target(s) too small or too close together

REVIEW

1 tap target(s) too small or too close together

1 tap target(s) too small or too close to neighbors

WCAG 2.5.5 (Level AAA) requires interactive targets to be at least 44x44 CSS pixels; WCAG 2.5.8 (Level AA, added in 2.2) requires 24x24 minimum. Failing targets cause mis-taps for users with motor impairments, large fingers, or shaky hands -- and are a major bounce-rate driver on mobile commerce flows. Lighthouse measures rendered rects + adjacent-element spacing; the failing list is in the Lighthouse 'tap-targets' audit detail panel.

404 Error Page

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

Navigation links present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title Fincantieri | 404 ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✗

Favicon & Branding

8 icon(s) detected

REVIEW

8 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

Multiple icon sizes detected

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✓ Multiple Sizes Present

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 FINCANTIERI

1.07:1

#000000

#04072D

needs 3.0:1 (large text)

32px · bottom of viewport

h1 IS A GLOBAL GROUP

1.07:1

#000000

#04072D

needs 3.0:1 (large text)

32px · bottom of viewport

h1 NEWSROOM

1.07:1

#000000

#04072D

needs 3.0:1 (large text)

32px · bottom of viewport

h2 SAFETY DAY

1.07:1

#000000

#04072D

needs 3.0:1 (large text)

24px · bottom of viewport

h2 FINCANTIERI AND PRINCESS CRUISES SIGN CO…

1.07:1

#000000

#04072D

needs 3.0:1 (large text)

24px · bottom of viewport

h2 WE ARE LEADERS IN SHIPBUILDING.

1.07:1

#000000

#04072D

needs 3.0:1 (large text)

24px · bottom of viewport

h2 AND MUCH MORE

1.07:1

#000000

#04072D

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Fincantieri and Viking sign contracts fo…

1.07:1

#000000

#04072D

needs 3.0:1 (large text)

24px · bottom of viewport

h2 DEI

1.07:1

#000000

#04072D

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Cookies, tracking and consent

1.07:1

#000000

#04072D

needs 3.0:1 (large text)

24px · bottom of viewport

title Fincantieri | Home Page

1.07:1

#000000

#04072D

needs 4.5:1 (normal text)

16px · top of page (header area)

a Skip to content

1.07:1

#000000

#04072D

needs 4.5:1 (normal text)

16px · top of page (header area)

p I am CaptAIn, the AI agent that is redes…

1.07:1

#000000

#04072D

needs 4.5:1 (normal text)

16px · top of page (header area)

p Proof that Fincantieri does not follow t…

1.07:1

#000000

#04072D

needs 4.5:1 (normal text)

16px · top of page (header area)

span Skip

1.07:1

#000000

#04072D

needs 4.5:1 (normal text)

16px · above the fold

p I am CaptAIn, the AI agent that is redes…

1.07:1

#000000

#04072D

needs 4.5:1 (normal text)

16px · above the fold

p Proof that Fincantieri does not follow t…

1.07:1

#000000

#04072D

needs 4.5:1 (normal text)

16px · above the fold

span Skip

1.07:1

#000000

#04072D

needs 4.5:1 (normal text)

16px · above the fold

a Group

1.07:1

#000000

#04072D

needs 4.5:1 (normal text)

16px · above the fold

a Business

1.07:1

#000000

#04072D

needs 4.5:1 (normal text)

16px · above the fold

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 FINCANTIERI	1.07:1	3.0:1	#000000	#04072D	Fail
h1 IS A GLOBAL GROUP	1.07:1	3.0:1	#000000	#04072D	Fail
h1 NEWSROOM	1.07:1	3.0:1	#000000	#04072D	Fail
h2 SAFETY DAY	1.07:1	3.0:1	#000000	#04072D	Fail
h2 FINCANTIERI AND PRIN…	1.07:1	3.0:1	#000000	#04072D	Fail
h2 WE ARE LEADERS IN SH…	1.07:1	3.0:1	#000000	#04072D	Fail
h2 AND MUCH MORE	1.07:1	3.0:1	#000000	#04072D	Fail
h2 Fincantieri and Viki…	1.07:1	3.0:1	#000000	#04072D	Fail
h2 DEI	1.07:1	3.0:1	#000000	#04072D	Fail
h2 Cookies, tracking an…	1.07:1	3.0:1	#000000	#04072D	Fail
title Fincantieri \| Home P…	1.07:1	4.5:1	#000000	#04072D	Fail
a Skip to content	1.07:1	4.5:1	#000000	#04072D	Fail
p I am CaptAIn, the AI…	1.07:1	4.5:1	#000000	#04072D	Fail
p Proof that Fincantie…	1.07:1	4.5:1	#000000	#04072D	Fail
span Skip	1.07:1	4.5:1	#000000	#04072D	Fail
p I am CaptAIn, the AI…	1.07:1	4.5:1	#000000	#04072D	Fail
p Proof that Fincantie…	1.07:1	4.5:1	#000000	#04072D	Fail
span Skip	1.07:1	4.5:1	#000000	#04072D	Fail
a Group	1.07:1	4.5:1	#000000	#04072D	Fail
a Business	1.07:1	4.5:1	#000000	#04072D	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.

Lighthouse Accessibility Audits

Action

Score 79/100 — 6 failing, 24 passed

REVIEW

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

When an element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn how to make command elements more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.swiper > div.swiper-wrapper > div.swiper-slide > div.btn-video-pause `div.swiper > div.swiper-wrapper > div.swiper-slide > div.btn-video-pause`
div.swiper > div.swiper-wrapper > div.swiper-slide > div.btn-video-audio `div.swiper > div.swiper-wrapper > div.swiper-slide > div.btn-video-audio`
div.swiper > div.swiper-wrapper > div.swiper-slide > div.btn-video-pause `div.swiper > div.swiper-wrapper > div.swiper-slide > div.btn-video-pause`
div.swiper > div.swiper-wrapper > div.swiper-slide > div.btn-video-audio `div.swiper > div.swiper-wrapper > div.swiper-slide > div.btn-video-audio`

ARIA dialog elements without accessible names may prevent screen readers users from discerning the purpose of these elements. Learn how to make ARIA dialog elements more accessible.

Why this matters

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

Source: MDN Permissions-Policy

Failing Elements
I AM CAPTAIN, THE AI AGENT THAT IS REDESIGNING DIGITAL NAVIGATION. PROOF THAT … `nav.fc-menu > div > div.fc-intro-captain > div#overlay-intro-captain`

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

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.main-logo-container > div.flex-row > a > img.main-logo `div.main-logo-container > div.flex-row > a > img.main-logo`
div#tlb-widget > div#wChartContainer > div.tlb-chart-wrapper > img#wChart `div#tlb-widget > div#wChartContainer > div.tlb-chart-wrapper > img#wChart`
div.video-component > div.video-container > div.poster-container > img `div.video-component > div.video-container > div.poster-container > img`
div.cmp-video-with-hotspot__inner-slider > div.cmp-video-with-hotspot__slide > div.poster-container > img `div.cmp-video-with-hotspot__inner-slider > div.cmp-video-with-hotspot__slide > div.poster-container > img`
div.cmp-video-with-hotspot__inner-slider > div.cmp-video-with-hotspot__slide > div.poster-container > img `div.cmp-video-with-hotspot__inner-slider > div.cmp-video-with-hotspot__slide > div.poster-container > img`
div.cmp-video-with-hotspot__inner-slider > div.cmp-video-with-hotspot__slide > div.poster-container > img `div.cmp-video-with-hotspot__inner-slider > div.cmp-video-with-hotspot__slide > div.poster-container > img`
div.cmp-video-with-hotspot__inner-slider > div.cmp-video-with-hotspot__slide > div.poster-container > img `div.cmp-video-with-hotspot__inner-slider > div.cmp-video-with-hotspot__slide > div.poster-container > img`
div.cmp-video-with-hotspot__inner-slider > div.cmp-video-with-hotspot__slide > div.poster-container > img `div.cmp-video-with-hotspot__inner-slider > div.cmp-video-with-hotspot__slide > div.poster-container > img`
div.video-component > div.video-container > div.poster-container > img `div.video-component > div.video-container > div.poster-container > 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
div > div.main-logo-container > div.flex-row > a `div > div.main-logo-container > div.flex-row > a`

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

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
Fincantieri logo `div > div.main-logo-container > div.flex-row > a`

These items highlight common accessibility best practices.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
01 `div.carousel-container > div.swiper > div.swiper-pagination > div.swiper-pagination-bullet`
02 `div.carousel-container > div.swiper > div.swiper-pagination > div.swiper-pagination-bullet`
03 `div.carousel-container > div.swiper > div.swiper-pagination > div.swiper-pagination-bullet`
04 `div.carousel-container > div.swiper > div.swiper-pagination > div.swiper-pagination-bullet`
01 `div.controllate-light-version-container-mobile > div.controllate-nav-container > div.inner-controllate-nav-container > div.nav-bullet`
WE ARE PIONEERS `div.links-list-component > div.horizontal-scrollable-container > div.inner-horizontal-scrollable-container > a.link-element`
WE ARE LEADERS `div.links-list-component > div.horizontal-scrollable-container > div.inner-horizontal-scrollable-container > a.link-element`

○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

●`[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

●`[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

●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

●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"]`

●All heading elements contain content.

●Uses ARIA roles only on compatible elements

●Identical links have the same purpose.

○`[accesskey]` values are unique

○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

○Buttons have an accessible name

○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.

○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.

○`[lang]` attributes have a valid value

○Tables have different content in the summary attribute and `<caption>`.

○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.

Heading Hierarchy

36 headings

PASS

36 headings

Multiple H1 headings (4 found)

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

1 empty heading(s)

Empty headings appear in the document outline but provide no information.

H3 About us
H3 Innovation
H3 Governance and Ethics
H3 Sustainability
H3 Company
H3 Products
H3 Services
H3 Living at Fincantieri
H3 Work with us
H3 Newsroom
H3 Investor Relations
H3 Suppliers and Partners
H3 About us
H3 Innovation
H3 Governance and Ethics
H3 Sustainability
H3 Company
H3 Products
H3 Services
H3 Living at Fincantieri
H3 Work with us
H3 Newsroom
H3 Investor Relations
H3 Suppliers and Partners
H2 (empty)
H2 SAFETY DAY
H2 FINCANTIERI AND PRINCESS CRUISES SIGN CONTRACT FOR THREE NEW CRUISE SHIPS
H1 FINCANTIERIIS A GLOBAL GROUP
H2 WE ARE LEADERS IN SHIPBUILDING.AND MUCH MORE
H1 UNDERWATER APPLICATION AREAS duplicate H1
H2 F4
H1 FAST. FORWARD. FURTHER. FUTURE. duplicate H1
H1 NEWSROOM duplicate H1
H2 Fincantieri and Viking sign contracts for two new ocean ships
H2 DEI
H2 Cookies, tracking and consent

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

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

Heading Text Quality

2 heading-text-quality issue(s) detected

PASS

2 heading-text-quality issue(s) detected

1 heading(s) are too short (≤2 characters) to convey meaning

Headings with 2 or fewer characters are almost always emoji / typos / alignment hacks rather than real headings. Screen readers announce the heading level ("heading 2") and then read the content -- a single-character heading conveys no information. Affected: - H2: "F4"

Got: 1 ≤2-char heading(s)

7 heading(s) are all-uppercase (excluding short acronyms)

Headings rendered in all-uppercase are a styling choice that should be done via CSS (`text-transform: uppercase`), not by typing the text in caps. Capitalized text is read letter-by-letter by some screen readers (e.g., "H-E-L-L-O W-O-R-L-D" instead of "hello world"). It's also a soft signal of CMS-migration artifacts where the original lowercase intent was lost.

Got: 7 all-caps heading(s)

A+

Form Input Types

7 form control(s) checked, no type mismatches

PASS

7 form control(s) checked, no type mismatches

No input-type mismatches detected

A+

Form Input Quality

7 form control(s) checked, no input-semantic issues

PASS

7 form control(s) checked, no input-semantic issues

All form input semantics look correct

A+

Mobile Keyboard & Autofill

No autofill-eligible form controls

PASS

No autofill-eligible form controls

No autofill-eligible form controls (no name/email/tel/address fields)

A+

Document Language

Lang attribute set to "en"

PASS

Lang attribute set to "en"

<html lang="en"> is set and valid

Got: en

A+

Tabindex Anti-Patterns

105 explicit tabindex attribute(s) checked, no anti-patterns

PASS

105 explicit tabindex attribute(s) checked, no anti-patterns

No tabindex anti-patterns detected

A+

Iframe Accessibility

All 1 iframe(s) have descriptive titles

PASS

All 1 iframe(s) have descriptive titles

All 1 iframe(s) have title attributes

A+

Mobile-Readable Font Sizes

All 8 visible text node(s) render at >= 12 CSS pixels

PASS

All 8 visible text node(s) render at >= 12 CSS pixels

All text uses legible mobile font sizes (>= 12 CSS px)

A+

PWA Depth

No PWA depth issues detected

PASS

No PWA depth issues detected

A+

Mobile UX Depth

2 mobile-depth signal(s) detected

PASS

2 mobile-depth signal(s) detected

No `<meta name="theme-color">` -- browser chrome falls back to default

Without `theme-color`, Android Chrome's status bar and iOS Safari's toolbar fall back to a generic gray. Adding a single hex color in `<meta name="theme-color" content="#0066cc">` tints them to your brand color across all mobile browsers.

Viewport `viewport-fit=cover` -- supports notched / dynamic-island devices

The viewport meta declares `viewport-fit=cover`, which lets the page draw into the safe-area edges (notch, dynamic island, home indicator) on iPhone X+ devices. Pair with `env(safe-area-inset-*)` CSS to keep critical UI inside the inset rectangle while letting backgrounds extend edge-to-edge.

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