Skip to content
https://trenitalia.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
49
GRADE
F
FIX
7
REVIEW
3
PASS
3
INFO
0
Checks
13
3 PASS 3 REVIEW 7 FIX
F
404 Error Page
Action
Soft 404 detected
FIX
Soft 404 detected
Critical::
Soft 404: server returns HTTP 200 for non-existent pages
The server returns HTTP 200 for a path that does not exist. Search engines will index these pages, diluting your real content. Configure your server to return a proper 404 status code for missing pages.
Got: Status: 200 for /beavercheck-404-test-cjrxgd
404 Page Quality ✗ Soft 404 (HTTP 200)
Status Code: HTTP 200

The server returned HTTP 200 for a non-existent path. Search engines will index this page as real content. Configure your server to return HTTP 404 for missing pages.

F
Favicon & Branding
Action
2 icon(s) detected
FIX
2 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'>.
✓ favicon.ico Present
✓ PNG Icons Present
✗ Apple Touch Missing
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
F
Web Manifest
Action
Invalid JSON
FIX
Invalid JSON
Warning::
Manifest contains invalid JSON
Manifest at https://trenitalia.com/manifest.json contains invalid JSON. Browsers cannot parse it.
Got: https://trenitalia.com/manifest.json

Manifest contains invalid JSON.

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.
B
Landmark Structure
16 landmarks
REVIEW
16 landmarks
Info::
<main> landmark present
Info::
3 <nav> landmark(s) found
Warning::
1 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 "Apri menu principale del sito Trenitalia" 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

B
Heading Hierarchy
31 headings
REVIEW
31 headings
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
  • H2 Accedi all'area riservata
  • H3 Aprile 2026
  • H3 Aprile 2026
  • H3 Funzionamento della sezione Soluzioni Principali
  • H3 Agevolazioni per i ragazzi
  • H2 Aggiungi buoni sconto
  • H2 Acquista
  • H2 carosello immagini
  • H2 Offerte, servizi e collegamenti
  • H2 Offerte, servizi e collegamenti
  • H2 Offerte, servizi e collegamenti
  • H2 Offerte, servizi e collegamenti
  • H2 CartaFRECCIA
  • H2 Programma X-GO
  • H2 Scopri tutti i vantaggi dell’App Trenitalia
  • H2 La vostra privacy è per noi molto importante
  • H3 Noi e i nostri partner trattiamo i dati per fornire:
  • H2 Informazioni sulla vostra privacy
  • H3 Gestisci preferenze consenso
  • H4 Cookie strettamente necessari
  • H4 Cookie di prestazione (Analytics di terze parti)
  • H4 Cookie di profilazione
  • H4 Finalità per le Terze parti 1 partner possono utilizzare questa finalità
  • H5 Sviluppare e migliorare i servizi 1 partner possono utilizzare questa finalità
  • H5 Comprendere il pubblico attraverso statistiche o la combinazione di dati provenienti da fonti diverse 1 partner possono utilizzare questa finalità
  • H5 Misurare le prestazioni degli annunci 1 partner possono utilizzare questa finalità
  • H5 Utilizzare profili per la selezione di pubblicità personalizzata 1 partner possono utilizzare questa finalità
  • H5 Utilizzare dati limitati per la selezione della pubblicità 1 partner possono utilizzare questa finalità
  • H5 Creare profili per la pubblicità personalizzata 1 partner possono utilizzare questa finalità
  • H5 Archiviare informazioni su dispositivo e/o accedervi 1 partner possono utilizzare questa finalità
  • H3 Elenco dei cookie

Every page should have one H1 that describes the page content.

Why this matters

No H1 means screen-reader users can't identify the page's primary topic, and Google's content-extraction degrades.

Learn more ▾

The H1 is the document title for assistive tech and a strong signal to search engines about page topic. Pages without one force screen readers to fall back to the <title> attribute or page chrome. Add a single H1 that names the page's primary subject.

Source: WCAG 2.4.6 / Google Search Central

C
Form Accessibility
Action
3 of 41 controls have issues
REVIEW
3 of 41 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="text" id="gpm-fix">
Warning::
2 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" id="calendarAndata">; <input type="text" id="calendarRitorno">
Info::
38 control(s) properly labeled
41 controls
38 labeled
2 placeholder only
1 unlabeled
ControlTypeLabelMethod
#menu-searchsearchAvvia ricercafor/id
#uidtextUser / Codicefor/id
#pwdpasswordPasswordfor/id
#partenzatextPartenza da Stazione di partenza, digita la stazione poi selezionala dall’elenco con i tasti frecce e conferma con inviofor/id
#arrivotextArrivo a Stazione di arrivo, digita la stazione poi selezionala dall’elenco con i tasti frecce e conferma con inviofor/id
#1radioSoluzioni Principalifor/id
#2radioLe Freccefor/id
#bestpricecheckboxnone
#3radioRegionalefor/id
#4radioIntercityfor/id
#email-pnr-codiceradioEmail e PNR/ Codice bigliettofor/id
#pnr-cpradioPNR e CPfor/id
#acquisto-senza-registrazioneradioAcquisto senza registrazionefor/id
#numero-treno-stazioneradioNumero trenofor/id
#nome-email-pnr-codicetextNomefor/id
#cognome-email-pnr-codicetextCognomefor/id
#codice-recupero-email-pnr-codicetextCodice di recuperofor/id
#pnrtextPNRfor/id
#cptextCPfor/id
#email-acquisto-senza-registrazioneemailEmailfor/id
#codice-biglietto-acquisto-senza-registrazionetextPNR/Codice bigliettofor/id
#numero-treno-stazione-inputtextNumero trenofor/id
#buonoSconto1textInserisci buono scontoaria-label
#ot-group-id-C0002checkboxCookie di prestazione (Analytics di terze parti)for/id
#ot-group-id-C0004checkboxCookie di profilazionefor/id
#ot-group-id-BG277checkboxFinalità per le Terze partifor/id
#ot-sub-group-id-IAB2V2_10checkboxSviluppare e migliorare i serviziaria-label
#ot-sub-group-id-IAB2V2_9checkboxComprendere il pubblico attraverso statistiche o la combinazione di dati provenienti da fonti diversearia-label
#ot-sub-group-id-IAB2V2_7checkbox Misurare le prestazioni degli annunciaria-label
#ot-sub-group-id-IAB2V2_4checkboxUtilizzare profili per la selezione di pubblicità personalizzataaria-label
#ot-sub-group-id-IAB2V2_2checkboxUtilizzare dati limitati per la selezione della pubblicitàaria-label
#ot-sub-group-id-IAB2V2_3checkboxCreare profili per la pubblicità personalizzataaria-label
#ot-sub-group-id-IAB2V2_1checkboxArchiviare informazioni su dispositivo e/o accederviaria-label
#vendor-search-handlertextRicerca nell'elenco dei cookiearia-label
#chkbox-idcheckboxcheckbox labelfor/id
#select-all-hosts-groups-handlercheckboxcheckbox labelfor/id
#select-all-vendor-groups-handlercheckboxcheckbox labelfor/id
#select-all-vendor-leg-handlercheckboxcheckbox labelfor/id
#calendarRitornotext(mm/dd/yyyy)placeholder only
#calendarAndatatext(mm/dd/yyyy)placeholder only
#gpm-fixtext(none)none

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

<input type="text" id="gpm-fix">

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.

<input type="text" id="calendarAndata">; <input type="text" id="calendarRitorno">

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

A+
Alt Text Quality
All 107 images OK
PASS
All 107 images OK
Info::
2 decorative image(s) correctly marked
Info::
105 image(s) with good alt text
107 images 105 good alt text 2 decorative
All images have appropriate alt text.
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
h2 Accedi all'area rise…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Aggiungi buoni scont…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Acquista21.00:13.0:1
#000000
#FFFFFF
Pass
h2 carosello immagini21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Offerte, servizi e c…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Offerte, servizi e c…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Offerte, servizi e c…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Offerte, servizi e c…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 CartaFRECCIA21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Programma X-GO21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Scopri tutti i vanta…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 La vostra privacy è…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Informazioni sulla v…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Aprile 202621.00:13.0:1
#000000
#FFFFFF
Pass
h3 Aprile 202621.00:13.0:1
#000000
#FFFFFF
Pass
h3 Funzionamento della …21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Agevolazioni per i r…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Noi e i nostri partn…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Gestisci preferenze …21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Elenco dei cookie21.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 91/100 — 3 failing, 29 passed
PASS
91

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

Each ARIA `role` supports a specific subset of `aria-*` attributes. Mismatching these invalidates the `aria-*` attributes. Learn how to match ARIA attributes to their roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Frecciarossa Regionale Intercity Internazionale div#custom-tabs-bar-cd7ca6a6b2 > nav.tab-bar > div#nav-tab > div.scrolled-content

Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more about roles and required children elements.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Frecciarossa Regionale Intercity Internazionale div.custom-tabs-bar > div#custom-tabs-bar-cd7ca6a6b2 > nav.tab-bar > div#nav-tab

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.

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
Scopri di più div.container-custom > div.pre-footer-row > div.col-cta > a.cta
○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-hidden="true"]` is not present on the document `<body>`
●`[role]`s have all required `[aria-*]` attributes
●`[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
●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 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.
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Deprecated ARIA roles were not used
●ARIA IDs are unique
●Uses ARIA roles only on compatible elements
●Identical links have the same purpose.
○`[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 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
○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
○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
○`<video>` elements contain a `<track>` element with `[kind="captions"]`
○Tables have different content in the summary attribute and `<caption>`.
○All heading elements contain content.
○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