Skip to content
https://eni.com

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
79
GRADE
C
FIX
4
REVIEW
7
PASS
13
INFO
0
Checks
24
13 PASS 7 REVIEW 4 FIX
D
Alt Text Quality
Action
10 of 77 images have issues
FIX
10 of 77 images have issues
Critical::
4 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Warning::
6 image(s) with generic alt text
Info::
2 decorative image(s) correctly marked
Info::
65 image(s) with good alt text
77 images 65 good alt text 2 decorative 6 generic 4 missing
IssueCount
missing4 image(s)
generic6 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

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::
Skip navigation link detected
Info::
3 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 3 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
3 of 6 testable patterns navigation patterns detected. Strong navigation UX with multiple discovery paths.
C
Landmark Structure
Action
15 landmarks
REVIEW
15 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
Info::
All <nav> elements are properly labeled
Info::
Skip navigation link present
Warning::
Skip link target(s) don't exist on page: #skipToMainContent
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
BANNER header NAV "Main navigation" 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

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.

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

B
Heading Hierarchy
52 headings
REVIEW
52 headings
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
Info::
8 hidden heading(s) (aria-hidden)
  • H3 Login
  • H2 Explore energy trends with the World Energy Review 2026
  • H2 Eni for 2025 – Sustainability Report
  • H2 Eni’s technological triangle
  • H2 Press releases
  • H3 Eni: report on the purchase of treasury shares during the period from 10 to 14 August 2026
  • H3 Eni and SONATRACH expand cooperation to reduce emissions in Algeria
  • H3 Argentina LNG submits application for RIGI approval
  • H3 Eni: report on the purchase of treasury shares during the period from 3 to 7 August 2026
  • H2 Business highlights
  • H3 Eni opens up supercomputing to businesses, startups and research hidden
  • H3 Our worldwide activities, the global reach of our actions hidden
  • H3 The technological neutrality principle – energy for competitiveness hidden
  • H3 Natural Gas – centre stage in our new energy mix hidden
  • H2 Discover Eni
  • H3 A strategic vision driven by research and technological innovation hidden
  • H3 Our actions: concrete steps towards carbon neutrality hidden
  • H3 Increasingly decarbonized products, services, and solutions hidden
  • H2 POLICIES
  • H3 Registered Head Office
  • H3 Company Share Capital
  • H3 Tax Identification Number
  • H3 Branches
  • H3 Rome Company Register
  • H2 OTHER LINKS
  • H3 Clear chat
  • H2 A window into Eni’s world
  • H3 Type your question here, and I’ll do my best to answer you!
  • H3 Disclaimer
  • H3 How does EnergIA work?
  • H2 My searches
  • H3 How does EnergIA work?
  • H3 Disclaimer
  • H3 Type your question here, and I’ll do my best to answer you!
  • H3 Use Eni’s artificial intelligence
  • H2 Modal Disclaimer
  • H2 This website uses cookies
  • H2 Privacy Preference Center
  • H2 Privacy Preference Center hidden
  • H3 Your Privacy
  • H3 Functional Cookies
  • H3 Strictly Necessary Cookies
  • H3 Performance Cookies
  • H3 Targeting Cookies
  • H3 Social Media Cookies
  • H4 Your Privacy
  • H4 Functional Cookies
  • H4 Strictly Necessary Cookies
  • H4 Performance Cookies
  • H4 Targeting Cookies
  • H4 Social Media Cookies
  • H3 Cookie List

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
404 Error Page
Action
Could not test
REVIEW
Could not test
Info::
404 page could not be tested
The 404 page check encountered an error. This may be due to a timeout or network issue.

404 page quality check not available.

B
Web Manifest
Valid manifest
REVIEW
Valid manifest
Info::
Name present: Eni.com
Info::
192x192 icon present
Info::
512x512 icon present
PWA Install Criteria Not Installable
Name Eni.com ✓192×192 icon ✓512×512 icon ✓Start URL / ✓Display Mode ✗
Name Eni.com Theme Color #fed300 Background Color #fed300 Icons 9 icon(s)
B
PWA Depth
2 PWA signal(s) surfaced
REVIEW
2 PWA signal(s) surfaced
Warning::
Manifest is missing `display` -- defaults to browser, no PWA UX
When `display` is `browser` (or unset, which is the spec default), the installed app opens in a regular browser tab -- no install prompt, no standalone window, no app-shell experience. The intended values for a PWA are `standalone` (most common; full-screen, no browser chrome) or `fullscreen` (games / immersive apps). `minimal-ui` is a middle ground (basic browser controls but no address bar).
Info::
Manifest has no maskable icon
Android 12+ Adaptive Icons crop non-maskable icons to a circle or squircle -- frequently hiding important parts of the logo. Add at least one icon entry with `"purpose": "maskable"` (or `"any maskable"`) and a maskable-aware design (16% safe-zone padding around the inner mark).
B
Lighthouse Accessibility Audits
Score 89/100 — 4 failing, 28 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.

ARIA

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
Use Eni’s artificial intelligence A window into Eni’s world, at your disposal.… body#page-c099fe26b6 > div > div#popupWelcome-genAI

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
li#splide02-slide01 > div.splide-content > picture > img.image

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.

Tables and lists

Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Link Linkedin footer#footer--273961437 > section.wrapper-component > div.fascia-social > ul.icons

These are opportunities to improve the experience of reading tabular or list data using 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
19 AUGUST 2026 - 9:30 AM CEST Eni: report on the purchase of treasury shares du… ul#splide01-list > li#splide01-slide01 > article > a.card
17 AUGUST 2026 - 11:00 AM CEST Eni and SONATRACH expand cooperation to reduce e… ul#splide01-list > li#splide01-slide02 > article > a.card
ACTIONS Our worldwide activities, the global reach of our actions div.wrapper-component > div#mosaico-1327084557 > article > a
VISION The technological neutrality principle – energy for competitiveness div.wrapper-component > div#mosaico-1327084557 > article > a
VISION A strategic vision driven by research and technological innovation div#nav-default > div.containerCard > article > a
ACTIONS Our actions: concrete steps towards carbon neutrality div#nav-default > div.containerCard > article > a
PRODUCT Increasingly decarbonized products, services, and solutions div#nav-default > div.containerCard > article > a
cookie-policy div#onetrust-group-container > div#onetrust-policy > div#onetrust-policy-text > a.ot-cookie-policy-link
○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
●`[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
●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
●Skip links are focusable.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●ARIA IDs are unique
●Uses ARIA roles only on compatible elements
○`[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
○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.
○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.
○Identical links have the same purpose.
○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 Text Quality
1 heading-text-quality issue(s) detected
PASS
1 heading-text-quality issue(s) detected
Info::
2 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: 2 all-caps heading(s)
A+
Form Accessibility
All 20 controls labeled
PASS
All 20 controls labeled
Info::
20 control(s) properly labeled
20 controls
20 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
#radioENradioEN - Englishfor/id
#radioITradioIT - Italianofor/id
#inputSearch-desktoptextSearchfor/id
#inputSearch-mobiletextSearchfor/id
#radioEN-mobileradioENfor/id
#radioIT-mobileradioITfor/id
#question-input-desktop-1inputInserisci una domanda per la ricercaaria-label
#question-input-desktop-2inputInserisci una domanda per la ricercaaria-label
#question-input-mobileinputInserisci una domanda per la ricercaaria-label
#question-inputinputInserisci una domanda per la ricercaaria-label
#checkbox1checkboxCheckbox defaultfor/id
#ot-group-id-C0003checkboxFunctional Cookiesfor/id
#ot-group-id-C0002checkboxPerformance Cookiesfor/id
#ot-group-id-C0004checkboxTargeting Cookiesfor/id
#ot-group-id-C0005checkboxSocial Media Cookiesfor/id
#vendor-search-handlertextCookie list searcharia-label
#select-all-hosts-groups-handlercheckboxcheckbox labelfor/id
#select-all-vendor-groups-handlercheckboxcheckbox labelfor/id
#select-all-vendor-leg-handlercheckboxcheckbox labelfor/id
#chkbox-idcheckboxcheckbox labelfor/id
A
Form Input Types
3 input(s) using type=text where a specific type would help
PASS
3 input(s) using type=text where a specific type would help
Info::
Input "submitInputSearch" should use type="search" (currently type="text")
Field name "submitInputSearch" suggests type="search". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="search">.
Info::
Input "submitInputSearch" should use type="search" (currently type="text")
Field name "submitInputSearch" suggests type="search". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="search">.
Info::
Input "vendor-search-handler" should use type="search" (currently type="text")
Field name "vendor-search-handler" suggests type="search". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="search">.
A+
Form Input Quality
20 form control(s) checked, no input-semantic issues
PASS
20 form control(s) checked, no input-semantic issues
Info::
All form input semantics look correct
A+
Mobile Keyboard & Autofill
No autofill-eligible form controls
PASS
No autofill-eligible form controls
Info::
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"
Info::
<html lang="en"> is set and valid
Got: en
A
Tabindex Anti-Patterns
0 positive, 2 -1-on-focusable
PASS
0 positive, 2 -1-on-focusable
Info::
tabindex="-1" on naturally-focusable <button>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <button>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
A+
Iframe Accessibility
All 1 iframe(s) have descriptive titles
PASS
All 1 iframe(s) have descriptive titles
Info::
All 1 iframe(s) have title attributes
A+
Tap Target Adequacy
All tap targets meet WCAG 2.5.5/2.5.8 sizing
PASS
All tap targets meet WCAG 2.5.5/2.5.8 sizing
Info::
All tap targets meet WCAG 2.5.5 (44x44px) sizing
A+
Mobile-Readable Font Sizes
All 5 visible text node(s) render at >= 12 CSS pixels
PASS
All 5 visible text node(s) render at >= 12 CSS pixels
Info::
All text uses legible mobile font sizes (>= 12 CSS px)
A
Favicon & Branding
28 icon(s) detected
PASS
28 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
SVG favicon detected — scales perfectly to any size
Info::
Multiple icon sizes detected
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✓ SVG Favicon Present
✓ Manifest Icons Present
✓ Multiple Sizes Present
A+
Mobile UX Depth
1 mobile-depth signal(s) detected
PASS
1 mobile-depth signal(s) detected
Info::
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.
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 Explore energy trend…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Eni for 2025 – Sus…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Eni’s technologica…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Press releases21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Business highlights21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Discover Eni21.00:13.0:1
#000000
#FFFFFF
Pass
h2 POLICIES21.00:13.0:1
#000000
#FFFFFF
Pass
h2 OTHER LINKS21.00:13.0:1
#000000
#FFFFFF
Pass
h2 A window into Eni’…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 My searches21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Modal Disclaimer21.00:13.0:1
#000000
#FFFFFF
Pass
h2 This website uses co…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Privacy Preference C…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Privacy Preference C…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Login21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Eni: report on the p…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Eni and SONATRACH ex…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Argentina LNG submit…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Eni: report on the p…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Eni opens up superco…21.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.

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

Send Feedback